deprecated dependencies with NPM Installation

[phpcodingmaster]

CheckList

• I agree to follow this project's Code of Conduct
• I have read and followed the Contributing Guide
• I have read and followed the Issue Tracker Guide
• I have searched and referenced existing issues and discussions
• I am filing a BUG report.
• I have managed to reproduce the bug after upgrading to the latest version
• I have created an accurate and minimal reproduction

Version

6.0.2

In What environments are you experiencing the problem?

Node.js

Node Version (if applicable)

None

Link To Reproduction

https://codesandbox.io/p/devbox/fabric-node-sandbox-forked-xewlhg

Steps To Reproduce

1. Run npm install fabric or npm install fabric --save
2. Check the console

Expected Behavior

Should not be deprecated modules.

Actual Behavior

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]: This package is no longer supported.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: This package is no longer supported.

Error Message & Stack Trace

No response

[asturur]

Those modules are part of the dev tooling for fabric.
Did you try to use npm install --production to avoid install dev deps?

[phpcodingmaster]

Hi @asturur - If I try --production it still shows the below.

npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Use your platform's native DOMException instead
npm warn deprecated [email protected]: This package is no longer supported.

Seems like there are a lot of packages that are deprecated

[asturur]

If they are deprecated are deprecated.
I m not investing time in the dev deps unless is JEST or is JSDOM.
If you want to discover which one are deprecated and from what and what it takes to update them you can open a PR.