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
Build plugins cannot access peer dependencies in the app #10827
Comments
Reopen of #9865. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Unstale. |
Very unstale, especially if this is the cause of juliancwirko/meteor-postcss not working (can't get it to work at all after 1-2 hours). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still relevant. |
As this issue has not had any activities in the last months... I will be closing it! |
This is still a problem. standard-minifier-css, zodern:melte and possibly other build plugins have to work around it. |
Tested on Meteor 1.6.1.1.
I am observing this with two built plugins:
The issue is that these days many build plugins might allow configuration. For example, in postcss case they allow you to specify which plugins you want to operate on your CSS. So the reasonable approach would be that:
The issue is that plugins often then just try to do
require(name_of_plugin)
. But this fails. The reason why this fails is because plugin seems to be run inside~/.meteor
namespace so resolving walks the tree there and not inside the app.This is even more problematic because during development, if you have package inside
packages
in your app things look like working. But then, once published, they break.The text was updated successfully, but these errors were encountered: