feat(cli): deno add --no-save and --save-optional#36039
Merged
Conversation
Adds two `deno add` / `deno install` flags for parity with npm (closes #36037): - `--no-save` installs the package(s) into `node_modules` and the lockfile without writing them to `deno.json` / `package.json`. - `--save-optional` / `-O` writes the package to `optionalDependencies`. Deno's installer does not materialize `optionalDependencies` from `package.json`, so optional packages (and `--no-save` packages) are installed directly via a new `additional_roots` field on `CacheTopLevelDepsOptions`, keeping `--save-optional` at parity with `--save-dev`.
bartlomieju
added a commit
that referenced
this pull request
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
deno addcould not install a package without declaring it, and had no wayto write to
optionalDependencies, which meant tools that translate installcommands between package managers (e.g. npm-to-yarn) could not faithfully
express
npm install --no-saveornpm install -O. This adds both flags todeno addanddeno install <pkg>, matching the npm short forms-Ofor--save-optional.--no-saveresolves and installs the package intonode_modulesand thelockfile but leaves
deno.json/package.jsonuntouched.--save-optional/
-Owrites the package tooptionalDependencies. The three placement flags(
--dev,--save-optional,--no-save) are mutually exclusive.Deno's installer does not currently materialize
optionalDependenciesfrompackage.json(the resolved package.json deps only cover dependencies anddevDependencies), so optional and
--no-savepackages are installed directlyas extra graph roots via a new
additional_rootsfield onCacheTopLevelDepsOptions. This keeps--save-optionalat parity with--save-dev, which installs on add. Teaching the installer to honoroptionalDependencieson its own is left as a follow-up.Closes #36037