/Knowledge/sources/honojs__hono/llms-full/deno-npm-and-jsr--9aa1b8f08aab.md
Deno: npm and JSR - hono-docs
Deno: npm and JSR Source evidence: /Sources/honojs hono/provenance.md Canonical citation: https://hono.dev/llms full.txt npm and jsr Summary Hono is availabl...
Deno: npm and JSR
Source evidence: /Sources/honojs__hono/provenance.md Canonical citation: https://hono.dev/llms-full.txt#npm-and-jsr
Summary
Hono is available on both npm and JSR (the JavaScript Registry). You can use either npm:hono or jsr:@hono/hono in your deno.json: ```json { "imports": { "hono": "js...
Content
Hono is available on both npm and JSR (the JavaScript Registry). You can use either npm:hono or jsr:@hono/hono in your deno.json:
{
"imports": {
"hono": "jsr:@hono/hono" // [!code --]
"hono": "npm:hono" // [!code ++]
}
}
To use middleware you need to use the Deno directory syntax in the import.
{
"imports": {
"hono/": "npm:/hono/"
}
}
When using third-party middleware, you may need to use Hono from the same registry as the middleware for proper TypeScript type inference. For example, if using the middleware from npm, you should also use Hono from npm:
{
"imports": {
"hono": "npm:hono",
"zod": "npm:zod",
"@hono/zod-validator": "npm:@hono/zod-validator"
}
}
Metadata
{
"chunk_index": 0,
"citation": "https://hono.dev/llms-full.txt#npm-and-jsr",
"coverage_role": "overview",
"qualified_title": "Hono / llms-full / Deno > npm and JSR (1)",
"retrieved_at": "2026-07-02T05:51:01Z",
"section_index": 443,
"source_id": "/honojs/hono",
"source_type": "llms_full",
"target_label": "llms-full",
"title": "Deno: npm and JSR",
"upstream_url": "https://hono.dev/llms-full.txt",
"version": "2026"
}
Kinic Wiki