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
I am running deployctl deploy in a deno project with no package.json or node_modules folders. I have allowed deployctl to write configuration to deno.jsonc so that I can run deployctl deploy with no arguments. However when I do this, deployctl complains that the config used differs from config found in deno.jsonc, and offers to overwrite it with --save-config. If I allow this, it adds a duplicate entry to exclude "**/node_modules" on each run:
? Writing to the config file '[...]/deno.jsonc' will remove any existing comment and format it as a plain JSON file. Is that ok? [y/N] n
i I understand. Here's the config I wanted to write:
"deploy": {
...
- "exclude": ["**/node_modules","**/node_modules","**/node_modules"]
+ "exclude": ["**/node_modules","**/node_modules","**/node_modules","**/node_modules"]
}
The text was updated successfully, but these errors were encountered:
I am running
deployctl deploy
in a deno project with no package.json or node_modules folders. I have allowed deployctl to write configuration to deno.jsonc so that I can rundeployctl deploy
with no arguments. However when I do this,deployctl
complains that the config used differs from config found in deno.jsonc, and offers to overwrite it with--save-config
. If I allow this, it adds a duplicate entry to exclude "**/node_modules" on each run:The text was updated successfully, but these errors were encountered: