new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Deno · Reference · all subjects

cli commands

115 notes in this subject, read out of this brain and free to use. This is page 1 of 2.

deno cache command deprecated

deno cache is deprecated. Use deno install instead.

deno install command

deno install is used to install a dependency or a script.

deno uninstall command

deno uninstall is used to uninstall a dependency or a script.

deno remove command

deno remove is used to remove dependencies.

deno outdated command

deno outdated is used to view or update outdated dependencies.

deno why command

deno why is used to explain why a package is in the dependency tree.

deno fmt command

deno fmt is used to format code.

deno info command

deno info is used to inspect an ES module and all of its dependencies.

deno init command

deno init is used to create a new project.

deno jupyter command

deno jupyter is used to run a Jupyter notebook.

deno lint command

deno lint is used to lint code.

deno lsp command

deno lsp is used for language server protocol integration.

deno pack command

deno pack is used to create an npm tarball from the current Deno project.

deno publish command

deno publish is used to publish a module to JSR.

deno test command

deno test is used to run tests.

deno transpile command

deno transpile is used to transpile TypeScript, JSX, or TSX to JavaScript.

deno types command

deno types is used to print runtime types.

deno x command

deno x is used to run an npm or JSR package.

deno serve command

deno serve is used to run a web server.

deno task command

deno task is used to run a task.

deno repl command

deno repl starts a read-eval-print-loop.

Deno CLI subcommand categories overview

The Deno CLI has subcommands organized into four categories: Execution (deno run, deno serve, deno task, deno repl, deno eval), Dependency management (deno add, deno approve-scripts, deno audit, deno bump-version, deno install, deno uninstall, deno remove, deno outdated, deno why), Tooling (deno bench, deno check, deno compile, deno completions, deno coverage, deno create, deno doc, deno deploy, deno desktop, deno fmt, deno info, deno init, deno jupyter, deno lint, deno lsp, deno pack, deno publish, deno test, deno transpile, deno types, deno upgrade, deno x), and Other (unstable feature flags, LSP integration).

deno run command

deno run is used to run a script.

deno jupyter command

The `deno jupyter` command installs and runs Deno's built-in Jupyter kernel that allows you to write JavaScript and TypeScript in Jupyter notebooks.

deno jupyter --install flag

The `--install` flag forces installation of the Deno Jupyter kernel. Deno assumes that the `jupyter` command is available in your PATH.

deno jupyter security limitation

Currently all code executed in the Jupyter kernel runs with the `--allow-all` flag. This is a temporary limitation and will be addressed in the future.

jupyter console --kernel deno

The Deno Jupyter kernel can be used in the `jupyter console` REPL by launching it with `jupyter console --kernel deno`.

Deno Jupyter kernel in VS Code

To use the Deno Jupyter kernel in VS Code, install the VSCode Jupyter extension, create a notebook file with the .ipynb extension, and select Deno from the Jupyter kernels list.

Deno Jupyter kernel in JetBrains IDEs

Jupyter Notebooks are available out of the box in JetBrains IDEs.

deno link command purpose

The deno link command points your project at a local copy of a JSR package so you can develop against it in place of the published version. It is the command-line equivalent of editing the links array in deno.json by hand, and mirrors the workflow of npm link or bun link.

deno link basic usage

To link a local package, pass the path to a local package directory: deno link ../my-local-pkg

deno link package requirements

The target directory must contain a deno.json or package.json with a name field so Deno knows which package it stands in for.

deno link behavior with deno.json

Deno appends the relative path to the links array in the nearest deno.json, creating the array if it does not exist, and then installs dependencies.

deno link import access

The linked package is importable by its bare name, just like a workspace member, so no imports entry is added.

deno link duplicate paths

Linking the same path again has no additional effect.

deno link multiple packages

You can link several packages in one command: deno link ../pkg-a ../pkg-b

deno unlink command

Use deno unlink to stop using the local copy of a linked package: deno unlink ../my-local-pkg

deno list command purpose

The `deno list` command prints the packages your project declares as dependencies. It reads them from the `imports` in `deno.json` and from the `dependencies` and `devDependencies` in `package.json`, resolves each to the version currently in use, and prints them grouped by package, similar to `npm ls` or `pnpm list`.

deno list vs deno info

`deno info` walks the module graph from an entrypoint and reports every file it reaches, while `deno list` reports what the project depends on straight from the manifest without an entrypoint.

deno list usage syntax

The usage syntax for deno list is: `deno list [OPTIONS] [filters...]`

deno list filters

Optional positional `filters` narrow the output by package name and support wildcards and `!` negation, the same matcher `deno outdated` uses.

deno list --depth option

The `--depth <N>` option renders the resolved dependency tree N levels deep, for both npm and JSR packages, read from the lockfile.

deno list --prod option

The `--prod` option shows only production dependencies.

deno list --dev option

The `--dev` option shows only development dependencies.

deno list --recursive option

The `--recursive` option includes the dependencies of every workspace member.

deno list example: list direct dependencies

The command `deno list` lists direct dependencies.

deno list example: show dependency tree two levels deep

The command `deno list --depth 2` shows the dependency tree two levels deep.

deno list example: list production dependencies with filter

The command `deno list --prod "@std/*"` lists only production dependencies whose name starts with `@std/`.

deno lsp command basic usage

The deno lsp command starts the Deno language server. It communicates over stdin/stdout using the Language Server Protocol (LSP). The language server provides features like IntelliSense, code formatting, and diagnostics. This command is not typically run directly by users; editors start it automatically.

deno lsp command syntax

The deno lsp command is invoked with: deno lsp

deno outdated command overview

The outdated subcommand checks for new versions of NPM and JSR dependencies listed in deno.json or package.json files, and displays dependencies that could be updated. Workspaces are fully supported, including workspaces where some members use package.json and others use deno.json.

deno outdated output table columns

The deno outdated command displays a table with four columns: Package (the dependency name), Current (the currently locked version), Update (the newest semver-compatible version), and Latest (the absolute latest version available).

deno outdated --compatible flag

The --compatible flag filters the output to only show packages that have new semver-compatible versions available, excluding packages with no compatible updates.

deno outdated --update flag

The --update flag updates dependencies in deno.json or package.json. By default, it only updates to semver-compatible versions and will not update to breaking versions.

deno outdated --latest flag

The --latest flag updates dependencies to the latest versions regardless of whether it is semver compatible. Must be used with the --update flag.

deno outdated package selection with package names

The outdated subcommand supports selecting which packages to operate on by passing package names as arguments. This works with or without the --update flag. Multiple selectors can be passed.

deno outdated wildcard and exclusion support

The outdated subcommand supports wildcards (*) and exclusions (!) for package selection. For example, '@std/*' matches all packages in the @std scope, and '!@std/fmt' excludes the @std/fmt package. Wildcards should be surrounded in quotes to prevent shell expansion.

deno outdated specific version updates

Specific versions can be selected for updating by appending the version after @ in the package name. For example, 'chalk@5.2' or '@std/async@1.0.6' will update those packages to the specified versions.

deno outdated --recursive flag

The --recursive flag (shorthand -r) includes all workspace members when checking for outdated dependencies. Without this flag, outdated only operates on the current workspace member.

deno outdated workspace default behavior

In a workspace setting, by default the outdated command only operates on the current workspace member, checking dependencies in the current directory's deno.json or package.json.

Give your agent this brain