remove absolute check

Author: james-elicx

.changeset/three-oranges-whisper.md

@@ -2,8 +2,6 @@
 "@opennextjs/aws": minor
 ---
 
-fix: support absolute paths for OpenNext configs
+fix: support absolute paths for OpenNext config compilation utility
 
 Compiling OpenNext configs will now support the ability to pass in either absolute or relative paths, instead of treating any input as a relative path.
-
-Further, the CLI will now treat absolute paths as absolute, instead of always treating them as relative. Relative paths should not start with a `/`, i.e. you should use `./config-path.ts` instead of `/config-path.ts`.

packages/open-next/src/build.ts

@@ -33,9 +33,7 @@ export async function build(
   const openNextDistDir = url.fileURLToPath(new URL(".", import.meta.url));
 
   const { config, buildDir } = await compileOpenNextConfig(
-    openNextConfigPath && path.isAbsolute(openNextConfigPath)
-      ? openNextConfigPath
-      : path.join(baseDir, openNextConfigPath ?? "open-next.config.ts"),
+    path.join(baseDir, openNextConfigPath ?? "open-next.config.ts"),
     { nodeExternals },
   );