Repository navigation
docs: remove Deno from the docs and align ESLint rule pages - #45
Merged
Merged
Conversation
Drop Deno install tabs, the Deno ecosystem tile and brand asset, and Deno compatibility claims from the documentation site and the package READMEs. Give every ESLint rule section the same shape: order sections like the rules table, add Reports lines plus Flagged and Accepted examples to no-object-em and no-manual-enum, and move the prefer-native-schema-adapters Reports line ahead of its examples. Closes #38
Remove the Deno setup step from Extended validation, the Hono example's Deno server, runtime test, scripts and config, the root Deno workspace file and the deno.lock ignore entry. The runtime suite now covers Bun and Cloudflare Workers, and contributor docs and the changeset say so.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #38
Deno removal
Deno is removed from the repo entirely: the docs, CI and the Hono example.
deno addinstall tabs are gone (getting started, adapters, ESLint plugin page, landing-page install picker). So are the Deno ecosystem tile, its brand registry entry,docs/public/brands/deno.svgand its brand-assets row. Deno is no longer listed as a supported runtime in any docs page.enumwaiipackage READMEs no longer have the Deno install command or Deno support claims. The patch changeset says the documented runtime support is now Node.js, Bun and Cloudflare Workers.denoland/setup-denostep from Extended validation. The runtime step is now "Check Bun and Cloudflare Workers".deno.json,runtime/deno.tsandruntime-tests/deno-runtime.ts, and removed thedev:denoandtest:denoscripts.test:runtimesnow runs Bun and Cloudflare only. Updated the example README and the Worker's description string.deno.jsonworkspace file and theexamples/**/deno.lockentry in.gitignore.CONTRIBUTING.md,MAINTAINERS.mdandexamples/README.mdno longer mention Deno.git grep -i denonow matches only the changeset text and existing CHANGELOG history.ESLint rules page consistency
no-object-emandno-manual-enumnow have aReports:line andFlagged/Acceptedexamples, like the other rules. The existingno-manual-enum.casessnippet became its Accepted example.prefer-native-schema-adaptersReports:line ahead of its examples, matching the other sections.Validation
pnpm checkchain passes. The format step was scoped to exclude.claude/worktrees/, because another local session's worktree there fails prettier. This doesn't affect CI.pnpm test:runtimes(Bun and Cloudflare Workers, including the Wrangler dry-run) passes. Locally it ran on Bun 1.3.11; CI pins Bun 1.4.2.