operation not permitted

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 16.15.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant packages:
  next: 12.3.2-canary.0
  eslint-config-next: 12.3.1
  react: 18.2.0
  react-dom: 18.2.0

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

When I run the build I have this error

> Build error occurred
[Error: EPERM: operation not permitted, scandir 'C:\Users\axell\Documents\Development\pikas-template\apps\app\.next\standalone\apps\app\node_modules\next'] {
  errno: -4048,
  code: 'EPERM',
  syscall: 'scandir',
  path: 'C:\\Users\\axell\\Documents\\Development\\pikas-template\\apps\\app\\.next\\standalone\\apps\\app\\node_modules\\next'
}

And in my next.config.js I have this

require('dotenv-flow').config({ path: '../..' });

const withPWA = require('next-pwa');
const withPlugins = require('next-compose-plugins');
const withBundleAnalyzer = require('@next/bundle-analyzer')({
  enabled: process.env.ANALYZE === 'true',
});
const { join } = require('path');
const withTM = require('next-transpile-modules')([]);

const plugins = [withTM, withBundleAnalyzer, withPWA];

/**
 * @type {import('next').NextConfig}
 */
const nextConfig = {
  swcMinify: true,
  reactStrictMode: true,
  output: 'standalone',
  experimental: {
    outputFileTracingRoot: join(__dirname, '../../'),
  },
  i18n: {
    locales: ['en', 'fr'],
    defaultLocale: 'en',
  },
  pwa: {
    disable: process.env.NODE_ENV === 'development',
    dest: 'public',
  },
};

module.exports = withPlugins(plugins, nextConfig);

I found these issues that talk about it too: #36645 #1537

Expected Behavior

I just want to build my app

Link to reproduction

https://github.com/Achaak/pikas-template

To Reproduce

Use this command

pnpm i

pnpm generate

pnpm build:packages

cd apps/app

pnpm build  <-- The bug appears here

[j2ghz]

Unfortunately, I cannot reproduce the issue myself, but it looks related to the output: "standalone" or outputFileTracingRoot settings.

To investigate further, here are some things we could try:

• Build with and without output: "standalone".

• Check if it builds when outputFileTracingRoot is not utilized

• Check a different package manager. yarn or npm, to see if the issue is pnpm-specific or not.

• It would also be nice to see if we can pinpoint exactly which version of next this bug was introduced in. (A good candidate to start bisecting is v12.1.7-canary.48, when output: "standalone" was stabilized. If the issue reproduces still, the bug might have always existed.)

• output: standalone is enough to break it, without it it works
• other package managers: npm works, yarn works
• next 12.1.7-canary.48 produces the same error, so I think it’s always been there

This is my minimal reproduction example, it’s basically just 3 steps (powershell):

# Make dir if not exists
mkdir -Force "./next-40760-repro"
# cd to it
pushd "./next-40760-repro"
# delete any content from previous run
rm * -Recurse -Force 

# create-next-app with pnpm
pnpm create next-app --ts --use-pnpm .

# add output: 'standalone' to next.config.js
[regex]$pattern = ",\s+}"
$pattern.Replace((cat "next.config.js"), ",output: 'standalone',};", 1) | Set-Content "next.config.js"

# build
pnpm next build

popd

[drewbitt]

I have just tried it in Linux and it works perfectly. So is Windows + pnpm specific. Turbotrace on Windows does not fix the issue either. And building the standalone folder on Linux, which works, and moving it to Windows and running it still causes the error.