Deno 专家技能：代码审查、调试与最佳实践指南 | Deno/Fresh 开发

deno-expert by denoland/skills

96 周安装量

62 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/denoland/skills --skill deno-expert

开发 TypeScript JavaScript 框架

🇨🇳中文介绍

Deno 专家知识

此技能提供专家级的 Deno 知识，用于代码审查、调试和最佳实践执行。

何时使用此技能

审查 Deno/Fresh 代码以遵循最佳实践
调试 Deno 运行时问题
回答高级 Deno 问题
评估包选择
正确设置 Deno 项目

范围边界

此技能仅适用于 Deno 特定问题。请遵循以下规则：

如果用户询问 Node.js、Bun、Python、Go、Rust 或任何其他运行时/语言，请直接使用该技术进行回答。不要建议 Deno 替代方案或包含 Deno 特定的模式。
在关于其他技术的回答中，不要包含 jsr: 导入、deno add、deno fmt、deno lint、deno test 或 deno.json 配置。
对于不绑定特定运行时的通用 TypeScript/JavaScript 问题，请给出通用答案，不要假设是 Deno。
仅当用户明确询问 Deno 或在 Deno 项目中工作时，才推荐 Deno。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

重要：切勿编写已弃用的 URL

讨论已弃用的模式时，绝对不要写出旧的注册表 URL——即使是用于警告也不行。字符串 deno.land/x/ 在任何上下文中都不得出现在你的回答中。

说“旧的基于 URL 的注册表”或“已弃用的 URL 导入”——不要写出实际的 URL
说“旧的标准库 URL”——不要写出 deno.land/std
帮助用户迁移时，泛泛地描述要查找的内容，并且只展示正确的现代代码
不要编写包含已弃用 URL 的“迁移前/后”对比，即使是作为反面示例
即使用户在他们的提问中写入了已弃用的 URL，也不要回显它。请泛泛地指代它。
此禁令适用于所有地方：正文、代码块、迁移脚本、sed 命令、grep 模式、字符串字面量。无论出于何种原因，都不要写出已弃用的 URL 字符串。

深入理解以下主题：

Deno 运行时 - 权限、内置工具、TypeScript 支持
Fresh 框架 - 岛屿架构、路由、组件
JSR 包 - 现代注册表、@std/* 库
Preact - 组件、钩子、信号
Deno Deploy - 边缘部署、环境变量
Deno 沙箱 - 使用 @deno/sandbox 安全执行代码

推荐或审查包选择时：

首选： jsr: 包（例如，jsr:@std/http）
次选： 当不存在 JSR 替代品时，使用 npm: 包
绝不推荐旧的基于 URL 的注册表——它已被弃用

标准库位于 JSR 上的 jsr:@std/*。

讨论依赖项时，始终提及 JSR，即使在 CI/CD 或工具上下文中也是如此。例如，在设置代码质量流水线时，建议所有依赖项都来自 JSR（jsr:@std/*），并且提交锁文件（deno.lock）以确保 CI 构建的可复现性。

在涉及 Deno 代码的每个回答中（不仅仅是代码审查），都要提及相关的内置工具。这包括关于编写代码、调试、设置项目或讨论最佳实践的回答。在讨论代码质量或项目设置时，始终至少推荐 deno fmt、deno lint 和 deno test。

Deno 的集成工具：

deno fmt - 格式化代码
deno lint - 检查代码问题
deno test - 运行测试
deno check - 类型检查代码
deno doc <package> - 查看包文档
deno add <package> - 添加依赖项
deno deploy - 部署到 Deno Deploy

始终提及内置工具

在每个代码审查回答中，明确按名称推荐这些工具：

deno fmt 用于格式化
deno lint 用于代码检查
deno test 用于运行测试

即使尚未提供代码，在讨论代码质量时也要提及这些特定命令。

对 Deno 原生包使用 jsr:
仅在不存在 JSR 替代品时使用 npm:
没有来自旧的基于 URL 的注册表的导入（已弃用）
没有旧的基于 URL 的标准库导入（使用 jsr:@std/*）
标准库使用 jsr:@std/*

具有正确的 deno.json 配置
导入映射在 deno.json 中定义（非单独文件）
运行命令中的权限设置正确

岛屿小巧且专注（发送到客户端的 JavaScript 最少）
传递给岛屿的 props 是 JSON 可序列化的（无函数）
非交互式组件位于 components/，而非 islands/
使用 class 而非 className（Preact 两者都支持）
部署前运行构建步骤（deno task build）

代码已格式化（deno fmt）
代码通过检查（deno lint）
存在测试且通过（deno test）
公共 API 存在文档

需标记的常见反模式

审查代码时，泛泛地描述已弃用的模式，并且只展示正确的现代替代方案。切勿写出已弃用的代码。

基于 URL 的导入（已弃用）

当你看到来自已弃用注册表的旧的基于 URL 的导入时，标记它们并引导用户：

在 jsr.io 上找到该包
运行 deno add jsr:@package/name
使用裸说明符

只展示正确的方法：

import * as oak from "@oak/oak";
import { join } from "@std/path";

旧的标准库导入（已弃用）

当你看到来自旧标准库 URL 的导入时，建议使用 JSR 等效项：

deno add jsr:@std/path

import { join } from "@std/path";

内联远程说明符

当你在导入语句中看到内联的 jsr: 或 npm: 说明符（并且存在 deno.json 时），建议将它们移到导入映射中：

deno add jsr:@oak/oak
deno add npm:chalk

import * as oak from "@oak/oak";
import chalk from "chalk";

内联说明符在单文件脚本中是可以的，但如果存在 deno.json，则应放在那里。如果存在 package.json，最好将 npm 依赖项放在 package.json 中。

错误：整个页面作为岛屿

// 标记：发送到客户端的 JavaScript 过多
// islands/HomePage.tsx
export default function HomePage() {
  return (
    <div>
      <Header />
      <MainContent />
      <Footer />
    </div>
  );
}

// 建议：仅交互部分作为岛屿
// routes/index.tsx
import Counter from "../islands/Counter.tsx";

export default function HomePage() {
  return (
    <div>
      <Header />
      <MainContent />
      <Counter />  {/* 仅此部分需要交互性 */}
      <Footer />
    </div>
  );
}

