You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
next build won't export .amp pages when the hybrid pages use getStaticProps
To Reproduce
1 - Create an hybrid AMP page
2 - Run next build
3 - Both page.html and page.amp.html are export in the out folder
4 - Add getStaticProps onto the page
5 - Run next build
6 - Only the page.html is being exported
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 30, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
Describe the bug
next build
won't export.amp
pages when the hybrid pages usegetStaticProps
To Reproduce
1 - Create an hybrid AMP page
2 - Run
next build
3 - Both
page.html
andpage.amp.html
are export in theout
folder4 - Add
getStaticProps
onto the page5 - Run
next build
6 - Only the
page.html
is being exportedCode Sample
Expected behavior
No matter if
getStaticProps
is being used, an hybrid AMP page should end up exporting bothpage.html
andpage.amp.html
.System information
9.3.2-canary.4
The text was updated successfully, but these errors were encountered: