[Bug]: npm reporting several deprecated packages among the adminjs dependencies
Contact Details
Github messages
What happened?
I am trying to use the latest adminjs version 6.8.2, and am facing numerous warnings about dependency deprecations. See log output below.
I see, for example, rollup-plugin-terser listed among the dependencies here but its own npm page notes that it is deprecated and points to the version (@rollup/plugin-terser) that should be used instead. I didn't see this mentioned in a previous issue, so wanted to highlight it here. Is there anything I can do to help with making that update, or are there other obstacles to updating?
Bug prevalence
Whenever checking dependency deprecation
AdminJS dependencies version
"node_modules/adminjs": { "version": "6.8.2", "resolved": "https://registry.npmjs.org/adminjs/-/adminjs-6.8.2.tgz", "integrity": "sha512-+xxxxx==", "dependencies": { "@adminjs/design-system": "^3.1.6", "@babel/core": "^7.10.2", "@babel/parser": "^7.10.2", "@babel/plugin-transform-runtime": "^7.10.1", "@babel/polyfill": "^7.10.1", "@babel/preset-env": "^7.16.4", "@babel/preset-react": "^7.10.1", "@babel/preset-typescript": "^7.10.1", "@babel/register": "^7.10.1", "@hello-pangea/dnd": "^16.0.0", "@rollup/plugin-babel": "^5.2.1", "@rollup/plugin-commonjs": "^22.0.1", "@rollup/plugin-json": "^4.1.0", "@rollup/plugin-node-resolve": "^13.3.0", "@rollup/plugin-replace": "^2.3.3", "@types/babel-core": "^6.25.7", "@types/react": "^18.0.8", "axios": "^0.27.2", "babel-plugin-styled-components": "^1.11.1", "commander": "^5.1.0", "flat": "5.0.1", "i18next": "^21.9.2", "lodash": "^4.17.21", "ora": "^5.4.1", "prop-types": "^15.7.2", "punycode": "^2.1.1", "react": "^18.1.0", "react-dom": "^18.1.0", "react-i18next": "^11.18.6", "react-is": "^18.1.0", "react-redux": "^8.0.2", "react-router": "^6.3.0", "react-router-dom": "^6.3.0", "redux": "^4.2.0", "rollup": "^2.79.1", "rollup-plugin-terser": "^7.0.2", "slash": "^3.0.0", "styled-components": "^5.3.5", "uuid": "^8.3.2", "xss": "^1.0.13" }, "bin": { "admin": "cli.js" }
What browsers do you see the problem on?
No response
Relevant log output
npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
npm WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated @babel/[email protected]: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
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.
Relevant code that's giving you issues
No response
@dickorydock we will update these alongside version 7 where we plan to upgrade to ES modules as well.
@dziraf is there a general timeframe for that upgrade to version 7?
Hi, I came here from a Google search about this deprecated packages, here is a log of some of them:
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm error A complete log of this run can be found in: /home/andrey/.npm/_logs/2025-08-07T11_18_51_071Z-debug-0.log
I canceled the instalation. Do you have any update on this issue?