fix: copy Next static exports with fs.promises.cp

The sync variant's native directory copy fails (EACCES) on shared-mount
filesystems (virtiofs, Docker Desktop mounts), breaking the workspace
build there.

Author: antfubot

examples/next-runtime-snapshot/scripts/build-spa.mjs

@@ -1,9 +1,13 @@
-import { chmodSync, cpSync, mkdirSync, readdirSync, rmSync } from 'node:fs'
+import { chmodSync, mkdirSync, readdirSync, rmSync } from 'node:fs'
+import { cp } from 'node:fs/promises'
 import { join } from 'node:path'
 
 rmSync('dist/client', { recursive: true, force: true })
 mkdirSync('dist', { recursive: true })
-cpSync('src/client/out', 'dist/client', { recursive: true })
+// `fs.promises.cp` rather than `cpSync`: the sync variant's native directory
+// copy fails (EACCES) on shared-mount filesystems (e.g. virtiofs, Docker
+// Desktop mounts).
+await cp('src/client/out', 'dist/client', { recursive: true })
 
 // A built SPA must be readable to be served. Some filesystems (e.g. Docker
 // Desktop's shared mounts) drop the read bits when copying, which yields

plugins/git/scripts/build-spa.mjs

@@ -1,6 +1,9 @@
-import { cpSync, rmSync } from 'node:fs'
+import { cp, rm } from 'node:fs/promises'
 
 // The Next.js static export is the plugin's iframe SPA; it ships in the
 // lockstep `@devframes/plugin-git--assets` package, not the node package.
-rmSync('assets-pkg/dist', { recursive: true, force: true })
-cpSync('src/client/out', 'assets-pkg/dist', { recursive: true })
+// `fs.promises.cp` rather than `cpSync`: the sync variant's native directory
+// copy fails (EACCES) on shared-mount filesystems (e.g. virtiofs, Docker
+// Desktop mounts).
+await rm('assets-pkg/dist', { recursive: true, force: true })
+await cp('src/client/out', 'assets-pkg/dist', { recursive: true })