-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
npm build not genrate index.html file instide .next directory #38261
Comments
Can you please post a link to the repo to reproduce your issue? |
@amitpanchal4 It is not supposed to in the default configuration, this way you can run the app after the build by the command
If you’d like to do a static HTML export of your Next Js app, you need to update your build script in
you can read more in Next Js docs Static HTML Export The easiest way to deploy your Next Js app is to use the Vercel Platform You can read more in Next Js deployment docs |
We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate. Why was this issue marked with the
|
This issue has been automatically closed because it received no activity for a month and had no reproduction to investigate. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you. |
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. |
Verify canary release
Provide environment information
What browser are you using? (if relevant)
Chrome
How are you deploying your application? (if relevant)
No response
Describe the Bug
npm run build command is not genrating html files insidel .next directory
Expected Behavior
We need html files for deployment in specific hosting
Link to reproduction
ll
To Reproduce
hit npm run build cmd inside project directory terminal
The text was updated successfully, but these errors were encountered: