Repository navigation
Conversation
Use the @nuxt/content4 build from nuxt/content-v4-temp (pkg.pr.new), aliased as @nuxt/content, and add shiki which v4 no longer bundles. Amp-Thread-ID: https://ampcode.com/threads/T-01a16a15-f311-73fe-b4a0-cf59e174c951 Co-authored-by: Sébastien Chopin <atinux@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Drop the v3 compatibility layer: remove content.config.ts, disable v3Composables, and read pages and navigation through the content client. Page meta now comes from top-level frontmatter (title, description, image), falling back to the leading heading and paragraph like v3 did. Amp-Thread-ID: https://ampcode.com/threads/T-01a16a15-f311-73fe-b4a0-cf59e174c951
Drop the heading/paragraph fallback: content-v4 generates the page data types from frontmatter, so content.get() needs no explicit type either. Amp-Thread-ID: https://ampcode.com/threads/T-01a16a15-f311-73fe-b4a0-cf59e174c951
Picks up the production hydration fix (nuxt/content-v4-temp#26) and drops the SQLite WASM chunk when v3 composables are disabled (nuxt/content-v4-temp#21). Amp-Thread-ID: https://ampcode.com/threads/T-01a16a15-f311-73fe-b4a0-cf59e174c951
BREAKING CHANGE: forks that set socials.twitter in app.config.ts must rename the key to socials.x to keep the X icon in the navbar. Amp-Thread-ID: https://ampcode.com/threads/T-01a1a18b-8326-72de-9960-d4bc57501905
…p#35) Headings link to themselves again, as on Content v3. Amp-Thread-ID: https://ampcode.com/threads/T-01a1a18b-8326-72de-9960-d4bc57501905
The preview depends on a pkg.pr.new build of comark while @comark/vue still pulls comark 0.8.1, and the two copies break the Nitro server build on Vercel. Override comark until it's released. Amp-Thread-ID: https://ampcode.com/threads/T-01a1a18b-8326-72de-9960-d4bc57501905
The previous preview couldn't load content snapshots in a serverless function (`useStorage is not defined`), so every page on Vercel was a 404. nuxt/content-v4-temp#36 fixes it, and #35 is now stacked on it. Amp-Thread-ID: https://ampcode.com/threads/T-01a1a18b-8326-72de-9960-d4bc57501905
Bundle sizeClient 93.7 kB
Largest changes in the client
And 44 more packages or files. Largest changes in the server
And 52 more packages or files. Brotli sizes. Initial page load counts the JavaScript and CSS a route loads before it renders. Measured by nuxt-bundle-analyzer for |
This was referenced Nov 7, 2026
Pins @nuxt/content to the pkg.pr.new preview of nuxt/content-v4-temp#35 at 9476cb5, rebased on v4 (comark ^0.9.0) with the serverless fix. comark 0.9.0 ships the heading-links plugin, so the comark override is no longer needed: a single comark@0.9.0 resolves. Amp-Thread-ID: https://ampcode.com/threads/T-01a1b55b-d6d9-77b9-8247-e18ca613421e Co-authored-by: Amp <amp@ampcode.com>
Pins @nuxt/content to the pkg.pr.new preview of nuxt/content-v4-temp#35 at 60b0921, on the latest v4 (which now includes #36). Same code as 9476cb5. Amp-Thread-ID: https://ampcode.com/threads/T-01a1b55b-d6d9-77b9-8247-e18ca613421e Co-authored-by: Amp <amp@ampcode.com>
The client fetches documents from the server instead of downloading the whole content snapshot. Static hosting still works: prerendered pages navigate through their payloads. Amp-Thread-ID: https://ampcode.com/threads/T-01a1a18b-8326-72de-9960-d4bc57501905
…347b6 Amp-Thread-ID: https://ampcode.com/threads/T-01a1b762-99d5-7223-af9e-fd8aa2c6db5a Co-authored-by: Amp <amp@ampcode.com>
This branch has not been deployed
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
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.
Written by an AI agent (Amp) on behalf of @atinux, who hasn't reviewed it yet.
Migrates content-wind to the upcoming Nuxt Content v4 (nuxt/content-v4-temp), built on comark-content, using its native API instead of the v3 compatibility layer.
Changes
@nuxt/contentnow points to the@nuxt/content4build of thev4branch from pkg.pr.new (a2347b6). It isn't on npm yet. It includes nuxt/content-v4-temp#35 (headings link to themselves again, as v3 did, through comark 0.9.0'sheading-links), nuxt/content-v4-temp#36 (content snapshots load in serverless functions, without which every page was a 404 on Vercel), nuxt/content-v4-temp#21 (no SQLite WASM chunk without v3 composables), nuxt/content-v4-temp#26 (fixes production hydration), nuxt/content-v4-temp#30 (rel="nofollow"on external links, like v3) and nuxt/content-v4-temp#40 (<ContentRenderer>renamed to<ContentDocument>).shiki, which v4 no longer bundles. The existingcontent.build.markdown.highlightconfig keeps working.content.config.tsand setscontent.v3Composables: false. Without a config, v4 servescontent/as a single source.content.get(route.path)and navigation withcontent.navigation(), and renders pages with<ContentDocument>. Withv3Composables: false, the deprecated<ContentRenderer>alias isn't registered: ona2347b6it leaves the page body empty. Layouts come frompage.data.layout.page.seo:useSeoMeta()readstitle,descriptionandimagestraight from frontmatter. Every page now setstitleanddescriptionin frontmatter, and About'sseo.*fields move to the top level.imageis now actually used asog:image. The "Pages" docs on the home page show the frontmatter instead of the v3 heading/paragraph rule.content.get()needs no type argument, because v4 generates the page data types from the frontmatter.v3Composables: falseis still needed: the module defaults it totrue, even without acontent.config.ts.content.mode: 'server-only': the client fetches documents from the server instead of downloading the whole content snapshot. On Vercel, the function answers/__nuxt_contentfrom its bundled snapshot. Withnuxi generate, no/__nuxt_contentfiles are emitted and client-side navigation uses the prerendered page payloads.experimental.sqliteConnector, which isn't a v4 option.LayoutKeyfrom#app, which fixes the 3vue-tscerrors that also exist onmain.socials.twittertosocials.xinapp.config.ts. Forks that setsocials.twitterlose the X icon until they rename the key. The socials docs now listxandbluesky.Checked against
main(v3)nuxi dev:/and/aboutrender the same: layouts (full-widthon About), MDC components (ButtonLink,:icon), navigation, and dual-theme code highlighting.<title>and meta description matchmainon both pages (Content WindandAbout).nuxi generatefrom a fresh worktree withpnpm install --frozen-lockfile: prerenders all routes, with no SQLite or WASM files emitted._nuxtis 892 KB (v3: 2.3 MB).windowmarker survives the clicks), and the navbar icons and color-mode toggle render.pnpm lintpasses, andvue-tscreports 0 errors.Known gaps (do not merge yet)