Skip to main content
On this page
View Page as MarkdownOpen the Markdown file in a new tabOpen in ClaudeAsk Claude about this pagellms.txtMachine-readable index of these docs for AI tools

deno remove

deno remove removes dependencies from your project's configuration file. It is the inverse of deno add.

Basic usage Jump to heading

Remove a package:

›_
deno remove @std/path

Remove multiple packages at once:

›_
deno remove @std/path @std/assert npm:express

Where dependencies are removed from Jump to heading

deno remove will look at both deno.json and package.json (if present) and remove the matching dependency from whichever file it is found in.

Removing a dependency does not delete it from the global cache. To reclaim disk space, see deno clean.

Removing a global executable Jump to heading

Pass --global (or -g) to remove a globally installed executable script, the same as deno uninstall --global:

›_
deno remove --global serve

A global removal targets a single executable, so you cannot combine --global with multiple names. Use --root to target a custom installation root.

Command line usage:
remove

Remove dependencies

Options Jump to heading

--cert
Jump to heading

Load certificate authority from PEM encoded file.

--config, -c
Jump to heading

Configure different aspects of deno including TypeScript, linting, and code formatting. Typically the configuration file will be called deno.json or deno.jsonc and automatically detected; in that case this flag is not necessary.

--frozen-lockfile
Jump to heading

Error out if lockfile is out of date.

--global, -g
Jump to heading

Remove globally installed package or module.

--import-map
Jump to heading

Load import map file from local file or remote URL.

--lock
Jump to heading

Check the specified lock file. (If value is not provided, defaults to "./deno.lock").

--lockfile-only
Jump to heading

Install only updating the lockfile.

--min-dep-age
Jump to heading

(Unstable) The age in minutes, ISO-8601 duration or RFC3339 absolute timestamp (e.g. '120' for two hours, 'P2D' for two days, '2025-09-16' for cutoff date, '2025-09-16T12:00:00+00:00' for cutoff time, '0' to disable).

--no-check
Jump to heading

Skip type-checking. If the value of "remote" is supplied, diagnostic errors from remote modules will be ignored.

--no-config
Jump to heading

Disable automatic loading of the configuration file.

--no-lock
Jump to heading

Disable auto discovery of the lock file.

--no-npm
Jump to heading

Do not resolve npm modules.

--no-remote
Jump to heading

Do not resolve remote modules.

--node-modules-dir
Jump to heading

Selects the node_modules directory mode for npm packages (not a path). One of: auto (create a local node_modules directory and install npm packages into it), manual (use the existing local node_modules directory, do not modify it), none (do not use a local node_modules directory; resolve npm packages from the global cache). Defaults to auto when the flag is passed without a value.

--node-modules-linker
Jump to heading

Sets the linker mode for npm packages (isolated or hoisted).

--package-json
Jump to heading

Force using package.json for dependency management instead of deno.json.

--reload, -r
Jump to heading

Reload source code cache (recompile TypeScript). With no value, reloads everything. Pass a comma-separated list of specifiers to reload only those modules; npm: reloads all npm modules; npm:chalk reloads a single npm module; jsr:@std/http/file-server,jsr:@std/assert/assert-equals reloads specific modules.

--root
Jump to heading

Installation root.

--unsafely-ignore-certificate-errors
Jump to heading

DANGER: Disables verification of TLS certificates.

--vendor
Jump to heading

Toggles local vendor folder usage for remote modules and a node_modules folder for npm packages.

Last updated on

Did you find what you needed?

Edit this page
Privacy policy