Manage the Deno runtime with OMG

Install verified Deno releases, pin JavaScript and TypeScript runtime versions, and keep Deno tasks and dependencies separate.

Release v0.1.224 ยท Reviewed

On this page

Choose a Deno release#

Deno is a JavaScript and TypeScript runtime. OMG v0.1.224 manages its executable; Deno itself remains responsible for project permissions, dependency resolution, lockfiles, and application execution.

The provider downloads official denoland/deno GitHub release ZIPs. Its target map covers Linux GNU and macOS on x86_64 and aarch64. It does not select a musl-specific Linux archive or a Windows executable.

OMG's own published CLI binaries target Linux x86_64 and Apple Silicon macOS. Provider target mappings do not establish released OMG binaries on other architectures. WSL uses the Linux guest target, not a native Windows target.

Install and inspect#

omg list deno --available
omg use deno latest
omg list deno
omg which deno

latest selects the newest stable release in the provider's bounded release list. Partial numeric requests also resolve against stable releases; an exact prerelease request is a different, explicit choice. The list is not an unbounded history of every Deno release.

Use an exact version for a project that needs a repeatable runtime selection. omg which deno reports the selected version. With the shell hook enabled, check the executable at a fresh prompt:

deno --version
which -a deno

The activation directory exposes the installed version's bin directory without command shims. A Deno installed elsewhere can still win if another shell configuration puts it earlier on PATH.

Pin a project#

Within a directory, Deno detection reads .deno-version, then .dvmrc, then .tool-versions. The current directory is checked before parent directories; supported mise layers follow those files within each directory.

For an installed version intended by your project, an example pin is:

printf '%s\n' '2.9.0' > .deno-version
omg use deno
omg which deno

Replace the example with the project's chosen release. The hook selects installed versions; it does not install a missing Deno when you enter the directory. A deno.json task definition is not a substitute for a Deno runtime version pin.

Run the project's own Deno workflow#

Use Deno's normal project commands after confirming the runtime:

deno task

OMG's task runner can discover tasks in deno.json. If an equal-priority task also exists in another ecosystem, select the intended ecosystem explicitly rather than relying on an interactive prompt in CI. See the task runner guide for argument forwarding and selection modes.

OMG does not turn a runtime checksum into a security review of remote modules or task scripts. Keep the project's Deno lockfile and permission choices under review.

Update or remove a version#

Use omg list deno --available, then omg use deno VERSION to install the chosen release. omg use deno latest asks the provider to resolve the current stable alias; it does not rewrite the project's version file.

Switch to another installed version before running omg use deno VERSION --uninstall. The version is required and removal refuses the active managed version. There is no separate omg update deno command.

Verify downloads and diagnose failures#

OMG requires either the GitHub asset's SHA-256 digest or the official archive's .sha256sum sidecar. The sidecar must identify the intended archive. A missing checksum or mismatch stops installation.

The archive is extracted into staging and the expected Deno launcher is checked before publishing the version. This checks downloaded bytes and layout against provider information; it does not establish a SLSA build level or verify every dependency Deno may fetch later.

SymptomCheck
Release or target ZIP is missingInspect the exact release and GNU Linux/macOS architecture mapping.
Checksum data is absentUse a release with supported integrity metadata; do not bypass verification.
Deno remains unchanged after selectionCheck the nearest pin, restart the hook, and compare which -a deno.
Old version is absent from the remote listDiscovery uses a bounded recent-release window; an exact release lookup and a partial request are different operations.

Continue#

Read runtime storage and hooks, security boundaries, and the Node.js guide when choosing between runtimes.

Reviewed release source: Deno provider, runtime CLI, and version-file hooks. The commands document source-supported behavior; no Deno release archive was executed for this review.