EEXIST: file already exists, symlink when build nextjs standalone mode twice

[nhducit]

pnpm version:

7.0.0

Code to reproduce the issue:

https://github.com/nhducit/pnpm-nextjs-standalone

Expected behavior:

build success

Actual behavior:

web:build: > Build error occurred
web:build: [Error: EEXIST: file already exists, symlink '../../../@next+env@12.1.6/node_modules/@next/env' -> '/Users/ducnguyen/Documents/code/pnpm-test/apps/web/node_modules/.pnpm/next@12.1.6_ef5jwxihqo6n7gxfmzogljlgcm/node_modules/@next/env'] {

Additional information:

• node -v prints: v16.13.2
• Windows, macOS, or Linux?: macOS 12.3.1
• I'm not sure is this a pnpm or next.js bug.

[zkochan]

It doesn't look related to pnpm. You run turbo which runs next. How is pnpm involved?

[await-ovo]

I think setting experimental.outputFileTracingRoot should solve this problem.
https://nextjs.org/docs/advanced-features/output-file-tracing#caveats

[hugovntr]

Sorry to bump this issue, unfortunately it seems to be an issue with PNPM itself.

I use a similar setup than the one linked by @nhducit (2 nextjs apps and a packages folder) without turborepo and it does the same thing.
On a first compilation it all runs great, but fails afterwards.

The temporary fix that I found for it is rm -rf apps/MY_APP/node_modules/.pnpm/*. I assume this is not the proper way to do it, but it does the trick

[nhducit]

Let me try repro with yarn

[mindyourlifeguide]

I confirm the issue. I have pnpm + next and it does not work when I rebuild it.

[mindyourlifeguide]

await-ovo workaround works.
Thanks, @await-ovo

[mindyourlifeguide]

Hastened to conclusions - the problem is not solved.

[kilemensi]

Ran into this issue on v7.3.0 but bumping to the recently released PNPM v7.4.0 and Next.js v12.2.0 appears to fix it @nhducit @hugovntr @mindyourlifeguide

[teddybee]

I still have this issue with pnpm 7.28 and nextjs 13.2.3 at the end of vercel build.