BREAKING: deps: eth-block-tracker@^6.1.0->^7.1.0; Nodejs min v16#105
BREAKING: deps: eth-block-tracker@^6.1.0->^7.1.0; Nodejs min v16#105legobeat merged 3 commits intoMetaMask:mainfrom
Conversation
|
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring: Next stepsTake a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with |
|
0a8edfc to
524f630
Compare
4d2e2c1 to
18f457b
Compare
| "main": "dist/index.js", | ||
| "engines": { | ||
| "node": "^14 || ^16 || >=18" | ||
| "node": "^16.20.1 || ^18.16.1 || >=20" |
There was a problem hiding this comment.
Do we plan on making this version match the module template eventually? (I know this package is out of date and it seems you are progressively updating it, so no worries, just curious at what stage we are at here or what your thoughts are)
There was a problem hiding this comment.
I'm not sure if there will ever be a single version range that can be expected to be applicable to all packages? Something like what we have here seems reasonable at this point in time for a package like this: 16 is still widely used, 18 is LTS, 20 is current. Only the latest odd version, if any.
As for the subversions for 16 and 18: Hesitated briefly here between what's here (require latest patches, allow depending on newer features and hey it's breaking engines anyway) and a more conservative >=16, which could make it smoother for maintainers of any downstreams maintaining full 16.x support. That trade-off seemed worth it here.
No description provided.