You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm warn deprecated [email protected]:
core-js@<3.23.3 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. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
Step-by-step reproduction instructions
After deleting the folder 'node_modules' and file 'package-lock.json', run 'ncu', 'ncu -u' and 'npm install -force' in turn.
Run 'npm ls ' for each of the module names listed in the warn warning presented by npm.
Screenshots, screen recording, code snippet
Environment info
System:
OS: macOS 14.5
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Memory: 24.13 MB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 22.2.0 - ~/.nodebrew/current/bin/node
Yarn: 1.22.22 - /usr/local/bin/yarn
npm: 10.8.0 - ~/.nodebrew/current/bin/npm
Please confirm that you have searched existing issues in the repo.
No
Please confirm that you have tested with all plugins deactivated except Gutenberg.
No
The text was updated successfully, but these errors were encountered:
Description
npm warn deprecated [email protected]:
core-js@<3.23.3 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. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
Environment info
System:
Binaries:
Please confirm that you have searched existing issues in the repo.
No
Please confirm that you have tested with all plugins deactivated except Gutenberg.
No
The text was updated successfully, but these errors were encountered: