scripts.nuxt.com appears to resolve registry metadata — category, logo, stats, options — from a published @nuxt/scripts that is still 2.0.0-beta.6 (09-09). Docs content comes from the repo and is current, so the affected pages exist but render without their metadata.
What it looks like
pulse-analytics sits in the Utility group at nav position 42, between gravatar and usercentrics, with the generic i-carbon:cube placeholder icon. The Analytics group is positions 0–15.
On main the entry reads:
m('pulseAnalytics', 'Pulse Analytics', 'analytics', 'useScriptPulseAnalytics', { bundle: true }, null)Why it looks like the site rather than the entries
beta.7 added exactly two registry rows — pulse-analytics and tawk-to — and tawk-to is missing from the site too. The live nav's categorised entries match beta.6's 46; beta.7 and beta.8 have 48.
So it is not specific to one entry.
Note
A 2.0.0 stable does not seem to be required — anything past beta.6 would carry both rows.
Happy to be wrong about the mechanism; the two symptoms and the row counts are what I measured.
scripts.nuxt.comappears to resolve registry metadata — category, logo, stats, options — from a published@nuxt/scriptsthat is still2.0.0-beta.6(09-09). Docs content comes from the repo and is current, so the affected pages exist but render without their metadata.What it looks like
pulse-analyticssits in the Utility group at nav position 42, betweengravatarandusercentrics, with the generici-carbon:cubeplaceholder icon. The Analytics group is positions 0–15.On
mainthe entry reads:Why it looks like the site rather than the entries
beta.7added exactly two registry rows —pulse-analyticsandtawk-to— andtawk-tois missing from the site too. The live nav's categorised entries match beta.6's 46;beta.7andbeta.8have 48.So it is not specific to one entry.
Note
A 2.0.0 stable does not seem to be required — anything past beta.6 would carry both rows.
Happy to be wrong about the mechanism; the two symptoms and the row counts are what I measured.