fix: match exsolve resolution errors when @nuxt/kit is missing

Author: danielroe

packages/nuxt-cli/src/utils/kit.ts

@@ -2,6 +2,9 @@ import { pathToFileURL } from 'node:url'
 import{resolveModulePath}from'exsolve'
 import{withNodePath}from'./paths'
 
+// `exsolve` and Node.js word their resolution failures differently
+constKIT_NOT_FOUND_RE=/Cannot(?:find|resolve)module['"]@nuxt\/kit['"]/
+
 exportasyncfunctionloadKit(rootDir: string): Promise<typeofimport('@nuxt/kit')>{
 try{
 constkitPath=resolveModulePath('@nuxt/kit',{from: tryResolveNuxt(rootDir)||rootDir})
@@ -18,7 +21,7 @@ export async function loadKit(rootDir: string): Promise<typeof import('@nuxt/kit
 returnkit
 }
 catch(e: any){
-if(e.toString().includes('Cannot find module \'@nuxt/kit\'')){
+if(KIT_NOT_FOUND_RE.test(String(e))){
 thrownewError(
 'nuxi requires `@nuxt/kit` to be installed in your project. Try installing `nuxt` v3+ or `@nuxt/bridge` first.',
 )

packages/nuxt-cli/test/unit/utils/kit.spec.ts

@@ -0,0 +1,30 @@
+import{mkdtemp}from'node:fs/promises'
+import{tmpdir}from'node:os'
+import{join}from'node:path'
+importprocessfrom'node:process'
+
+import{afterEach,beforeEach,describe,expect,it}from'vitest'
+
+import{loadKit}from'../../../src/utils/kit'
+
+letnodePath: string|undefined
+
+// `vitest` points `NODE_PATH` at the pnpm store, where `@nuxt/kit` is resolvable
+beforeEach(()=>{
+nodePath=process.env.NODE_PATH
+deleteprocess.env.NODE_PATH
+})
+
+afterEach(()=>{
+process.env.NODE_PATH=nodePath
+})
+
+describe('loadKit',()=>{
+it('should explain how to install `@nuxt/kit` when it cannot be resolved',async()=>{
+constrootDir=awaitmkdtemp(join(tmpdir(),'nuxi-kit-'))
+
+awaitexpect(loadKit(rootDir)).rejects.toThrowError(
+'nuxi requires `@nuxt/kit` to be installed in your project. Try installing `nuxt` v3+ or `@nuxt/bridge` first.',
+)
+})
+})