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

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 unlink command removes local package link

The deno unlink command removes a local package link created with deno link, so imports resolve to the published registry version again. It edits the links array in the nearest deno.json for you.

deno unlink argument formats

You can remove an entry by its path or by the linked package's JSR name. Examples: deno unlink ../my-local-pkg removes a link by the path you linked, and deno unlink @scope/name removes a link by the package's JSR name.

deno unlink path resolution

Path arguments resolve relative to the current working directory, the same way deno link resolves them. So deno unlink ../pkg matches an entry created by deno link ../pkg from the same directory.

deno unlink removes empty links array

When the links array becomes empty after unlinking, it is removed entirely from deno.json.

deno unlink exit status on mismatch

If no argument matches a linked entry, deno unlink exits with a non-zero status rather than reporting success, so a mistyped path or name is detectable in scripts and CI.

deno unlink does not create deno.json

deno unlink never creates a deno.json: if there is none, there are no linked packages to remove.

Give your agent this brain