Why does the MDG group not talk about which version of node to use?

mrphilbert · December 6, 2015, 10:40pm

It seems that a lot of people have issues with node versions and package incompatibility.
Nowhere in the examples does it mention which version of node to use to ensure a stable development environment.

Please, instead of starting all examples with “install meteor”, start off with “make sure this " " version of node is installed”. Or better yet, make a list matching meteor and node versions.

That would eliminate a lot of confusion and maybe solve a good percentage of posts in the forum.

Thanks

P.S. What is the current version of node that people are using with 1.2?

shock · December 6, 2015, 10:42pm

I dont know, Meteor have it’s own so I do not need to care.

lampe · December 6, 2015, 11:14pm

meteor 1.2.1 uses node v0.10.40

on linux you can finde the node bin in:

~/.meteor/packages/meteor-tool/1.1.10/mt-os.linux.x86_64/dev_bundle/bin for meteor 1.2.1

mrphilbert · December 7, 2015, 12:26am

Thank you sir. That is quite helpful.
It is a far cry from shock’s rather snide answer.

I do appreciate it.

SkinnyGeek1010 · December 7, 2015, 1:01am

@mrphilbert

You’ll want to checkout the history.md on the MDG repo. It will tell you the latest Node you can use for each major version (1.2 specifies but 1.2.3 does not). In general you should always read this change log every time you upgrade to make sure there are not other breaking changes.

Searching for 0.10 with the find command works pretty well (until we get to upgrade to 4.x!)

github.com

meteor/meteor/blob/devel/History.md

## v.NEXT

* The `meteor-babel` npm package (along with its Babel-related
  dependencies) has been updated to version 7.0.0-beta.35, a major update
  from Babel 6. Thanks to the strong abstraction of the `meteor-babel`
  package, the most noticeable consequence of the Babel 7 upgrade is that
  the `babel-runtime` npm package has been replaced by `@babel/runtime`,
  which can be installed by running
  ```js
  meteor npm install @babel/runtime
  ```
  in your application directory. There's a good chance that the old
  `babel-runtime` package can be removed from your `package.json`
  dependencies, though there's no harm in leaving it there. Please see
  [this blog post](https://babeljs.io/blog/2017/09/12/planning-for-7.0)
  for general information about updating to Babel 7 (note especially any
  changes to plugins you've been using in any `.babelrc` files).
  [PR #9440](https://github.com/meteor/meteor/pull/9440)

* The previously served `/manifest.json` application metadata file is now

This file has been truncated. show original

Hope this helps!

martijnwalraven · December 7, 2015, 5:43am

@mrphilbert Meteor does not use a globally installed node, but bundles its own version (which also has support for fibers compiled in). So there is no need to install your own node before installing Meteor.

SkinnyGeek1010 · December 7, 2015, 4:22pm

Good point. it’s only needed if you’re deploying your app (except for Galaxy).

cstrat · December 7, 2015, 10:48pm

This is not my experience.

I’ve had issues on my DO server because I had node directly installed at the 0.10.36 and when upgrading it required 0.10.40. My deployments failed until I upgraded the node instance installed on my server…

See here: