@axlsdk/axl 0.17.1 → 0.17.2

package/dist/index.d.cts

@@ -2573,10 +2573,18 @@ declare function expandGlob(pattern: string, cwd: string): string[];
  * `exports` use a `development` condition to point at `.ts` source instead
  * of built `dist`.
  *
- * Caveat: ESM-only. CJS `require()` chains bypass the hook. Files tsx
- * compiles to CJS (`.cts`, or `.ts` in a package without
- * `"type": "module"`) issue `require()` calls that don't see the extra
- * conditions — workaround is to add `"type": "module"` or rename to `.mts`.
+ * Caveat: ESM-only. `node:module.register()` only installs ESM resolve
+ * hooks; Node's CJS resolver never sees them. So when tsx compiles a
+ * `.ts` file in a CJS-typed package, its `import` statements become
+ * `require()` calls, those `require()`s use the CJS resolver, and the
+ * extra conditions don't propagate — meaning a workspace package whose
+ * `exports.development → "./src/foo.ts"` resolves to the `default`
+ * entry (e.g. built `./dist/foo.js`) instead of the `.ts` source. This
+ * is independent of the `tsx/cjs/api` hook (which fixes `.ts` *file
+ * loading* under require, but can't make the CJS resolver consult ESM
+ * conditions). Workaround for full condition coverage: add
+ * `"type": "module"` to the importer's package, or rename it to `.mts`,
+ * so its internal imports stay as `import` and hit the ESM resolve hook.
  *
  * @internal
  */

package/dist/index.d.ts

@@ -2573,10 +2573,18 @@ declare function expandGlob(pattern: string, cwd: string): string[];
  * `exports` use a `development` condition to point at `.ts` source instead
  * of built `dist`.
  *
- * Caveat: ESM-only. CJS `require()` chains bypass the hook. Files tsx
- * compiles to CJS (`.cts`, or `.ts` in a package without
- * `"type": "module"`) issue `require()` calls that don't see the extra
- * conditions — workaround is to add `"type": "module"` or rename to `.mts`.
+ * Caveat: ESM-only. `node:module.register()` only installs ESM resolve
+ * hooks; Node's CJS resolver never sees them. So when tsx compiles a
+ * `.ts` file in a CJS-typed package, its `import` statements become
+ * `require()` calls, those `require()`s use the CJS resolver, and the
+ * extra conditions don't propagate — meaning a workspace package whose
+ * `exports.development → "./src/foo.ts"` resolves to the `default`
+ * entry (e.g. built `./dist/foo.js`) instead of the `.ts` source. This
+ * is independent of the `tsx/cjs/api` hook (which fixes `.ts` *file
+ * loading* under require, but can't make the CJS resolver consult ESM
+ * conditions). Workaround for full condition coverage: add
+ * `"type": "module"` to the importer's package, or rename it to `.mts`,
+ * so its internal imports stay as `import` and hit the ESM resolve hook.
  *
  * @internal
  */

package/dist/index.js

@@ -7925,15 +7925,23 @@ var tsxRegistered;
 async function ensureTsxRegistered() {
   if (tsxRegistered !== void 0) return tsxRegistered;
   try {
-    const mod = await import("tsx/esm/api");
-    if (typeof mod.register === "function") {
-      mod.register();
-      tsxRegistered = true;
-    } else {
+    const esm = await import("tsx/esm/api");
+    if (typeof esm.register !== "function") {
       tsxRegistered = false;
+      return tsxRegistered;
     }
+    esm.register();
+    tsxRegistered = true;
   } catch {
     tsxRegistered = false;
+    return tsxRegistered;
+  }
+  try {
+    const cjs = await import("tsx/cjs/api");
+    if (typeof cjs.register === "function") {
+      cjs.register();
+    }
+  } catch {
   }
   return tsxRegistered;
 }