Tutor npm error

Hello i have some problem to run tutot localy,
I use this command:

pip install "tutor[full]"
tutor local launch

After image built:
I have this error:

npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm notice 
npm notice New major version of npm available! 8.3.1 -> 10.6.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.6.0
npm notice Run npm install -g npm@10.6.0 to update!
npm notice 
npm ERR! code EINTEGRITY
npm ERR! sha512-sWMb40chzlUOKrHZCGpZoUrVnGm6khfL/fAMKO8vLtUR8yOmWIVVN7MRmep3/DSFhy1Hilon6qAH+UbLZgGG0w== integrity checksum failed when using sha512: wanted sha512-sWMb40chzlUOKrHZCGpZoUrVnGm6khfL/fAMKO8vLtUR8yOmWIVVN7MRmep3/DSFhy1Hilon6qAH+UbLZgGG0w== but got sha512-P9aZDwDEAVgAbdHG/ViapRzAUJ6zBSq/4I1lJFluIbrld6Sv6LI+HT2J4dgWqtfaCgIyDnHBHSHiJ/anter7wQ==. (11488 bytes)

npm ERR! A complete log of this run can be found in:
npm ERR!     /openedx/.npm/_logs/2024-04-28T11_36_43_075Z-debug-0.log
Error: Command failed with status 1: docker compose -f /Users/yurakomarnicki/Library/Application Support/tutor/env/local/docker-compose.yml -f /Users/yurakomarnicki/Library/Application Support/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /Users/yurakomarnicki/Library/Application Support/tutor/env/local/docker-compose.jobs.yml run --rm lms-job sh -e -c 

The initialization job contains various re-install operations needed to be done
on mounted directories (edx-platform, /mnt/*xblock, /mnt/<edx-ora, search, enterprise>)

  1. /mnt/*
    Whenever xblocks or other installable packages are mounted, during the image build, they are copied over to container
    and installed. This results in egg_info generation for the mounted directories. However, the egg_info is not carried
    over to host. When the containers are launched, the host directories without egg_info are mounted on runtime
    and disappear from pip list.

  2. edx-platform
    When a new local copy of edx-platform is bind-mounted, certain build
    artifacts from the openedx image’s edx-platform directory are lost.
    We regenerate them here.

for mounted_dir in /mnt/*; do
    if [ -f $mounted_dir/setup.py ] && ! ls $mounted_dir/*.egg-info >/dev/null 2>&1 ; then
        echo "Unable to locate egg-info in $mounted_dir"
        pip install -e $mounted_dir
    fi
done

if [ -f /openedx/edx-platform/bindmount-canary ] ; then
        # If this file exists, then edx-platform has not been bind-mounted,
        # so no build artifacts need to be regenerated.
        echo "Using edx-platform from image (not bind-mount)."
        echo "No extra setup is required."
        exit
fi

echo "Performing additional setup for bind-mounted edx-platform."
set -x # Echo out executed lines

# Regenerate Open_edX.egg-info
pip install -e .

# Regenerate node_modules
npm clean-install

# Regenerate static assets.
openedx-assets build --env=dev

set -x
echo "Done setting up bind-mounted edx-platform."

I have faced this error as well and proposed a fix here: fix: npm EINTEGRITY error in openedx build by regisb · Pull Request #1075 · overhangio/tutor · GitHub