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/update

6 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

deno update basic usage

deno update 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 update --latest flag

The --latest flag makes deno update upgrade to the latest versions regardless of whether it's semver compatible.

deno update with package selectors

deno update accepts package selectors to specify which packages to update. Multiple selectors can be passed, and wildcards (*) and exclusions (!) are supported. For example: deno update --latest "@std/*" "!@std/fmt" updates all packages with @std scope except @std/fmt. When using wildcards, surround arguments in quotes to prevent shell expansion.

deno update to specific version

You can specify a specific version to update a package to by appending @ and the version after the package name. For example: deno update chalk@5.2 @std/async@1.0.6

deno update --recursive flag for workspaces

In a workspace setting, deno update by default only operates on the current workspace member. Use the --recursive flag (or -r shorthand) to update dependencies across all workspace members.

deno update workspace behavior

When in a workspace with multiple members defined in deno.json, running deno update from a specific directory will only update dependencies listed in that directory's deno.json or package.json, not dependencies in other workspace members.

Give your agent this brain