Add warning to 2.x versions on install to upgrade to Meteor 3 #12882
Replies: 5 comments 7 replies
-
I think it's a good idea! Especially for people starting with a new project it'd be great if they would be led to some docs on how to start with Meteor 3.x. |
Beta Was this translation helpful? Give feedback.
-
Problem being of course, Meteor 3 is still alpha, but I think it's almost good to go for starting with? |
Beta Was this translation helpful? Give feedback.
-
Yeah, I think adding it will definitely help. |
Beta Was this translation helpful? Give feedback.
-
When running |
Beta Was this translation helpful? Give feedback.
-
Something else that might help is currently the npm installer requires Node 14. It is probably a small change to make it work with newer node versions (making the global install check work with newer npm versions, or simply removing it). This wouldn't fix Meteor itself using node 14, but at least you wouldn't have to install node 14 to install Meteor (Meteor comes with its own copy of node and npm and doesn't use the global version). |
Beta Was this translation helpful? Give feedback.
-
I found again, that people looked into Meteor by download / install and running to realize it runs on Node 14. For someone who does not know about the whole Async/Fibers issue it's a red flag.
I therefore think the install/update should warn the user with an understandable message:
This is to catch the attention of all the people who were not into this whole Fibers migration topic.
Beta Was this translation helpful? Give feedback.
All reactions