feat: first-party comark-content support - #321
Open
harlan-zw wants to merge 1 commit into
Open
Conversation
resolveNuxtContentVersion() only answers for @nuxt/content, so an app running comark-content never reached the robots frontmatter mapping. Switch to resolveContentProvider() and run the same content:file:afterParse handler for both providers. comark reads Markdown into Nitro server assets rather than a database, so unlike Nuxt Content v2 it needs no Cloudflare opt out.
This was referenced Aug 18, 2026
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.
❓ Type of change
📚 Description
The Nuxt Content integration gated on
resolveNuxtContentVersion(), which only ever answers for@nuxt/content. An app running comark-content never reached the frontmatter mapping, sorobots: falsein a Markdown file did nothing and gave no warning about it.comark fires
content:file:afterParsewith the same context shape as@nuxt/contentv3, so this is the same handler behindresolveContentProvider()instead of a version number. No new frontmatter, no schema opt in, anduseSeoMeta(page.seo)renders it exactly as before.The Cloudflare opt out stays scoped to Nuxt Content v2. comark reads Markdown into Nitro server assets at build time, so there is no database to be unavailable at the edge.
Depends on
nuxtseo-sharedexportingresolveContentProvider(). CI is red until that publishes.🔗 Related
Six PRs for one cross-repo change. Release order is top to bottom:
nuxtseo-sharedfeat(shared): detect comark-content as a content provider harlan-zw/nuxt-seo#621@nuxtjs/sitemapfeat: first-party comark-content support sitemap#665@nuxtjs/robotsfeat: first-party comark-content support #321nuxt-schema-orgfeat: first-party comark-content support harlan-zw/nuxt-schema-org#151nuxt-link-checkerfeat: first-party comark-content support harlan-zw/nuxt-link-checker#104comark-contentfeat(comark-content): hand the sitemap integration to @nuxtjs/sitemap harlan-zw/harlan-nuxt#742 through 5 need 1 published. 6 needs 2 published.