feat(action): auto-discovery of deno.json and auto-populate defaults #351
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.
Closes #350
PS: the diff is not that huge, most of the changed files are due to the addition of a jsonc parser package in the node_module directory
Features:
deno-config
deno.json
/deno.jsonc
from the root fileproject
defaults to"deploy.project"
entrypoint
defaults to"deploy.entrypoint"
exclude
defaults to"deploy.exclude"
include
defaults to"deploy.include"
import-map
defaults to"importMap"
"import"
field, it is saved as JSON toimport-map-autogen-temp
, allowing use of JSONC deno config file since using them directly inimport-map
would cause parsing issues if there is commentsChanges:
jsonc
as dependencydeno-config
featureSide note: since the deno config is discovered it allows for a really clean workflow, and also if user test their deployment from the CLI version (which populates the "deploy" section of deno config) then they'll have the same "experience" on the GA version.
It may or may not be considered a breaking change, since the config file was totally ignored before, so it could change they way if work if inputs were explicit