This patch moves the config files into a new config folder, this allows the new config package to detect it and based on a priority list and compute a final config.
The final config is provided to the app via virtual modules that are created on build time and provided to the app during run time.
We define also a new NODE_CONFIG_ENV env variable which is used by the config package to overwrite certain parts of the config for e.g. testing.
This allows us also to clean up any config changes we do in the test suites and have everything in the same place, aka the config dir.
Also since this new env var removes the need for window.PLAYWRIGHT and window.VITEST, I went the extra step and was able to remove all the injections into the window object we did, which is just cleaner.
Added additionally a custom-environment-variables.json mapping file which defines env vars for each of the config options.
Some are pretty straight forward, others require to serialize the values into a json string to be parsed.
The error behavior is pretty gracefully and in all cases always fallback to our default.json file instead of throwing build or run time errors.
This patch moves the config files into a new config folder, this allows the new config package to detect it and based on a priority list and compute a final config.
The final config is provided to the app via virtual modules that are created on build time and provided to the app during run time.
We define also a new NODE_CONFIG_ENV env variable which is used by the config package to overwrite certain parts of the config for e.g. testing.
This allows us also to clean up any config changes we do in the test suites and have everything in the same place, aka the config dir.
Also since this new env var removes the need for window.PLAYWRIGHT and window.VITEST, I went the extra step and was able to remove all the injections into the window object we did, which is just cleaner.
Added additionally a custom-environment-variables.json mapping file which defines env vars for each of the config options.
Some are pretty straight forward, others require to serialize the values into a json string to be parsed.
The error behavior is pretty gracefully and in all cases always fallback to our default.json file instead of throwing build or run time errors.
Separate into more atomic commits and make tests work
Added custom environment variable matcher to allow individual env variables
Create a symlink to make it clear which config our production deployment uses
Add a configure section to the README
Rename module.d.ts declaration
Rebase on top of responsive changes
Rewrite README configuration section and add local config files to gitignore
Remove module.d.ts comment