VulcanJS/vulcan-next

Improved pattern for public config management

Opened this issue · 0 comments

Is your feature request related to a problem? Please describe.
Collocate all environment varaible into a nextPublicConfig.ts file.
Describe the solution you'd like

It would behave as a replacement to Next public RUNTIME config, which is actually not suited for configuration (legacy feature left there for legacy reason, see incoming article on Vulcan blog for more details)

It can be validated in _app at start/build time so we can tell if the server have the correct values.