Suggestion: support reading environment variables from a file. about cross-env HOT 9 CLOSED

Thanks for thinking this through @knpwrs, but I'm not really interested in expanding this library to do anymore than it does currently. If you'd like to do more with it then you can feel free to fork it, but I'd like to keep this small and specific.

from cross-env.

@knpwrs I just created that very lib because I needed the same thing for a sequelize PR. You can find my util here env-cmd

@kentcdodds Thank you so much for creating cross-env and inspiring me to create my own with new functionality I needed 😄

from cross-env.

Wonderful! Thank you!

from cross-env.

Would you like to add something to the README? Like a Related Projects section?

from cross-env.

Yeah that would be great! I can make a PR for that and I will add a similar section to env-cmd's README as well.

from cross-env.

@toddbluhm You beat me to it! I was going to create use-env as soon as I needed it.

from cross-env.

@knpwrs I actually really like that name. Wish I had thought of it before.

from cross-env.

You took a slightly different approach than I was going to take. I was going to make cross-env a peer dep and go after the crossEnv function exported from cross-env/dist/index.js (since main in package.json is set to src/index.js). Though I suppose that may not technically be a public api so that may or may not have been a good idea.

from cross-env.

I seriously considered going that route at first too, but then I just wanted the fun of writing it all from scratch, along with minimal dependencies. Weirdly enough, I actually enjoy writing parsing code.

from cross-env.