output: 'standalone' error: ENOENT: no such file or directory, lstat .next/server/app

[khteh]

Verify canary release

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

Provide environment information

"next": "13.0.6",

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue

private repo

To Reproduce

Buildind a output: 'standalone' application bumps into the following build error:

       > Build error occurred
       [Error: ENOENT: no such file or directory, lstat '/apps/api/.next/server/app'] {
         errno: -2,
         code: 'ENOENT',
         syscall: 'lstat',
         path: '/apps/api/.next/server/app'
       }

Describe the Bug

Building a output: 'standalone' application bumps into the following build error:

       > Build error occurred
       [Error: ENOENT: no such file or directory, lstat '/apps/api/.next/server/app'] {
         errno: -2,
         code: 'ENOENT',
         syscall: 'lstat',
         path: '/apps/api/.next/server/app'
       }

Expected Behavior

No build error

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[DuCanhGH]

Can you make a minimal reproduction? It's not like you have to link to your actual repo as using actual repos makes it hard to find the issue anyway. This doesn't seem to be happening to me...

[baronha]

I have the same issue

[ovasylenko]

Temporary hotfix

"build": "next build; bash -c 'sleep 10 && mkdir -p ./.next/server/app'"

It creates an app folder. The issue that builds does not create a folder .next/server/app if created during the build - build passes with no issues.

It is not a solid solution. Just a temporary workaround for everyone stuck

[khteh]

Temporary hotfix

"build": "next build; bash -c 'sleep 10 && mkdir -p ./.next/server/app'"

It creates an app folder. The issue that builds does not create a folder .next/server/app if created during the build - build passes with no issues.

It is not a solid solution. Just a temporary workaround for everyone stuck

How about removing appDir: true from the experimental section of the file?

[ricardobrandao]

Hi,

Same issue occurring here and it only breaks when the appDir: true flag is on. This started happening at least on next@13.0.7 but is working fine on next@13.0.4

[BoBoooooo]

any solutions ?

[castrix]

it's happening on 13.4.2 as well.

I'm not using appDir flag. here is my next.config.js:

module.exports = {
  output: 'standalone',
};

[nipunahh]

Any solutions for this?

UPDATE:
Fixed by commenting out output:"standalone" and setting appDir: true

const nextConfig = {
    reactStrictMode: true,
    // output: 'standalone',
    swcMinify: false,
    experimental: {
        appDir: true,
}
}

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.