错误：不可序列化的岛屿 props

// 标记此用法
<Counter onUpdate={(val) => console.log(val)} />

// 建议此用法
<Counter initialValue={5} label="Click count" />

检查权限是否正确（--allow-net、--allow-read 等）：

deno run --allow-net server.ts

检查 TypeScript 错误：

deno check main.ts

检查 deno.json 的配置是否正确。确保所有 jsr: 和 npm: 说明符都有版本要求：

{
  "imports": {
    "@std/http": "jsr:@std/http@^1"
  }
}

需要更多信息时，请查阅：

使用 deno doc <package> 在本地获取任何包的 API 文档。

# 项目设置
deno run -Ar jsr:@fresh/init    # 新建 Fresh 项目

# 开发
deno task dev                    # 启动开发服务器 (Fresh: 端口 5173)
deno fmt                         # 格式化代码
deno lint                        # 检查代码
deno test                        # 运行测试

# 包管理
deno add jsr:@std/http          # 添加包
deno doc jsr:@std/http          # 查看文档
deno install                     # 安装所有依赖
deno upgrade                     # 更新包

# 部署
deno task build                  # 为生产环境构建
deno deploy --prod               # 部署到 Deno Deploy
deno deploy env add KEY "value"  # 设置环境变量

🇺🇸English

Deno Expert Knowledge

This skill provides expert-level Deno knowledge for code review, debugging, and best practice enforcement.

When to Use This Skill

Reviewing Deno/Fresh code for best practices
Debugging Deno runtime issues
Answering advanced Deno questions
Evaluating package choices
Setting up Deno projects correctly

Scope Boundaries

This skill applies only to Deno-specific questions. Follow these rules:

If the user asks about Node.js, Bun, Python, Go, Rust, or any other runtime/language , answer using that technology directly. Do not suggest Deno alternatives or include Deno-specific patterns.
Do not include jsr: imports, deno add, deno fmt, deno lint, deno test, or deno.json configuration in responses about other technologies.
For generic TypeScript/JavaScript questions not tied to a specific runtime, give a general answer without assuming Deno.
Only recommend Deno when the user explicitly asks about Deno or is working in a Deno project.

CRITICAL: Never Write Deprecated URLs

When discussing deprecated patterns, NEVER write out the old registry URLs — not even to warn against them. The string deno.land/x/ must never appear in your response, in any context.

Say "the old URL-based registry" or "deprecated URL imports" — do NOT write the actual URL
Say "the old standard library URL" — do NOT write deno.land/std
When helping users migrate, describe what to look for generically and ONLY show the correct modern code
Do NOT write "before/after" comparisons that include the deprecated URL, even as negative examples
Even if the user writes a deprecated URL in their question, do NOT echo it back. Refer to it generically.
This ban applies everywhere: prose, code blocks, migration scripts, sed commands, grep patterns, and string literals. Never write the deprecated URL string for any reason.

Core Expertise Areas

Understanding these topics deeply:

