🚀 Meteor 3.5-beta: Change Streams & Performance improvements

announce releases
61

Not in 3.5 since we are focusing in ddp/transport/reactivity fronts, maybe in 3.6 or later

62

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.
63

Got it :+1:
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
65

HI,

For my information, when is beta.8 planned?

66

Yeap, right after the official release of 3.4.1. I’m not launching it in parallel so I don’t compete for testers and attention. Probably beta.8 will be the last one

2 Likes
67

@italojs

I upgraded WeKan to Meteor 3.5-beta.7 and Node.js 24.14.1. Does someone know how to fix rspack errors at these GitHub Actions?

68

Have you tried to run meteor update --npm before running the app or tests followed by meteor npm install?

You either run that as part of your GA pipeline or just ensure when you update locally you do it after upgrade Meteor version and commit any npm dependencies bump happened if any.

I’d apply it to GA anyway similarly as done for Docker envs:

(meteor update --npm 2>/dev/null || true) && meteor npm install

2 Likes