Meteor 1.6
Meteor 1.6. is already here. Apiko team has tested it on practice and now we want to share these findings with you.
Let’s dive right in!
We have compared old and new Meteor while working on the current project. The results are the following.
There is an issue with package-lock file in npm 5 for 5.6.0. version. The problem is that different packages may be added to the operational systems, e.g. FSEvents on Mac OS.This package will be deleted as soon as the “Meteor npm install” is conducted. It leads to the conflicts while file merging with version control systems. However, in Meteor, npm will be renewed in 1.6.1 version, that’s why this can be ignored yet.
Not all Meteor packages on Atmosphere that use npm dependencies function well enough. It happens because of the rapid changes in Node versions.
Some functions may be deleted from the updated version or the syntax may be partially changed. That’s why it will take some time until community will adapt its packages to updated Meteor. However, most of the frequently used packages are already adapted. In addition, you can directly use npm packages without Meteor-wrappers.
We are so excited about new Meteor version and hope you feel the same.
In case you share our tech passion to Meteor, these articles will come in handy for you.
Enjoy it and feel free to share with us your Meteor experience!
Originally published at apiko.com on December 27, 2017.