chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@iconify-json/lucide	^1.2.75 -> ^1.2.81
@iconify-json/simple-icons	^1.2.60 -> ^1.2.63
@iconify-json/vscode-icons	^1.2.36 -> ^1.2.37
@nuxt/content (source)	^3.8.2 -> ^3.9.0
@nuxt/eslint (source)	^1.10.0 -> ^1.12.1
@nuxtjs/mcp-toolkit (source)	0.5.1 -> 0.5.2
better-sqlite3	^12.4.6 -> ^12.5.0
eslint (source)	^9.39.1 -> ^9.39.2
nuxt-og-image (source)	^5.1.12 -> ^5.1.13
pnpm (source)	10.23.0 -> 10.26.0
vue-tsc (source)	^3.1.5 -> ^3.1.8
zod (source)	^4.1.13 -> ^4.2.1

---

Release Notes

nuxt/content (@​nuxt/content)

v3.9.0

Compare Source

Features

• amplity: usenode:sqlite on AWS Amplify if Node.js > 22 (#​3598) e74bb6d

Bug Fixes

• fs-watcher: add timeout to deal with race-condition c07336e
• prepare for NuxtHub 0.10 with hub.db (#​3624) 8a9f9d3
• respect app.baseURL in Cloudflare database handler (#​3608) 1af6adc

nuxt/eslint (@​nuxt/eslint)

v1.12.1

Compare Source

No significant changes

    View changes on GitHub

v1.11.0

Compare Source

   🚀 Features

• Allow config key sorting on files not named nuxt.config  -  by @​benedictleejh in #​630 (be2e9)

    View changes on GitHub

nuxt-modules/mcp-toolkit (@​nuxtjs/mcp-toolkit)

v0.5.2

Compare Source

What's Changed

Bug Fixes 🐞

• fix: prevents usage with nuxt generate by @​HugoRCD in #​47
• fix: exclude declaration files from file pattern generation by @​HugoRCD in #​48

Full Changelog: nuxt-modules/mcp-toolkit@v0.5.1...v0.5.2

WiseLibs/better-sqlite3 (better-sqlite3)

v12.5.0

Compare Source

What's Changed

• Update SQLite to version 3.51.1 in #​1424

Full Changelog: WiseLibs/better-sqlite3@v12.4.6...v12.5.0

eslint/eslint (eslint)

v9.39.2

Compare Source

nuxt-modules/og-image (nuxt-og-image)

v5.1.13

Compare Source

   🐞 Bug Fixes

• Updated wasm satori API  -  by @​harlan-zw (c330a)
• Handle _query in og-image without breaking render path  -  by @​JackTYM (2e5bd)
• content: Prefer users zod version  -  by @​harlan-zw (e9550)

    View changes on GitHub

pnpm/pnpm (pnpm)

v10.26.0

Compare Source

v10.25.0

Compare Source

v10.24.0

Compare Source

vuejs/language-tools (vue-tsc)

v3.1.8

Compare Source

Features

• feat(vscode): support multiline attribute for <script> and <style> tag (#​5830) - Thanks to @​serkodev!
• feat(vscode): supports format with selected range (#​5761) - Thanks to @​serkodev!
• feat(language-service): add tsconfig-based document link support for Pug

Bug Fixes

• fix(language-core): limit the range of parseDiagnostics checks (#​5823)
• fix(language-core): restore default import bindings for template scope (#​5824) - Thanks to @​serkodev!
• fix(typescript-plugin): get preferences and formatOptions in tsserver (#​5829)
• fix(language-core): avoid generating component options within the setup scope (#​5832)

Other Changes

• perf(language-core): dedupe component options generation (#​5831)

v3.1.7

Compare Source

v3.1.6

Compare Source

Features

• feat(vscode): add settings to enable per-block formatting (#​5784) - Thanks to @​serkodev!
• feat(language-service): enhanced component auto import (#​5790)
• feat(component-meta): add component name and description fields (#​5797)
• feat(typescript-plugin): add support for template "Add Import" quick fix (#​5799) - Thanks to @​serkodev!
• feat(typescript-plugin): mapping JSDoc informations from <script setup> (#​5805)
• feat(vscode): support tsdk path for Eclipse Theia (#​5806) - Thanks to @​serkodev!

Bug Fixes

• fix(language-service): ignore intrinsic elements when detect tag name casing (#​5771)
• fix(language-core): createParsedCommandLineByJson parsed incorrect options since v3.1.5 (#​5768 (comment))
• fix(vscode): make vue.server.path compatible with Windows (#​5772)
• fix(vscode): analyze interpolation highlight ranges based on AST (#​5777)
• fix(vscode): sync latest vscode html language configuration (#​5740)
• fix(language-core): enhance getVIfNode to support v-else-if directives (#​5765) - Thanks to @​serkodev!
• fix(language-core): generate {} instead of its string value for style="..." (#​5781) - Thanks to @​KazariEX!
• fix(language-core): v-bind="$attrs" loses navigation when inferTemplateDollarAttrs is disabled (#​5783)
• fix(language-service): skip const props = completion in StringLiteral (#​5786)
• fix(language-core): unable to get completion for the second scoped class name
• fix(language-service): format components with HTML void-element names (#​5788) - Thanks to @​serkodev!
• fix(language-service): properly handle promise when resolving CSS links (#​5785)
• fix(language-core): infer $el type for generic components using inferComponentDollarEl (#​5794)
• fix(language-core): ensure <script> content generates before <script setup> (#​5795)
• fix(language-core): remove bypassDefineComponent hack for better JS support (#​4876) (#​5379)
• fix(language-core): Prettify<T> caused generic props gets inferred as unknown (#​5667) - Thanks to @​so1ve!
• fix(vscode): handle leading < as operator in SFC scripts (#​5801) - Thanks to @​serkodev!
• fix(vscode): patch isTypeScriptDocument in VSCode for typescript.preferences.autoImportSpecifierExcludeRegexes config support (#​5364)
• fix(language-core): ensure type consistency for optional boolean props (#​5803)
• fix(language-core): add compatibility for vapor attr (#​5496)
• fix(language-core): AST fault tolerance for key binding on template (#​5807)

Performance

• perf(language-core): reuse ts asts for :class - Thanks to @​KazariEX!

Other Changes

• Revert "refactor(typescript-plugin): remove go to definition trick for auto imported components (#​5733)"
• docs(typescript-plugin): update Neovim configuration link (#​5775) - Thanks to @​AlexVagrant!
• refactor(language-core): normalize template AST (#​5782)
• refactor(language-core): split style codegen (#​5787)
• refactor(language-core): remove debugger from virtual code for tsslint compatibility
• refactor(language-core): remove legacy navigation support in ref="xxx"
• refactor(language-core): reduce codegen options (#​5804)
• refactor(component-meta): deprecated rawType and __internal__.tsLs (#​5808)
• chore: update volar to 2.4.26
  • feat: fallback resolution mode for createResolveModuleName (volarjs/volar.js#293) (#​5644) - Thanks to @​serkodev!

colinhacks/zod (zod)

v4.2.1

Compare Source

v4.2.0

Compare Source

Features

Implement Standard JSON Schema

standard-schema/standard-schema#134

Implement z.fromJSONSchema()

const jsonSchema = {
  type: "object",
  properties: {
    name: { type: "string" },
    age: { type: "number" }
  },
  required: ["name"]
};

const schema = z.fromJSONSchema(jsonSchema);

Implement z.xor()

const schema = z.xor(
  z.object({ type: "user", name: z.string() }),
  z.object({ type: "admin", role: z.string() })
);
// Exactly one of the schemas must match

Implement z.looseRecord()

const schema = z.looseRecord(z.string(), z.number());
// Allows additional properties beyond those defined

Commits:

• af49c08 Update docs for JSON Schema conversion of z.undefined() (#​5504)
• 767f320 Add .toJSONSchema() method (#​5477)
• e17dcb6 Add z.fromJSONSchema(), z.looseRecord(), z.xor() (#​5534)

---

Configuration

📅 Schedule: Branch creation - "on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

Suggested change

	"packageManager": "pnpm@10.25.0"
	"packageManager": "pnpm@10.25.0",
	"engines": {
	"node": ">= 20.19.0"
	}

The package.json doesn't specify a Node.js engine requirement, but the newly updated @nuxt/content@3.9.0 requires Node.js >= 20.19.0. This could cause runtime failures if someone installs dependencies on an older Node.js version.

View Details

Analysis

Missing Node.js engine requirement in package.json

What fails: The @nuxt/content@3.9.0 dependency requires Node.js >= 20.19.0 (as specified in pnpm-lock.yaml), but package.json lacks an engines field to document this requirement.

How to reproduce:

1. Clone the repository
2. Check package.json - no engines field present
3. Compare with pnpm-lock.yaml line 915: engines: {node: '>= 20.19.0'}
4. Note that @nuxt/content is not the only dependency with this requirement - the entire project requires Node 20+

Result: Without an engines field, developers and tooling cannot easily determine the minimum Node.js version requirement from package.json. While pnpm still allows installation on incompatible Node versions (with warnings), the explicit documentation is missing.

Expected: package.json should include an engines field documenting the minimum Node.js version requirement, aligning with:

• Nuxt 4 installation requirements: Node.js 20.x or newer
• @nuxt/content@3.9.0 requirement: Node.js >= 20.19.0
• Industry best practices used by the official Nuxt packages

Fix applied: Added "engines": { "node": ">= 20.19.0" } to package.json, matching the most restrictive dependency requirement.