You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 5, 2022. It is now read-only.
It'd be nice to utilize some form of templating for the various image's package.json in order to increase maintainability, and reduce duplication. This will make it much easier to customize the different images while keeping a standard base.
We could use a template/replacenent variable system to generate each application's package.json from an application-specific template. Replacement variables would be replaced by an arbitrary value for a given run, depending on some settings.
With such a mechanism, the resolutions block of each application's package.json could be defined in a single place and injected everywhere.
Description
It'd be nice to utilize some form of templating for the various image's
package.json
in order to increase maintainability, and reduce duplication. This will make it much easier to customize the different images while keeping a standard base.We could use a template/replacenent variable system to generate each application's package.json from an application-specific template. Replacement variables would be replaced by an arbitrary value for a given run, depending on some settings.
With such a mechanism, the resolutions block of each application's package.json could be defined in a single place and injected everywhere.
Something like this could help:
https://www.npmjs.com/package/envsub
Example
Additional Information
The text was updated successfully, but these errors were encountered: