Skip to content

chore(docs): run on ViteHub main db9f307 - #39

Merged
vite-hub[bot] merged 1 commit into
mainfrom
chore/vitehub-main
Nov 18, 2026
Merged

vite-hub[bot] merged 1 commit into
mainfrom
chore/vitehub-main

Conversation

@onmax

@onmax onmax commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

The docs site was on @vite-hub/content 0.1.0, about 1,380 commits behind ViteHub main, with a Comark 0.8 stack held together by an override. This moves it to the pkg.pr.new build of ViteHub main at db9f307 (after v0.2.0, which is not on npm yet) and the Comark versions Content uses there. The pages come out the same.

What changes:

  • @vite-hub/content pins db9f307. comark and @comark/html go to ^0.9, comark-ui and comark-icon to ^0.12, comark-content to 0.5.1 (the version Content pins), and shiki to ^4.6 (comark 0.9's peer range).
  • defineContent() on main adds its own Comark UI preset in front of markdown.plugins (feat(docs): read pages through content.get() with one parser config vite-hub/vitehub#4143), which would bring chips and typeset back. markdown: { preset: false, plugins } keeps the site's own preset as the only one.
  • The comark-content>comark override goes: comark-content 0.5.1 asks for comark 0.9 itself.
  • Content on main no longer pulls Workspace, Sandbox and Shell, so the install drops about 400 package versions, including the native ones (@mongodb-js/zstd, @swc/core, cbor-extract, cpu-features, msgpackr-extract, node-liblzma, ssh2). Their allowBuilds entries and the release-age excludes for ViteHub 0.1.0 and Comark 0.8 go with them.
  • blockExoticSubdeps: false, since the pkg.pr.new tarballs depend on each other by URL.

The Nuxt nightly stays at the locked 5.0.0-2611081128-d54cab9 and the library packages' lockfile entries don't change.

What I ran, Node 24.21.0 on Linux:

  • pnpm install --frozen-lockfile passes.
  • pnpm docs:generate on main and on this branch, then compared docs/dist/public. The same 115 files outside _nuxt/ and the same 24 pages. Every .md copy, search.json, llms.txt and _headers is byte-identical. The visible text of 23 pages is identical. On /tinylinkify/compatibility/, the bare github.com in prose is no longer a link: comark 0.9 follows GFM there, which only links a domain with www. or a scheme. The rest of the HTML diff is Comark UI 0.12's CSS and code-block script. Code lines (174) and links otherwise match, and no chips or typeset markup shows up.
  • wrangler@4.158.0 dev -c docs/dist/server/wrangler.json: /, /tinyaml/guide/getting-started/, /tinylinkify/compatibility/, /search.json, /llms.txt, /index.md, /tinyaml/guide/api.md answer 200 with the right content types, Accept: text/markdown on / answers Markdown, /nope/ 404, and Host: tinyaml.onmax.me 301s to https://tiny.onmax.me/guide/.

pnpm docs:dev fails with "Unrecognized import attributes specified" on every page, on main as well. I think it's @iconify-json/lucide, which imports its JSON with { type: 'json' } and goes through the Cloudflare dev runner, but I didn't confirm it. This PR doesn't change that.

Workers Builds deploys on merge. After that, curl -sI https://tinyaml.onmax.me/guide/ should still 301.

@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-18T00:00:43.651075Z
We couldn’t complete this review. Comment @codex review to try again.
e988e15 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@pkg-pr-new

pkg-pr-new Bot commented Nov 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

tinyaml

pnpm add https://pkg.pr.new/onmax/tiny/tinyaml@39

tinyini

pnpm add https://pkg.pr.new/onmax/tiny/tinyini@39

tinyjson5

pnpm add https://pkg.pr.new/onmax/tiny/tinyjson5@39

tinylinkify

pnpm add https://pkg.pr.new/onmax/tiny/tinylinkify@39

tinyswap

pnpm add https://pkg.pr.new/onmax/tiny/tinyswap@39

commit: e988e15

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found. No P0 or P1 findings remain.

Approach: sound — the dependency upgrade aligns Content with its supported Comark stack, while explicitly disabling Content’s added preset preserves the site’s existing rendering configuration.

Reviewed changes — reviewed all four changed files and traced their effects through Markdown parsing, prerendering, client navigation, and Cloudflare serving.

  • Dependency alignment: pins ViteHub Content to db9f307 and updates Comark, Comark Content, Comark UI/icon, and Shiki while retaining the locked Nuxt nightly.
  • Preset preservation: keeps the site’s custom plugin ordering and prevents Content’s defaults from restoring chips or typesetting.
  • Install configuration: removes the obsolete parser override, unused native-package build permissions, and old release-age exclusions; allows the preview packages’ transitive tarball URLs.
  • Lockfile regeneration: removes the unused ViteHub dependency graph; tinyaml retains its existing Comark/chart versions with an updated Shiki peer resolution, which passed a focused SVG-generation smoke test.

Validation passed: pnpm install --frozen-lockfile, pnpm docs:generate, production-worker route/content-type/redirect checks, and browser checks for navigation, code tabs, copying, and image zoom. The build produced all 24 pages, and generated internal links and heading anchors resolved successfully.

Pullfrog  | View workflow run | Using gpt-6.1-sol(xhigh) | 𝕏

@vite-hub
vite-hub Bot merged commit 02dfd3e into main Nov 18, 2026
10 checks passed
@vite-hub

vite-hub Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor
Session Status Started Duration
Pending Completed Not started —

Latest result

Pull request merged.

Final answers

Session

Pull request merged.

@github-actions github-actions Bot mentioned this pull request Nov 18, 2026
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