feat: generate d2.config.json from d2.config.js #471
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This generates a new config file
d2.config.json
from the compiled application config (merge ofpackage.json
andd2.config.js
). The.json
file is placed at the root of the application output, next tomanifest.webapp
, which it will eventually replace. The data in this config file is necessary to enforce immutable application slugs, parse version numbers, and other things when publishing to the App Hub.Here is a sample
d2.config.json
output generated fromexamples/simple-app
: