Skip to content

docs: document framework detection in deno compile (2.8)#3080

Open
lunadogbot wants to merge 1 commit intodenoland:mainfrom
lunadogbot:docs/2.8-compile-framework-detect
Open

docs: document framework detection in deno compile (2.8)#3080
lunadogbot wants to merge 1 commit intodenoland:mainfrom
lunadogbot:docs/2.8-compile-framework-detect

Conversation

@lunadogbot
Copy link
Copy Markdown

Summary

Documents the new framework-detection behavior of deno compile in Deno 2.8 (denoland/deno#33164). Pointing deno compile at a directory now detects common web frameworks, runs deno task build, and generates an appropriate entrypoint.

  • New "Framework detection" section in runtime/reference/cli/compile.md listing the supported frameworks (Next.js, Astro, Fresh 1.x/2.x, Remix, SvelteKit, Nuxt, SolidStart, TanStack Start, Vite SSR).
  • Notes that entrypoints use import.meta.dirname so framework asset paths resolve against the embedded VFS.
  • Mentions the explicit-entrypoint fallback when no framework matches.

Test plan

  • deno task serve — section renders, anchor #framework-detection resolves, link to "Including Data Files or Directories" works.

Adds a "Framework detection" section to compile.md describing the new
behavior: \`deno compile .\` (or a directory) detects Next.js, Astro,
Fresh 1.x/2.x, Remix, SvelteKit, Nuxt, SolidStart, TanStack Start, and
Vite SSR projects, runs \`deno task build\` first, and generates the
entrypoint automatically. Notes that the entrypoint uses
\`import.meta.dirname\` so framework asset paths resolve against the VFS.

Refs denoland/deno#33164
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant