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

[docs] Workaround next.js AMP support limitation #18020

Merged
merged 2 commits into from Oct 24, 2019
Merged

[docs] Workaround next.js AMP support limitation #18020

merged 2 commits into from Oct 24, 2019

Conversation

ghost
Copy link

@ghost ghost commented Oct 24, 2019

Closes #17784

@ghost ghost changed the title Apply changes as suggested in issue #17784 [docs] Apply changes as suggested in issue #17784 Oct 24, 2019
@mui-pr-bot
Copy link

No bundle size changes comparing fdafbc5...f649347

Generated by 🚫 dangerJS against f649347

@oliviertassinari oliviertassinari changed the title [docs] Apply changes as suggested in issue #17784 [docs] Workaround next.js AMP support limitation Oct 24, 2019
@oliviertassinari oliviertassinari added bug 🐛 Something doesn't work docs Improvements or additions to the documentation labels Oct 24, 2019
Copy link
Member

@oliviertassinari oliviertassinari left a comment

Choose a reason for hiding this comment

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

Looks good. I'm not aware of any limitation of these changes, it should be safe :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something doesn't work docs Improvements or additions to the documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Example "nextjs-with-typescript" not working with NextJS AMP support
3 participants