Nuxt SEO v6: what apps need to change (cwa-nuxt-module #392)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- nuxtjs
- Domain
- documentation
Research direction
The payload names no docs file, so start by finding the existing upgrade or migration page for the cwa/nuxt module in this repo. Check the Nuxt SEO v6 package majors, the optional OG renderer peers, the skewProtection and aiReady opt-outs in nuxt.config, and the defineSitemapEventHandler import and RequestEvent change. Done when each of these four points appears in the migration notes with its version or config example, and the wording is checked against cwa-nuxt-module #392.
Written by the indexing model from the issue text.
Description
From cwa-nuxt-module #392 (2b694b80, unreleased after 2.0.0-alpha.15). Breaking for apps.
- @cwa/nuxt now needs the Nuxt SEO v6 family: @nuxtjs/sitemap 9, @nuxtjs/robots 7, nuxt-site-config 5, nuxt-seo-utils 9, nuxt-schema-org 7, nuxt-link-checker 6, nuxt-og-image 7. An app that lists any of these (or @nuxtjs/seo) itself must move to the same majors, or two majors get installed side by side.
- Optional OG renderer peers: satori 0.47.1 or later, @resvg/resvg-js 2.6.2 or later.
- Registering @nuxtjs/seo 6 also switches on nuxt-skew-protection (polls for new builds) and nuxt-ai-ready (llms.txt etc.), adding about 5.5 KB gzip to every visitor's entry. Opt out with
skewProtection: { enabled: false }andaiReady: { enabled: false }in nuxt.config. - Custom sitemap sources:
defineSitemapEventHandleris imported from#sitemap/server, and sitemap hooks receive Nuxt'sRequestEvent(noevent.node).
- Dominant language
- Vue
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from components-web-app/docs
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
components-web-app/docs#234 ·
-
Document opening the add page data form with defaults (?parentPage, ?parentPageData, ?template)Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
components-web-app/docs#230 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
components-web-app/docs#228 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
components-web-app/docs#227 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
components-web-app/docs#235 ·
All issues in components-web-app/docs
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
cathrynlavery/diagram-design#443 ·
Maintainers usually reply within 2 days
-
review-followup
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
griffinwork40/agent-afk#3868 ·
Maintainers usually reply within 1 day
-
swift.md: `Date(myString, strategy: .iso8601)` example omits `try` — the initializer is throwingOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
btclib-org/btclib-secp256k1#1208 ·
Maintainers usually reply within 1 day