Not in 3.5 since we are focusing in ddp/transport/reactivity fronts, maybe in 3.6 or later
Noticed this on 3.5-beta.7.
meteor npm update
npm warn Unknown env config "nodedir". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
Also when running this shows up a few times:
(node:61590) Warning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
[Rspack Client Error] npm warn Unknown env config "nodedir". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
[Rspack Server Error] npm warn Unknown env config "nodedir". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
Got it ![]()
Since npm 11.2.0, npm warns when it sees unknown environment configs (npm/cli#8153). NPM_CONFIG_NODEDIR now triggers that warning because nodedir is a node-gyp config, not an npm one. npm also warns that this will stop working in the next major version
3 Likes