fix(turbopack): add no-op resolveAbsolutePath to browser runtime

crates/turbopack-ecmascript-runtime/js/src/browser/dev/runtime/base/runtime-base.ts

@@ -365,6 +365,7 @@ function instantiateModule(id: ModuleId, source: SourceInfo): Module {
           w: loadWebAssembly.bind(null, sourceInfo),
           u: loadWebAssemblyModule.bind(null, sourceInfo),
           g: globalThis,
+          P: resolveAbsolutePath,
           U: relativeURL,
           k: refresh,
           R: createResolvePathFromModule(r),
@@ -386,6 +387,14 @@ function instantiateModule(id: ModuleId, source: SourceInfo): Module {
   return module;
 }
 
+/**
+ * no-op for browser
+ * @param modulePath
+ */
+function resolveAbsolutePath(modulePath?: string): string {
+  return `/ROOT/${modulePath ?? ""}`;
+}
+
 /**
  * NOTE(alexkirsz) Webpack has a "module execution" interception hook that
  * Next.js' React Refresh runtime hooks into to add module context to the

crates/turbopack-ecmascript-runtime/js/src/nodejs/runtime.ts

@@ -36,10 +36,8 @@ function stringifySourceInfo(source: SourceInfo): string {
 
 type ExternalRequire = (id: ModuleId) => Exports | EsmNamespaceObject;
 type ExternalImport = (id: ModuleId) => Promise<Exports | EsmNamespaceObject>;
-type ResolveAbsolutePath = (modulePath?: string) => string;
 
 interface TurbopackNodeBuildContext extends TurbopackBaseContext {
-  P: ResolveAbsolutePath;
   R: ResolvePathFromModule;
   x: ExternalRequire;
   y: ExternalImport;

crates/turbopack-ecmascript-runtime/js/src/shared/runtime-types.d.ts

@@ -53,6 +53,8 @@ type AsyncModule = (
   hasAwait: boolean
 ) => void;
 
+type ResolveAbsolutePath = (modulePath?: string) => string;
+
 interface TurbopackBaseContext {
   a: AsyncModule;
   e: Module["exports"];
@@ -71,6 +73,7 @@ interface TurbopackBaseContext {
   w: LoadWebAssembly;
   u: LoadWebAssemblyModule;
   g: typeof globalThis;
+  P: ResolveAbsolutePath;
   U: RelativeURL;
   __dirname: string;
 }