@vercel/microfrontends 1.4.0-canary.0 → 1.4.0-canary.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @vercel/microfrontends
 
+## 1.4.0-canary.1
+
+### Patch Changes
+
+- Update the logic for which require function to use to be compatible with tsup/esbuild.
+
 ## 1.4.0-canary.0
 
 ### Minor Changes

package/dist/bin/cli.cjs

@@ -30,7 +30,7 @@ var import_env = require("@next/env");
 // package.json
 var package_default = {
   name: "@vercel/microfrontends",
-  version: "1.4.0-canary.0",
+  version: "1.4.0-canary.1",
   private: false,
   description: "Defines configuration and utilities for microfrontends development",
   keywords: [

package/dist/next/config.cjs

@@ -1704,7 +1704,6 @@ var SortChunksPlugin = class {
 
 // src/next/config/transforms/webpack.ts
 var import_meta = {};
-var cjsRequire = typeof require === "function" ? require : (0, import_node_module.createRequire)(import_meta.url);
 var nextVersion = getNextJsVersion();
 function transform6(args) {
   const useDefineServer = args.opts?.preferWebpackEnvironmentPlugin ? false : semver.gte(nextVersion, "15.4.0-canary.41");
@@ -1763,8 +1762,15 @@ function transform6(args) {
   };
 }
 function getNextJsVersion() {
+  const cjsRequire = (
+    // This is used so we can use `require.resolve` to find the Next.js package:
+    // - `import.meta.resolve` is not available in CJS or early Node.js versions.
+    // - tsup/esbuild don't generate import meta urls for CJS modules, so use this as
+    // a test to see if we're running in ESM. Referencing `import.meta.url` is
+    // still grammatically valid in CJS because esbuild transforms it.
+    typeof import_meta.url === "string" ? (0, import_node_module.createRequire)(import_meta.url) : require
+  );
   const parsedNextPackageJson = JSON.parse(
-    // `import.meta.url` is not available in CJS or early Node.js versions
     import_node_fs8.default.readFileSync(cjsRequire.resolve("next/package.json"), "utf8")
   );
   if (typeof parsedNextPackageJson !== "object" || parsedNextPackageJson === null) {