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
Describe the bug:
There are a number of out of date, deprecated or insecure packages used in the project. These should be updated.
NPM START build warnings:
Browserslist: caniuse-lite is outdated. Please run:
npx update-browserslist-db@latest
Why you should do it regularly: https://github.com/browserslist/update-db#readme
(node:642767) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:643011) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Expected behaviour:
NPM audit, and builds, should be clean and free of deprecation and out-of-date and insecure warnings or errors.
Environment:
Version: 2.3.0-RC2
Platform: Web App
OS: Amazon Linux
Browser: Brave (chrome)
To Reproduce:
npm start
npm audit
Any additional context, screenshots, etc:
I am working on a fork that fixes all the out-of-date issues and runs on the latest version of node.js. I will send a merge request when ready.
The text was updated successfully, but these errors were encountered:
Hello @ericfitz , thanks for raising this issue and it is certainly been a long running problem
If you can get some of these fixed that would be great: mainly they are a result of various third party libs that may be difficult to upversion - please see what you can do
I have assigned it to you and tentatively marked this for version 2.3.1 due for release next month, but if you need more time then version 2.4 is due mid year
Describe the bug:
There are a number of out of date, deprecated or insecure packages used in the project. These should be updated.
NPM START build warnings:
Expected behaviour:
NPM audit, and builds, should be clean and free of deprecation and out-of-date and insecure warnings or errors.
Environment:
To Reproduce:
npm start
npm audit
Any additional context, screenshots, etc:
I am working on a fork that fixes all the out-of-date issues and runs on the latest version of node.js. I will send a merge request when ready.
The text was updated successfully, but these errors were encountered: