Version 0.4.1 prevents Vercel to build the project

[ozgur-dogan]

Describe the bug

When the library updated from 0.4.0 to 0.4.1, Vercel builds throws an error as below. Local builds complete without any issue.

Next.js version 14.2.16

Error: ENOENT: no such file or directory, lstat '/vercel/path0/.next/export-detail.json'

Reproduction

Update the library to 0.4.1 and push to Vercel for build

System Info

Vercel with Node 20
Next.js version 14.2.16
next-swagger-doc 0.4.1

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

[mbramani]

I’m also experiencing this issue after updating next-swagger-doc from 0.4.0 to 0.4.1. The Vercel build fails with the following error, although local builds complete successfully:

Error: ENOENT: no such file or directory, lstat '/vercel/path0/.next/export-detail.json'

Reverting back to version 0.4.0 fixed the problem, so it seems to be related to the changes in 0.4.1.

Here’s my repository for reference: GitHub Repo.

[jellydn]

Thank you all. I will check and get back on this issue soon.

[jellydn]

Hi @mbramani Could you show me the full error logs on Vercel? Thanks.

[gadcam]

Hello @jellydn,
I had to downgrade for the same reason and it seems to be the only difference in the build logs

What information would be useful to debug this ?

[jellydn]

Ok, let me deploy the examples app to Vercel and test. Thanks.

[jellydn]

I could reproduce the issue with examples/next14-app on Vercel as well.

https://paste.ofcode.org/cDsjZqxbj2rPT8RFvPGNM6

I'm not sure what is the issue in this case. There is a similar issue here https://github.com/orgs/vercel/discussions/6575

[jmikedupont2]

I found that "tar" produces the problem https://vercel.community/t/calling-tar-x-causeserror-enoent-no-such-file-or-directory-lstat-next-export-detail-json/2007
by removing its usage I could work around the issue