Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

feat: rm deprecated next export #78

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

edoardolunardi
Copy link
Contributor

@edoardolunardi edoardolunardi commented Feb 8, 2024

next export has been removed and it's not a valid command anymore.
The correct way to get a static export is now by setting output: "export" in the next.config file.

I added an env variable to control this behaviour, otherwise if output is set to "export" it will always create a static export when next build runs.

Usually for us, we run the normal next app on a server, where we don't need the site to be a static export there.

https://nextjs.org/docs/pages/building-your-application/deploying/static-exports

Copy link
Contributor

@r0skar r0skar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about this one - iE. I dont think it make sense to add a new dependency (dev or not) for a feature that we rarely use. Let's just remove the export command? If a projects needs a static export - usually its a custom thing anyway and it should be setup on a project level. What do you think?

@edoardolunardi
Copy link
Contributor Author

Yeah I agree, let's just remove the command. I updated the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants