Skip to content
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

Release 1.4.3.1 #8363

Merged
merged 11 commits into from Feb 14, 2017
Merged

Release 1.4.3.1 #8363

merged 11 commits into from Feb 14, 2017

Conversation

benjamn
Copy link
Contributor

@benjamn benjamn commented Feb 13, 2017

Whereas Meteor 1.4.2.7 fixed #8349 by reverting npm from version 4.1.2 to version 3.10.9, this release fixes the same bug by keeping npm@4.1.2 but dealing with the consequences of this breaking change.

This release will also fix #8312, which could have been fixed independently (since it involves only packages), but was easier to fix after fixing the problem described above.

Note that Meteor 1.4.3 has been published, but we have not (and will not) "recommend" it, because of the problem with upgrading npm dependencies of Meteor packages.

@benjamn benjamn added this to the Release 1.4.3.1 milestone Feb 13, 2017
@benjamn benjamn changed the base branch from devel to master February 13, 2017 23:07
Although we thought the upgrade from `npm` 3.10.9 to 4.1.2 was worthwhile
and safe, this breaking change proved problematic:
https://github.com/npm/npm/blob/latest/CHANGELOG.md#no-more-partial-shrinkwraps-breaking

Specifically, if a Meteor package calls `Npm.depends` in a way that
disagrees with the contents of `.npm/package/npm-shrinkwrap.json` file,
Meteor will create a partial shrinkwrap file in order to install the
correct top-level npm dependencies, but transitive dependencies of the
package will no longer be installed.

This was fixed in Meteor 1.4.2.7 by reverting the upgrade of npm, but
Meteor 1.4.3.1 will keep npm@4.1.2 and fix the consequences.
Thanks to @abernix for fixing this Babel/Babylon bug in Reify:
benjamn/reify#62

Fixes #8312.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants