From 755ce6aa2e18b7b7af99850e76bbd6154469056c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 19 May 2026 08:37:43 +0000 Subject: [PATCH] Version Packages --- .changeset/inspector-windows-spawn.md | 11 ----------- apps/mcp-starter/package.json | 2 +- packages/nuxt-mcp-toolkit/CHANGELOG.md | 12 ++++++++++++ packages/nuxt-mcp-toolkit/package.json | 2 +- 4 files changed, 14 insertions(+), 13 deletions(-) delete mode 100644 .changeset/inspector-windows-spawn.md diff --git a/.changeset/inspector-windows-spawn.md b/.changeset/inspector-windows-spawn.md deleted file mode 100644 index 6f11972b..00000000 --- a/.changeset/inspector-windows-spawn.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -"@nuxtjs/mcp-toolkit": patch ---- - -Fix "spawn npx ENOENT" error when launching the MCP Inspector on Windows. - -Since the Node.js CVE-2024-27980 mitigation (Node 18.20.2 / 20.12.2), `child_process.spawn` no longer resolves `.cmd`/`.bat` shims on Windows without `shell: true`. This caused the DevTools "Launch Inspector" button to throw `ENOENT` on every Windows machine. - -`shell: true` is now passed only when `process.platform === 'win32'`, leaving the default behaviour unchanged on Linux and macOS. - -Closes #259. diff --git a/apps/mcp-starter/package.json b/apps/mcp-starter/package.json index dd7553a2..fe477cfa 100644 --- a/apps/mcp-starter/package.json +++ b/apps/mcp-starter/package.json @@ -17,7 +17,7 @@ "lint:fix": "eslint . --fix" }, "dependencies": { - "@nuxtjs/mcp-toolkit": "^0.17.0", + "@nuxtjs/mcp-toolkit": "^0.17.1", "nuxt": "^4.4.6", "zod": "^4.1.13" }, diff --git a/packages/nuxt-mcp-toolkit/CHANGELOG.md b/packages/nuxt-mcp-toolkit/CHANGELOG.md index 08dba19e..bcc3120b 100644 --- a/packages/nuxt-mcp-toolkit/CHANGELOG.md +++ b/packages/nuxt-mcp-toolkit/CHANGELOG.md @@ -1,5 +1,17 @@ # @nuxtjs/mcp-toolkit +## 0.17.1 + +### Patch Changes + +- [#261](https://github.com/nuxt-modules/mcp-toolkit/pull/261) [`500c43e`](https://github.com/nuxt-modules/mcp-toolkit/commit/500c43e6ef0befdff47e2c574f8615594c68e47e) Thanks [@HugoRCD](https://github.com/HugoRCD)! - Fix "spawn npx ENOENT" error when launching the MCP Inspector on Windows. + + Since the Node.js CVE-2024-27980 mitigation (Node 18.20.2 / 20.12.2), `child_process.spawn` no longer resolves `.cmd`/`.bat` shims on Windows without `shell: true`. This caused the DevTools "Launch Inspector" button to throw `ENOENT` on every Windows machine. + + `shell: true` is now passed only when `process.platform === 'win32'`, leaving the default behaviour unchanged on Linux and macOS. + + Closes [#259](https://github.com/nuxt-modules/mcp-toolkit/issues/259). + ## 0.17.0 ### Minor Changes diff --git a/packages/nuxt-mcp-toolkit/package.json b/packages/nuxt-mcp-toolkit/package.json index a0d7ab67..5d50412c 100644 --- a/packages/nuxt-mcp-toolkit/package.json +++ b/packages/nuxt-mcp-toolkit/package.json @@ -1,6 +1,6 @@ { "name": "@nuxtjs/mcp-toolkit", - "version": "0.17.0", + "version": "0.17.1", "description": "Create MCP servers directly in your Nuxt application. Define tools, resources, and prompts with a simple and intuitive API.", "repository": { "type": "git",