Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

FR: Add a config option to disable writing .next/export-detail.json when running next export #43344

Closed
gregmagolan opened this issue Nov 24, 2022 · 1 comment
Closed

FR: Add a config option to disable writing .next/export-detail.json when running next export #43344

gregmagolan opened this issue Nov 24, 2022 · 1 comment

Comments

@gregmagolan
Copy link

gregmagolan commented Nov 24, 2022 •
edited
Loading

Describe the feature you'd like to request

A config option to disable writing .next/export-detail.json when running next export.

When building Next.js under Bazel, the .next folder is a write-protected input directory to the next export target so Bazel prevents Next.js from writing the .next/export-detail.json file there which fails the build.

This is relevant to non-Bazel use cases as well in workflows where the .next folder is read-only: #10137

Describe the solution you'd like

A config option to disable writing .next/export-detail.json when running next export.

Describe alternatives you've considered

No alternatives available.
@gregmagolan gregmagolan changed the title Add a config option to disable writing .next/export-detail.json when running next export FR: Add a config option to disable writing .next/export-detail.json when running next export Nov 24, 2022
@gregmagolan
Copy link
Author

gregmagolan commented Nov 24, 2022 •
edited
Loading

cc @tannerwelsh @alexeagle

@gregmagolan gregmagolan mentioned this issue Nov 24, 2022
Merged
@vercel vercel locked and limited conversation to collaborators Nov 25, 2022
@balazsorban44 balazsorban44 converted this issue into discussion #43363 Nov 25, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gregmagolan