Alex Guerra
Alex Guerra
Environment variables have to be compiled in because things like `NODE_ENV` lead to tons of dead code elimination, so whatever solution you're looking for will probably need to coexist with...
[Here's](https://gist.github.com/heyimalex/ec48d03d8c9ab581b9ebe88e2b6ec093) a build script to do this. Usage: - Define some variables in your `.env` with the prefix `REACT_APP_RUNTIME_` - Run the build script. It should run the regular react-script...
@The-Loeki I think that potentially breaks sourcemaps and caching in weird ways. Even if you take out the service worker stuff, you have to remember to not set far future...
@The-Loeki Everything in `/static/` has a content hash appended to the filename so that you can safely set far-future caching headers. When you modify those files using sed, the contents...
I think your solution works well. The use case for build time environment variables is that their values can be used during optimization. For example, all code wrapped in `if...
You could try setting the `__webpack_public_path__` magic variable.
Sorry, I'll take a look tonight!
Sorry, I'll try and find some time soon! RE: Immutable, right now it's a devDependency, so people who `npm install` don't need to have it installed. Using it in the...
My thoughts on this right now are I can cut a release exposing the functions you need, but adding type definitions seems too difficult. If you want to try and...
Released 1.0.6, lmk if that solves your problem