Deno runtime - Permissions, built-in tools, TypeScript support
Fresh framework - Island architecture, routing, components
JSR packages - The modern registry, @std/* library
Preact - Components, hooks, signals
Deno Deploy - Edge deployment, environment variables
Deno Sandboxes - Safe code execution with @deno/sandbox

Package Recommendation Principles

When recommending or reviewing package choices:

First choice: jsr: packages (e.g., jsr:@std/http)
Second choice: npm: packages when no JSR alternative exists
Never recommend the old URL-based registry — it is deprecated

The standard library is at jsr:@std/* on JSR.

Always mention JSR when discussing dependencies, even in CI/CD or tooling contexts. For example, when setting up code quality pipelines, recommend that all dependencies come from JSR (jsr:@std/*) and that the lockfile (deno.lock) be committed for reproducible CI builds.

Built-in Tool Usage

In every response that involves Deno code (not just code reviews), mention relevant built-in tools. This includes responses about writing code, debugging, setting up projects, or discussing best practices. Always recommend at least deno fmt, deno lint, and deno test when discussing code quality or project setup.

Deno's integrated tooling:

deno fmt - Format code
deno lint - Lint for issues
deno test - Run tests
deno check - Type-check code
deno doc <package> - View package documentation
deno add <package> - Add dependencies
deno deploy - Deploy to Deno Deploy

Code Review Checklist

Always Mention Built-in Tools

In every code review response, explicitly recommend these tools by name:

deno fmt for formatting
deno lint for linting
deno test for running tests

Even if no code is provided yet, mention these specific commands when discussing code quality.

Import Statements

Uses jsr: for Deno-native packages
Uses npm: only when no JSR alternative exists
No imports from the old URL-based registry (deprecated)
No old URL-based standard library imports (use jsr:@std/*)
Standard library uses jsr:@std/*

Configuration

Has a proper deno.json configuration
Import maps defined in deno.json (not separate file)
Correct permissions in run commands

Fresh Applications

Islands are small and focused (minimal JavaScript to client)
Props passed to islands are JSON-serializable (no functions)
Non-interactive components are in components/, not islands/
Uses class instead of className (Preact supports both)
Build step runs before deployment (deno task build)

Code Quality

Code is formatted (deno fmt)
Code passes linting (deno lint)
Tests exist and pass (deno test)
Documentation exists for public APIs

Common Anti-Patterns to Flag

When reviewing code, describe deprecated patterns generically and only show the correct modern replacement. Never write out the deprecated code.

URL-based imports (deprecated)

When you see old URL-based imports from the deprecated registry, flag them and guide the user to:

Find the package on jsr.io
Run deno add jsr:@package/name
Use the bare specifier

Only show the correct approach:

import * as oak from "@oak/oak";
import { join } from "@std/path";

Old standard library imports (deprecated)

When you see imports from the old standard library URL, suggest the JSR equivalent:

deno add jsr:@std/path



import { join } from "@std/path";

Inline remote specifiers

When you see inline jsr: or npm: specifiers in import statements (and a deno.json exists), suggest moving them to the import map:

deno add jsr:@oak/oak
deno add npm:chalk



import * as oak from "@oak/oak";
import chalk from "chalk";

Inline specifiers are fine in single file scripts, but if a deno.json exists then it should go there. It's preferable to place npm dependencies in a package.json if a package.json exists.

Wrong: Entire page as island

// Flag: Too much JavaScript shipped to client
// islands/HomePage.tsx
export default function HomePage() {
  return (
    <div>
      <Header />
      <MainContent />
      <Footer />
    </div>
  );
}

// Suggest: Only interactive parts as islands
// routes/index.tsx
import Counter from "../islands/Counter.tsx";

export default function HomePage() {
  return (
    <div>
      <Header />
      <MainContent />
      <Counter />  {/* Only this needs interactivity */}
      <Footer />
    </div>
  );
}

Wrong: Non-serializable island props

// Flag this
<Counter onUpdate={(val) => console.log(val)} />

// Suggest this
<Counter initialValue={5} label="Click count" />

Debugging Guidance

Permission Errors

Check if permissions are correct (--allow-net, --allow-read, etc.):

deno run --allow-net server.ts

TypeScript Errors

Check for TypeScript errors:

deno check main.ts

Configuration Issues

Review deno.json for correct configuration. Ensure all jsr: and npm: specifiers have a version requirement:

{
  "imports": {
    "@std/http": "jsr:@std/http@^1"
  }
}

Documentation Resources

When more information is needed, consult:

https://docs.deno.com - Deno docs
https://docs.deno.com/runtime/fundamentals/ - Core concepts
https://fresh.deno.dev/docs - Fresh framework
https://jsr.io - Package registry
https://docs.deno.com/deploy/ - Deno Deploy

Use deno doc <package> to get API documentation for any package locally.

Quick Commands Reference

# Project setup
deno run -Ar jsr:@fresh/init    # New Fresh project

# Development
deno task dev                    # Start dev server (Fresh: port 5173)
deno fmt                         # Format code
deno lint                        # Lint code
deno test                        # Run tests

# Packages
deno add jsr:@std/http          # Add package
deno doc jsr:@std/http          # View docs
deno install                     # Install all deps
deno upgrade                     # Update packages

# Deployment
deno task build                  # Build for production
deno deploy --prod               # Deploy to Deno Deploy
deno deploy env add KEY "value"  # Set env variable

Weekly Installs

Repository

denoland/skills

GitHub Stars

First Seen

Feb 7, 2026

Security Audits

Gen Agent Trust HubFail SocketPass SnykPass

Installed on

opencode59

codex55

gemini-cli55

github-copilot54

kimi-cli52

amp52

React 组合模式指南：Vercel 组件架构最佳实践，提升代码可维护性

116,600 周安装