[windows] Specify the file:// protocol when importing config on Win…

…dows (#460) * [windows] Specify the `file://` protocol when importing config on Windows On Windows, if the file protocol is not specified when using dynamic imports, the process exits with ERR_UNSUPPORTED_ESM_URL_SCHEME error. Signed-off-by: Costin Sin <[email protected]> * Create witty-dots-film.md --------- Signed-off-by: Costin Sin <[email protected]> Co-authored-by: conico974 <[email protected]>
opennextjs · Jul 8, 2024 · e2d0c7f · e2d0c7f
1 parent 001aaa0
commit e2d0c7f
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/.changeset/witty-dots-film.md b/.changeset/witty-dots-film.md
@@ -0,0 +1,5 @@
+---
+"open-next": patch
+---
+
+[windows] Specify the `file://` protocol when importing config on Windows
diff --git a/packages/open-next/src/build.ts b/packages/open-next/src/build.ts
@@ -50,11 +50,13 @@ export async function build(
 
   // Load open-next.config.ts
   const tempDir = initTempDir();
-  const configPath = compileOpenNextConfigNode(
+  let configPath = compileOpenNextConfigNode(
     tempDir,
     openNextConfigPath,
     nodeExternals,
   );
+  // On Windows, we need to use file:// protocol to load the config file using import()
+  if (process.platform === "win32") configPath = `file://${configPath}`;
   config = (await import(configPath)).default as OpenNextConfig;
   validateConfig(config);