Closed greggman closed 6 years ago
You are correct; this is an unfortunate problem in the semver
package we are using. I really need to figure out some way to replace or work around that problem.
Fixed by 73241f38dff8bc6b1af586f81e4b112e139d7648
Fix not sufficient... back to the drawing board.
Another problem with the 1.6 release, is that it requires a newer version of Node. Perhaps make the NODE version configurable? Or extract it from meteor node -v
?
@smeijer That's a good idea. Are you up to writing it? In any case, please do create a new issue about it.
I tried using meteor 1.6 with
And got this message:
I'm guessing it wants me to put in 1.6.0? or 1.6.0.0 but meteor itself, after upgrading from 1.5.2.2 just says 1.6 when using
meteor version
another issue seems to be the node version. This container references node 4 but meteor 1.6 seems to need node 8