-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
meta: Indicate compatible Node.js versions #152
Conversation
2dee47c
to
c8819de
Compare
I don't think that's correct. We're likely supporting v16, v14, v12 etc. Noble-hashes minimum is v16, but curves are usable without hashes. Esp if user brings their own hashes. |
Oh! Do you agree that it would make sense to rewrite the tests to be runnable under these Node.js versions, then, so compatibility can be verified? Currently they contain syntax that make the test suite require 18+. |
|
I don’t know how to test v14, because nodejs 14 on arm macs is unavailable. We are falling back to built in nodejs crypto instead of less supported webcrypto AFAIR. Also there is no hard dependency on webcrypto in most places. Lib can be used without randomness.
such as? |
For consideration: |
The new syntax for loaders but that can be addressed!
It looks like it should be doable now? nodejs/node#40127 I guess in any case if that is a concern it might make sense to test macOS in CI also? |
c8819de
to
014c9ba
Compare
@paulmillr Updated to indicate support also for v14, v16 (b69a8bb). Indicating only support for at least latest patch releases for When attempting to run on Node.js v12, I get syntax error on the unsupported Is it worth it to fix support for v12? And in any case could be worth indicating what's currently expected to work? :) |
|
added manually |
Indicate compatible and supported Node.js versions in package manifest via
engines.node
.