Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upDefine globals only for a specific directory #462
Comments
This comment has been minimized.
This comment has been minimized.
|
Your options are:
Standard isn't going to add |
feross
added
the
question
label
Mar 19, 2016
feross
closed this
Mar 19, 2016
lock
bot
locked as resolved and limited conversation to collaborators
May 10, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ilearnio commentedMar 18, 2016
I have
src/clientandsrc/serverdirectories in my project. The one is for the client side (WebPack), the second one is for a Node backend. On the backend, I am using some global variables (e.gROOT_DIR), that I don't have on the client. How do I tell standard to allow to use these globals only on the backend?My package.json config for standard looks like so:
It would be nice to have something like
.standardrcthat might be placed into any children directory and would inherit settings from other.standardrcfiles that are located in parent directories. But it seems it only supports for a single package.json and doesn't look back for other parentspackage.jsons. I tried to create asrc/server/package.jsonand it works but that way I need to duplicate all the settings and then add some more options. It might go as a temporal solution, but it so hackish to create a package.json everywhere I need to add some option to standard. It's there for a different purpose – for Node's NPM