[api-extractor] Surface bundledPackages no-op when packageId is missing (#5730)

When `bundledPackages` is configured but TypeScript could not assign a
`packageId` to a resolved module, the lookup in `_isExternalModulePath`
silently failed via optional chaining and the module was bundled as
external. The most common cause is a local workspace package whose
`package.json` lacks a `"version"` field — TypeScript does not assign
a `packageId` without one (microsoft/TypeScript#63307).

Throw an `InternalError` with a remediation message in that exact
combination (`packageId` undefined AND `_bundledPackageNames.size > 0`)
so users see the cause instead of staring at an unexpectedly-not-bundled
`from "foo"` in their `.d.ts` rollup.

The non-bundled case (`_bundledPackageNames.size === 0`) is unchanged
— the missing `packageId` flows through to the existing
`isExternalLibraryImport` check that already handles ambiguous modules.

Matches the fix suggested by the issue reporter in #5730.

Author: LeSingh1

apps/api-extractor/src/analyzer/ExportAnalyzer.ts

@@ -300,6 +300,28 @@ export class ExportAnalyzer {
       return false;
     }
 
+    // If the user configured `bundledPackages` but TypeScript could not
+    // produce a `packageId` for this module, the bundled-package lookup is
+    // guaranteed to miss it and the module will be silently treated as
+    // external (issue #5730). The most common cause is a local package
+    // whose `package.json` lacks a `"version"` field — TypeScript does not
+    // assign a `packageId` without one (microsoft/TypeScript#63307). Surface
+    // the cause with a remediable error rather than producing a confusing
+    // bundling result.
+    if (packageName === undefined && this._bundledPackageNames.size > 0) {
+      throw new InternalError(
+        `Cannot determine the package name for the module ${JSON.stringify(
+          moduleSpecifier
+        )}, but "bundledPackages" is configured. ` +
+          `This is usually because the resolved package's package.json ` +
+          `is missing a "version" field — TypeScript does not assign a ` +
+          `packageId without one (microsoft/TypeScript#63307), so the ` +
+          `bundledPackages lookup cannot match it. Add a "version" field ` +
+          `(any value works) to the package's package.json and re-run.\n` +
+          SourceFileLocationFormatter.formatDeclaration(importOrExportDeclaration)
+      );
+    }
+
     if (resolvedModule.isExternalLibraryImport === undefined) {
       // This presumably means the compiler couldn't figure out whether the module was external, but we're not
       // sure how this can happen.

common/changes/@microsoft/api-extractor/fix-bundled-packages-missing-version_2026-05-27-19-00.json

@@ -0,0 +1,10 @@
+{
+  "changes": [
+    {
+      "packageName": "@microsoft/api-extractor",
+      "comment": "Throw an actionable InternalError instead of silently failing to bundle when bundledPackages is configured but TypeScript could not assign a packageId to the resolved module (most often because the package's package.json is missing a \"version\" field).",
+      "type": "patch"
+    }
+  ],
+  "packageName": "@microsoft/api-extractor"
+}