-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[Meteor 3] "meteor node" use the old node 14 instead of 20 #13146
Comments
Are you running the first command in the app directory? If it is outside I believe Meteor will return the Node version for the latest recommended version (so for Meteor 2.15). |
All the commands are run in the same directory aka the meteor app directory. It does this in all our meteor app, even with the repo we've made for another bug that you can clone to test: https://github.com/acemtp/meteor3reactbug When you execute those commands, you don't have the same output? ❯ pwd
/Users/vialec75/tmp/meteorbug3
❯ ls -la
total 32
drwxr-xr-x 12 vialec75 staff 384 May 17 14:48 .
drwxr-xr-x 6 vialec75 staff 192 May 17 18:37 ..
drwxr-xr-x 14 vialec75 staff 448 May 22 08:32 .git
-rw-r--r--@ 1 vialec75 staff 14 May 17 14:03 .gitignore
drwxr-xr-x 10 vialec75 staff 320 May 17 14:06 .meteor
-rw-r--r--@ 1 vialec75 staff 2105 May 17 14:53 README.md
drwxr-xr-x 4 vialec75 staff 128 May 17 14:47 bin
drwxr-xr-x@ 3 vialec75 staff 96 May 17 13:47 client
drwxr-xr-x 11 vialec75 staff 352 May 17 14:48 node_modules
-rw-r--r-- 1 vialec75 staff 2476 May 17 14:03 package-lock.json
-rw-r--r-- 1 vialec75 staff 459 May 17 14:03 package.json
drwxr-xr-x 3 vialec75 staff 96 May 17 14:42 packages
❯ meteor node -v
v14.21.4
❯ meteor --version
Meteor 3.0-rc.1
❯ cat .meteor/release
METEOR@3.0-rc.1 |
After investigating we found that if you used For now, you can delete |
Indeed, I use the original way to install Meteor (since I'm an original fan < Meteor 0.5). I was never a big fan of the installation of Meteor with npm but anyway, thanks for the finding a workaround! |
We found out that you have to make sure the bundle for the release version of the app is present. So running |
I use meteor 3 rc1 and there's some incoherence as you can see, "meteor node" and "meteor npm" commands still use node 14
"meteor node" uses node 14
"meteor shell" uses node 20
I want to update a npm package that is not compatible with node 14, it displays false warning. In the end, it seems that it still install the latest version of the package but it's unclear.
For example, try to install the npm package discord.js:
The text was updated successfully, but these errors were encountered: