Remove app-module-path-node dependency
martijnwalraven opened this issue · comments
We tracked down an issue with the Todos app to the use of app-module-path-node in this package. Because app-module-path-node patches Node internals to modify module resolution, the Cordova code ends up with a faulty version of a package installed in the app's node_modules directory instead of the local one.
Modifying module resolution in this way could potentially break other parts of the build tool too, as it allows apps to override versions of packages we ship in the dev bundle.
Is there any way you can get rid of this dependency? I'm not sure what made you rely on this behavior, but we may be able to help you find a better way to accomplish this without globally modifying Node internals.
This is a remnant of the old version based on meteorhacks:npm If I'll be able to read from /node_modules it shouldn't be a problem to remove it. And I think this is possible without this dependency. I'll try it asap. Thanks for the info.
Great, thanks for looking into this!
From minify-css.js plugin I try to get to the main node_modules in the app. So I try to do something like: path.resolve(process.cwd(), 'node_modules'); to be able to require PostCSS plugins installed in the app. And in the minify-css.js I want to do: Npm.require(appsNodeModulesPath + '/' + pluginName). It seems to be good path, but it stucked at:
While minifying app stylesheet:
module.js:338:15: Cannot find module
'/home/jul/workspace/meteor/postcss-demo/packages/meteor-postcss/.npm/plugin/minifier-postcss/node_modules/home/jul/workspace/meteor/postcss-demo/node_modules/postcss-safe-parser/'
So the path is not resolved as it should here in module.js :/
Also I wonder how will it behave when downloaded from Atmosphere.
Any ideas how to Npm.require from main node_modules in the package's minify-css.js plugin? :)
Thanks.
I've tried it in many different ways, I can only think of relative path to node_modules but then it will not work when bundled. I thought that it will be simpler :/ It appears that Node can't resolve this in its module.js.
And of course with app-module-path it is possible because it overwrites Module._nodeModulePaths, anyway this whole approach to PostCSS isn't a very good solution. It is rather a hacky way to achieve something which is really useful in the Front-end world, although underestimated ;)
Unfortunatelly for me it's hard to say what we could do with this problem.
@juliancwirko can you provide instructions on how to reproduce what you are seeing (maybe push a branch and I'll play with it?)
@benjamn it seems that passing an absolute path into Npm.require or our require() doesn't work. I'm not sure if that's by design or otherwise, but it'd be an easy workaround for this problem if there was a way to do so.
One way would probably be to create an npm package that is simply a requirer:
// in the requirer npm package
module.exports.require = require;
// in the app / build plugin
require('requirer').require(absolutePath);Why would that work (I think)? Because inside an npm package, require is just npm's default
I've been scratching my head over non-informative Cordova build errors and through a ton of trial and error I've been able to isolate the errors to this package. Removing this package from my project results in reliable, successful builds on all platforms. For more information on the issues I ran into, please refer to this issue posted on the Meteor issue tracker.
If you need any additional information from my end, I am happy to oblige.
I can confirm that npm install shelljs@0.5.3 seems to put a bandaid over this problem. Any updated guidance on how to handle this issue?
Hmm, this seems to have dropped off the radar. Will surface it again.
@juliancwirko do you want to try using the new inputFile.require(id) API in the 1.3.3 beta: meteor/meteor#7073 (comment) ?
Also, I think that there's a uglier way to do this that would work in older 1.3 versions too, is that correct @benjamn?
@juliancwirko why do you not have access to an input css file?
@tmeasday I probably misunderstood this. I'll try to explain. I'll use your reproduction repo.
So, You add aws-sdk here so it should be installed on the application level. Then you want to import it in the plugin (in the package) here. Here at the beginning of the file you aren't in the context of the input file. Am I right?
Could you rewrite your reproduction repo with these changes? Or maybe you will be able to explain it a a little bit? It would be very appreciated. Many thanks.
I mean, sure it doesn't directly solve the problem as stated, but a build plugin doesn't need to import until it has some files to operate on, right?
The reason it works like this is because a build plugin can also be set to operate on a package, so you can't just import the one time blindly.
Ok, I think I understand it now. So I should require all plugins in the loop with every single css file. I probably could rewrite it that way. I wonder if it will be fast enought. Let's supose we have 15 PostCSS plugins and 30 css files. It gives 450 require calls each app rebuild ;) But maybe it is still performant. I am not sure.
I'm not sure what makes the most sense, but FYI if you require something with the exact same path, it's a no-op.
Ok, cool. So I try to rewrite it soon. Thank you :)
@tmeasday one more problem ;) I think that this is implemented only in compiler-plugin.js and not in the minifier-plugin.js
Unfortunatelly I need it in the minifier-plugin.js
any updates on this issue? We're still not able to make a build with Meteor 1.3.5.1 :/
I can confirm that npm install shelljs@0.5.3 seems to put a bandaid over this problem.
@v3rron Try installing shelljs@0.5.3. This allowed me to build again.
This is addressed by #32, because it uses another regular NPM package to do importing. This in fact is then just a fancy requirer @tmeasday was talking about.
The issue is that I am observing some random failures to find a node module. Restarting Meteor helps. But it is just unclear why it happens that this package then cannot find it. I do not modify node_modules at all. It is just random.
@mitar ok, I'll test it and release new major version with your changes, thanks!
I'll close it. Feel free to comment here if needed. Thanks!
I think I managed to break this package. Sorry. It worked when I had fork inside packages, but now that it is published, it does not really work. The issue is that @tmeasday's idea does not really work. I made the NPM package print module.paths before require call and you will see why it does not:
[ '/home/mitar/.meteor/packages/juliancwirko_postcss/.2.0.1.1h3wuhm.m6do++os+web.browser+web.cordova/plugin.minifier-postcss.os/npm/node_modules/meteor/minifier-postcss/node_modules/postcss-load-plugins/lib/node_modules',
'/home/mitar/.meteor/packages/juliancwirko_postcss/.2.0.1.1h3wuhm.m6do++os+web.browser+web.cordova/plugin.minifier-postcss.os/npm/node_modules/meteor/minifier-postcss/node_modules/postcss-load-plugins/node_modules',
'/home/mitar/.meteor/packages/juliancwirko_postcss/.2.0.1.1h3wuhm.m6do++os+web.browser+web.cordova/plugin.minifier-postcss.os/npm/node_modules/meteor/minifier-postcss/node_modules',
'/home/mitar/.meteor/packages/juliancwirko_postcss/.2.0.1.1h3wuhm.m6do++os+web.browser+web.cordova/plugin.minifier-postcss.os/npm/node_modules/meteor/node_modules',
'/home/mitar/.meteor/packages/juliancwirko_postcss/.2.0.1.1h3wuhm.m6do++os+web.browser+web.cordova/plugin.minifier-postcss.os/npm/node_modules',
'/home/mitar/.meteor/packages/juliancwirko_postcss/.2.0.1.1h3wuhm.m6do++os+web.browser+web.cordova/plugin.minifier-postcss.os/node_modules',
'/home/mitar/.meteor/packages/juliancwirko_postcss/.2.0.1.1h3wuhm.m6do++os+web.browser+web.cordova/node_modules',
'/home/mitar/.meteor/packages/juliancwirko_postcss/node_modules',
'/home/mitar/.meteor/packages/node_modules',
'/home/mitar/.meteor/node_modules',
'/home/mitar/node_modules',
'/home/node_modules',
'/node_modules' ]
See, search path is from installed module inside home directory, not from inside my package app. So this is why require does not find packages inside node_modules inside the app.
Yes, I've checked it only locally too ;)
Ok, I'll merge that. Thanks.
After more battling with this, it seems this is not possible at the moment because of the limitation in Meteor. I opened an issue about this: meteor/meteor#9865
My proposal is that we revert for now to using app-module-path-node and reopen this issue and wait for better times when this will be fixed in Meteor.