fix: patch upstream pnpm issue

Author: mrstork

src/build/content/server.ts

@@ -299,7 +299,12 @@ export const copyNextDependencies = async (ctx: PluginContext): Promise<void> =>
       }
       const src = join(ctx.standaloneDir, entry)
       const dest = join(ctx.serverHandlerDir, entry)
-      await cp(src, dest, { recursive: true, verbatimSymlinks: true, force: true })
+      await cp(src, dest, {
+        recursive: true,
+        verbatimSymlinks: true,
+        force: true,
+        filter: nodeModulesFilter,
+      })
 
       if (entry === 'node_modules') {
         await recreateNodeModuleSymlinks(ctx.resolveFromSiteDir('node_modules'), dest)
@@ -438,3 +443,21 @@ export const verifyHandlerDirStructure = async (ctx: PluginContext) => {
     )
   }
 }
+
+// This is a workaround for Next.js installations in a pnpm+glibc context
+// Patch required due to an intermittent upstream issue in the npm/pnpm ecosystem
+// https://github.com/pnpm/pnpm/issues/9654
+// https://github.com/pnpm/pnpm/issues/5928
+// https://github.com/pnpm/pnpm/issues/7362 (persisting even though ticket is closed)
+const nodeModulesFilter = async (sourcePath: string) => {
+  // Filtering rule for the following packages:
+  // - @rspack+binding-linux-x64-musl
+  // - @swc+core-linux-x64-musl
+  // - @img+sharp-linuxmusl-x64
+  // - @img+sharp-libvips-linuxmusl-x64
+  if (sourcePath.includes('linuxmusl-x64') || sourcePath.includes('linux-x64-musl')) {
+    return false
+  }
+
+  return true
+}