A way to define custom environment variables

This may be a tiny yet non-obtrusive solution. Allow a custom .env.js file that exports a key value pair used for custom webpack defines. I guess this wont be useful for many, since you any way get to refer to NODE_ENV but I also used this for defining a publicPath from an environment variable or defaulting to root. (useful for me as i had to run the same app for multiple quizzes, so I could build the frontend without configuring anything and having sane default not-get-in-the-way configs while development and testing)

[dmi3y]

I might have one. Let’s say there is api server running at different enviroments like so:

• dev.api.foobar.com
• prod.api.foobar.com

And I’m building SPA which supposed to use CORS and being hosted anywhere, just like static site.

And such I want to supply dev/prod absolute paths for different versions of SPA.

Hope this makes sense.

[mxstbr]

I think at that point you have a very advanced use case and ejecting is the way to go. I don’t think adding .env support by default is really necessary, since most users will never need it?