packages/kit/src/internal/esm.ts (1)

36-41: Avoid shadowing exsolve’s built-in extension list

By unconditionally supplying our own default list we start to drift from exsolve’s evolving defaults (and today we already omit values like .node). That regression bites anyone relying on those built-ins unless they set extensions themselves. Let’s only pass extensions when the caller provides them so we preserve existing behaviour.

 export function resolveModule (id: string, options?: ResolveModuleOptions) {
-  return resolveModulePath(id, {
-    // eslint-disable-next-line @typescript-eslint/no-deprecated
-    from: options?.url ?? options?.paths ?? [import.meta.url],
-    extensions: options?.extensions ?? ['.js', '.mjs', '.cjs', '.ts', '.mts', '.cts'],
-  })
+  return resolveModulePath(id, {
+    // eslint-disable-next-line @typescript-eslint/no-deprecated
+    from: options?.url ?? options?.paths ?? [import.meta.url],
+    ...(options?.extensions ? { extensions: options.extensions } : {}),
+  })
 }

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Learnt from: GalacticHypernova
PR: nuxt/nuxt#29661
File: packages/kit/src/template.ts:227-229
Timestamp: 2024-11-28T21:22:40.496Z
Learning: In `packages/kit/src/template.ts`, when updating the `EXTENSION_RE` regular expression for TypeScript configuration, avoid using patterns like `(\.\w+)+$` as they can result in catastrophic backtracking.