meteorNpm portable file marker causes npm shrinkwrap to fail on organization npm modules #7296
Comments
Same bug as storybookjs/storybook#181 |
What's the progress on this @benjamn ? any timeline for when it'll be fixed? This is super annoying, and slows down both local development and deployments to our development environments |
benjamn
added a commit
that referenced
this issue
Jun 30, 2016
Also clean up any existing misplaced .meteor-portable files. Fixes #7296.
benjamn
added a commit
that referenced
this issue
Jul 1, 2016
Also clean up any existing misplaced .meteor-portable files. Fixes #7296.
I'm planning a Meteor 1.3.4.2 bug fix release, with this fix included. Please run |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As you can see, we have a npm module installed that is not in a top level directory under
node_modules
due to the fact that this belongs to an npm organization.https://www.npmjs.com/package/@workpop/optimistic-middleware
Before running
meteor build
, the.meteor-portable
does not exist in this directory andmeteor npm shrinkwrap
works as expected. After runningmeteor build
, this.meteor-portable
file causes subsequent shrinkwrapping attempts to fail as this file is not in a npm module directory but is undernode_modules
.meteor-portable
should not be placed if the directory is not a npm module. Usually top level directories innode_modules
are, but not always.meteor/tools/isobuild/meteor-npm.js
Line 261 in d71ebb6
The text was updated successfully, but these errors were encountered: