fix(nuxt): provide node16-style type exports

[danielroe]

🔗 Linked issue

#19606

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR makes some updates to Nuxt internals to improve support for Node16-style module resolution.

👉 Current status

nuxt v3.2.3

	"nuxt"	"nuxt/config"	"nuxt/schema"	"nuxt/app"	"nuxt/package.json"
node10	✅	✅	✅	✅	✅ (JSON)
node16 (from CJS)	❌ No types ⚠️ ESM (dynamic import only)	👺 Masquerading as ESM ⚠️ ESM (dynamic import only)	⚠️ ESM (dynamic import only)	❌ No types ⚠️ ESM (dynamic import only)	✅ (JSON)
node16 (from ESM)	❌ No types	✅ (ESM)	✅ (ESM)	❌ No types	✅ (JSON)
bundler	❌ No types	✅	✅	❌ No types	✅ (JSON)

nuxt (edge)

	"nuxt3"	"nuxt3/config"	"nuxt3/schema"	"nuxt3/kit"	"nuxt3/app"	"nuxt3/package.json"
node10	✅	✅	✅	✅	✅	✅ (JSON)
node16 (from CJS)	❌ No types ⚠️ ESM (dynamic import only)	👺 Masquerading as ESM ⚠️ ESM (dynamic import only)	⚠️ ESM (dynamic import only)	⚠️ ESM (dynamic import only)	❌ No types ⚠️ ESM (dynamic import only)	✅ (JSON)
node16 (from ESM)	❌ No types	✅ (ESM)	✅ (ESM)	✅ (ESM)	❌ No types	✅ (JSON)
bundler	❌ No types	✅	✅	✅	❌ No types	✅ (JSON)

after this pr

	"nuxt"	"nuxt/config"	"nuxt/schema"	"nuxt/kit"	"nuxt/app"	"nuxt/package.json"
node10	✅	✅	✅	✅	✅	✅ (JSON)
node16 (from CJS)	⚠️ ESM (dynamic import only)	👺 Masquerading as ESM ⚠️ ESM (dynamic import only)	⚠️ ESM (dynamic import only)	⚠️ ESM (dynamic import only)	⚠️ ESM (dynamic import only)	✅ (JSON)
node16 (from ESM)	✅ (ESM)	✅ (ESM)	✅ (ESM)	✅ (ESM)	✅ (ESM)	✅ (JSON)
bundler	✅	✅	✅	✅	✅	✅ (JSON)

See https://arethetypeswrong.github.io.

the remaining blockers for full support for Node16 format can be tracked in #19606.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[dargmuesli]

minor notice: the issue mentioned is not linked properly because of a typo in "resolves" 🤫

[pi0]

Nice work on this 🔥

[danielroe]

Okay, so that's why I kept it in: https://github.com/nuxt/nuxt/actions/runs/4363710497/jobs/7630133013

[pi0]

Strange... It is vitest or jiti? (jiti fallsback to import condition and we have enabled this behavior)

[danielroe]

I think it's neither - I think it's the call to _require.resolve in our deprecated cjs utils in kit:

nuxt/packages/nuxi/src/utils/cjs.ts

Lines 20 to 22 in e05f8ee

	export function resolveModule (id: string, paths?: string | string[]) {
	return normalize(_require.resolve(id, { paths: getModulePaths(paths) }))
	}

(Though this might then be jiti.)

Replicable with built monorepo:

./packages/nuxi/bin/nuxi.mjs prepare test/fixtures/basic