You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it's some file deletion method in Next will recursive delete file in folder symlink, because there's a node_module with symlink produced by pnpm when set NEXT_PRIVATE_STANDALONE: "true"
The text was updated successfully, but these errors were encountered:
I have tried running a sample next.js app from the examples using the adapter with admin rights (pwsh). It works the first time but throws a bunch of errors the second time as shown below.
First time: pnpm --filter api preview:worker
Second time: pnpm --filter api build:worker
It looks like, most data from node_modules and the .next dir are being removed and the adapter is looking for something that doesn't exist.
I will try and see why but I hope it helps anyone looking into it!
To get it working, I has to delete the node_modules on the root and the api example project and run pnpm i again
When I execute
npm run build:worker
for the second time, build will be failed with the following errorIf I
ls D:\project-dir\node_modules\.pnpm\[email protected][email protected][email protected][email protected][email protected]\node_modules\next\
will get an empty dir. It is normal before the second build.I think it's some file deletion method in Next will recursive delete file in folder symlink, because there's a
node_module
with symlink produced by pnpm when setNEXT_PRIVATE_STANDALONE: "true"
The text was updated successfully, but these errors were encountered: