Cannot Deploy to Galaxy from Mac (Due to binary NPM modules in dev dependencies)
tomitrescak opened this issue · comments
Blog app uses some binary modules which prohibit it from being deployed to Linux servers from non Linux computers such as my Mac. For example a binary module is:
> fsevents@1.0.11 install /Users/tomi/Documents/Programming/Github/mantra-sample-blog-app/node_modules/fsevents
> node-pre-gyp install --fallback-to-build
[fsevents] Success: "/Users/tomi/Documents/Programming/Github/mantra-sample-blog-app/node_modules/fsevents/lib/binding/Release/node-v47-darwin-x64/fse.node" is installed via remote
mantra-demo@0.3.1 /Users/tomi/Documents/Programming/Github/mantra-sample-blog-app
The only way to develop to Galaxy is to delete the dev-dependency modules and use only the application one as those do not use binary modules. What do you reckon is the best way to deal with that?
One idea would be to use Docker and deploy to Galaxy from docker.
Another would be to keep two versions of node modules and during deployment substitute them.
Both of these solutions seem to me quite heavy ... do you have any better idea?
It seems that the culprit is @kadira/storybook which installs these modules. Maybe it should not be a part of the application bu run from a parent directory?
@arunoda does this even have a solution? It's the fsevents component that is acting up:( exon in Webpack handled this just not sure how.
@tomitrescak Try using the latest Meteor 1.3.2.
It seems this issue is fixed in that.
Yea, when I heard about the binary modules in 1.3.2, made my hear sing;) I'll test it soon and post back
No that's not the case. This issue is fixed in the latest Meteor version. It's not related to binary NPM modules.
But, Meteor bundles all the NPM modules here. So, it's better move all devDependecies to the top level.
@tomitrescak here's the related issue: meteor/meteor#6836