Bump the node group across 1 directory with 2 updates

[dependabot]

Bumps the node group with 2 updates in the / directory: typescript and @nuxtjs/seo.

Updates typescript from 5.9.3 to 6.0.2

Release notes

Sourced from typescript's releases.

TypeScript 6.0

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

TypeScript 6.0 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 6.0.0 (Beta).

Downloads are available on:

• npm

Commits

• 607a22a Bump version to 6.0.2 and LKG
• 9e72ab7 🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...
• 35ff23d 🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...
• e175b69 Bump version to 6.0.1-rc and LKG
• af4caac Update LKG
• 8efd7e8 Merge remote-tracking branch 'origin/main' into release-6.0
• 206ed1a Deprecate assert in import() (#63172)
• e688ac8 Update dependencies (#63156)
• 29b300d Bump the github-actions group across 1 directory with 2 updates (#63205)
• 0c2c7a3 DOM update (#63183)
• Additional commits viewable in compare view

Updates @nuxtjs/seo from 3.4.0 to 5.1.0

Release notes

Sourced from @​nuxtjs/seo's releases.

v5.1.0

   🚀 Features

• Skew protection + ai ready standalone  -  by @​harlan-zw (d0fc2)

    View changes on GitHub

v5.0.0

Nuxt SEO v5 bumps every sub-module to a new major version (except OG Image, which stays on v6). The common thread is the Site Config v4 dependency; addressing those changes first will make the rest of the migration smooth.

For step-by-step upgrade instructions, see the v4 to v5 migration guide.

🛠️ DevTools Unity

The biggest change in v5 is that every Nuxt SEO module now shares a single DevTools foundation through our new shared DevTools layer (nuxtseo-layer-devtools).

Previously each module shipped its own DevTools client with inconsistent layouts, patterns, and capabilities. In v5, all DevTools clients extend a common Nuxt layer that provides:

• Consistent layout and navigation across every module, with a module switcher to jump between them
• Setup checklist that validates your configuration across all installed modules, flagging required and recommended actions
• Built-in troubleshooting, update indicators, and production mode preview in every module

Nuxt SEO Utils gets a brand new DevTools client for the first time, and the DevTools for Robots, Sitemap, Schema.org, and Link Checker have all been revamped to use the shared layer.

🔗 ESLint Link Checking

Nuxt Link Checker v5 ships an ESLint integration with zero-config @nuxt/eslint support:

• link-checker/valid-route (error): validates relative URLs match known routes with "did you mean?" suggestions
• link-checker/valid-sitemap-link (warn): checks URLs exist in the sitemap
• Scans Vue templates, TS/JS (navigateTo, router.push), and Markdown links

If you're using @nuxt/eslint, the rules are registered automatically. Otherwise, add them manually:

import linkChecker from 'nuxt-link-checker/eslint'
export default [
linkChecker,
]

Example output when a link doesn't match any route:

... (truncated)

Commits

• ab12ca3 chore: release v5.1.0
• d0fc2d1 feat: skew protection + ai ready standalone
• ccea303 chore: release v5.0.2
• e3dd45b chore: release v5.0.1
• 96eb27c chore: release v5.0.0
• 008d768 chore: sync
• 7a47f61 chore: sync
• d6ba77e chore: sync
• 64a4fcb chore: playgrounds
• c67ce91 fix(ci): use >= version constraints and fix workspace key order
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.