deno-deploy_skill

Overview

This skill guides deploying Deno apps to Deno Deploy using the modern deno CLI. It emphasizes using deno deploy (not deployctl), covers preflight checks, auth flows, app creation, framework builds, and common error handling. Follow the steps to reliably build and publish production or preview deployments.

How this skill works

The skill inspects your project for deno.json/deno.jsonc to locate the app directory and detects common frameworks (Fresh, Astro, Next, Nuxt, Remix, SvelteKit, Lume, etc.). It runs preflight checks (Deno version, deploy config, framework detection), instructs how to authenticate (interactive browser or CI token), and maps to the correct build and deno deploy commands. It also explains how to create an app, set entrypoints, manage env vars, and interpret deployment output.

When to use it

• You want to publish a Deno or framework-based app to Deno Deploy (production or preview).
• You need guidance on authentication flows or CI/CD token setup for automated deploys.
• You need help determining app directory, entrypoint, or required build steps before deploying.
• You encounter common errors like missing org, missing entrypoint, or auth failures.
• You are configuring environment variables, static site deployment, or cloud integrations.

Best practices

• Always run preflight checks from the app directory where deno.json/deno.jsonc is located.
• Use deno deploy (requires Deno >= 2.4.2). Do not use deployctl (deprecated).
• For automation, create a Deno Deploy access token and set DENO_DEPLOY_TOKEN in CI.
• Add deploy org/app and entrypoint to deno.json to avoid interactive flows and entrypoint errors.
• Run framework-specific build steps (npm run build or deno task build) before deno deploy --prod.

Example use cases

• Deploy a Fresh app: deno task build && deno deploy --prod from the project directory.
• Create a first app when no deploy config exists: deno deploy create --org <org> and complete browser flow.
• CI pipeline: export DENO_DEPLOY_TOKEN and run deno deploy --prod in GitHub Actions.
• Static site: build to _site, then either include _site in deno.json or use a serve.ts entrypoint to serveDir.
• Troubleshoot missing entrypoint: add deploy.entrypoint in deno.json or use --entrypoint flag.