Open jetzezoethout opened 8 months ago
punycode is transtive dependency of eslint. Even when using latest version of eslint (8.52.0). Please also notice that eslint is dev dependency.
If you want to you can similar issue to eslint library.
ravendb@5.4.2 C:\workspaces\client-node\v5.4
`-- eslint@8.52.0
`-- ajv@6.12.6
`-- uri-js@4.4.1
`-- punycode@2.3.0
In node-fetch I don't see dependency to punycode (https://github.com/node-fetch/node-fetch/blob/main/package.json)
Thanks for your quick reply! I'm aware that punycode is a transitive dependency of eslint, but dev dependencies shouldn't cause runtime warnings in node. I did a bit more digging: running node with the --trace-deprecations
flag shows that punycode is used in whatwg-url
, which enters through node-fetch:
$ npm list whatwg-url
Test@ ~/Documents/Test
└─┬ ravendb@5.4.1
└─┬ node-fetch@2.7.0
└── whatwg-url@5.0.0
ok we will investigate that with node 21. Thanks :)
For the eslint dependency: https://github.com/garycourt/uri-js/pull/95
Running a project using ravendb on the newest version of node (v21) yields a deprecation warning.
Minimal example
package.json
main.js
After running
npm i
, we get the following behaviour:On older versions of node, the same warning can be seen by adding the
--pending-deprecations
flag.The dependency on
punycode
seems to enter throughnode-fetch
v2. Simply updating to v3 might do the trick.Specific version information