-
Notifications
You must be signed in to change notification settings - Fork 27.4k
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
Issue with Fetch as Google? Robots? #3126
Comments
FYI, I was able to confirm it's still an issue in |
Hmm, this could be related styled-components/styled-components#1033 |
Ignore! There was an issue with how we were loading postcss in our specific app. Apologies for making it an issue. Carry on with the good work! |
❤️ No worries! |
hmm, this actually might still be an issue. When I use a custom |
I think the problem relies on using strip-ansi package in next js. since strip-ansi uses arrow functions and google uses chrome 41 for crawling websites which doesn't support arrow functions and results in errors. |
Ah thanks for connecting me to that issue @iamsoorena I'll close this in favor of #2747 |
A few discussions: vercel#2747 vercel#3126
What I had to do to finally make it all work: |
Expected Behavior
Current Behavior
I'm struggling to figure out how to duplicate this locally, but I was using
3.0.0-beta9
and upgraded to4.1
(including upgrading to react 16) and now I get this when I use fetch as google or google's page speed test. I narrowed it down to happening sometime between the 3.0 beta and upgrading to next3.2.1
I'm worried that it's causing SEO issues. Has anyone else run into this issue?
Steps to Reproduce (for bugs)
3.2.1
Context
Your Environment
The text was updated successfully, but these errors were encountered: