[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 <sin.costinrobert@gmail.com>

* Create witty-dots-film.md

---------

Signed-off-by: Costin Sin <sin.costinrobert@gmail.com>
Co-authored-by: conico974 <nicodorseuil@yahoo.fr>

.changeset/witty-dots-film.md

@@ -0,0 +1,5 @@
+---
+"open-next": patch
+---
+
+[windows] Specify the `file://` protocol when importing config on Windows

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);