Closed agallant closed 7 years ago
Assigning you all as FYI and consensus check - freedom.js has been pretty stable, and I think locking down the dependencies is a good bet. If anyone has objections please let me know by early next week - I intend to cut a release Wednesday morning at latest and merge this before doing so.
seems reasonable. :+1:
On Fri, Oct 07, 2016 at 12:39:52PM -0700, soycode wrote:
Assigning you all as FYI and consensus check - freedom.js has been pretty stable, and I think locking down the dependencies is a good bet. If anyone has objections please let me know by early next week - I intend to cut a release Wednesday morning at latest and merge this before doing so.
You are receiving this because you were assigned. Reply to this email directly or view it on GitHub: https://github.com/freedomjs/freedom/pull/330#issuecomment-252343018
Hrm, that said it seems like "just add npm-shrinkwrap.json" breaks fresh installation in CI. Will update once I figure out the conflict.
Should be resolved - fsevents
is an optional OSX-specific package that gets thrown in when you use npm on a Mac. Did npm install --no-optional
instead of the regular npm install
before shrinkwrapping, and now the result should be Linux-friendly.
The actual error for future search friendliness - "Not compatible with your operating system or architecture: fsevents@1.0.14"
Just to update/document - the plan is to merge this, cut a release, do similar bumping/freezing of the freedom flavors and cut those releases as well. I'll be working with @rajasagashe as he'll be taking over some of this (though his immediate focus will be node-wrtc related).
Fix #311
Dependencies are fairly fresh, things that are held back are chosen on purpose (so that build/tests still work).