-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use native options of dependencies when available #19
Comments
undici is an official Node.js dependency. I don't see why changing it to |
The feature request, and the discussion on Twitter, is not about the vulnerabilities the Node.js version being tested - but the ones used by |
Yes, I understand. However, I'm still not convinced that removing |
Yes, I understand. But upgrading undici, or any other dependencies, may conflict with the minimum Node.js version which Ideally, this module should support some EOL Node.js versions, as it's aimed to inform users whether their Node.js version is vulnerable. But it's dependencies may (and likely) drop support for EOL Node.js versions sooner. There's no package.json engines field for this module, and I couldn't find minimum supported Node.js version in README. As per #6 (comment), I think this module aims to support Node.js 12+. Undici 6.x supoports Node.js 18+, for example https://github.com/nodejs/undici/blob/e218fc61eda46da8784e0cedcaa88cd7e84dee99/package.json#L137-L139 |
* feat: add compatibility to Node.js >= 0.12 For retro-compatibility lovers * doc: add note about supported Node.js versions * fixup! feat: add compatibility to Node.js >= 0.12 * chore: drop cli-colors Refs: #19 * fixup! extra forward slashes Co-authored-by: Trivikram Kamat <[email protected]> * fixup! feat: add compatibility to Node.js >= 0.12 --------- Co-authored-by: Trivikram Kamat <[email protected]>
I just realized that you're bundling all the code with |
The dist is only used for github actions, when users attempt to |
I see. In that case, moving the GitHub Actions usage into its own package might be better. |
* chore: remove debug dependency (#25) Part of: #19 * Use response.pipe instead of stream.pipeline * Add error handler for fetchCoreIndex and call end() * Remove variable req in getCoreIndex() --------- Co-authored-by: Rafael Gonzaga <[email protected]>
Is your feature request related to a problem? Please describe.
Since
is-my-node-vulnerable
is officially recommended by Node.js, it would be better to have as less dependencies as possible.Describe the solution you'd like
Use native options of dependencies when available
Additional context
Discussion on Twitter https://x.com/styfle/status/1847469788236255562
The text was updated successfully, but these errors were encountered: