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
Accept npm's config variables in package.json #1711
Comments
Isn't it a duplicate of your own issue? :) #1626 Just a note: You can use That said, I really like this feature, and it should be as easy to implement as allowing Would you mind preparing PR with tests for https://github.com/bower/config ? |
@sheerun thanks for the support. Actually I believe this complements #1626 in a way that would partially resolve one of its issues. I have managed to allow https://github.com/zanona/config/commit/b2bbd68fc4db30164cd4556c31686d6e0fd27902 Please let me know if you have an idea on what would be the proper way to link that to the main test thread. |
Hey. For filesystem tests I think you can use: https://github.com/tschaub/mock-fs I also think it's possible to edit |
hey @sheerun let me know if that's ok now. If so, I can then submit a PR. cheers |
Allow NPM config variables. Resolve #1711
It would be really awesome if we could be able to set NPM's config object for setting bower configurations as well, in addition to env vars and having a
package.json
like:package.json
This would be it really good for development and continuous integration as well, without having to reset these variables for every
bower
command called (usingbower --config
flag). Simply runningnpm install
would then inherit all those configurations.The text was updated successfully, but these errors were encountered: