-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
After gatsby build, we still see only chunked js in the html and not the full content #28431
Comments
Hi! Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a minimal reproduction. This is a simplified example of the issue that makes it clear and obvious what the issue is and how we can begin to debug it. If you're up for it, we'd very much appreciate if you could provide a minimal reproduction and we'll be able to take another look. Thanks for using Gatsby! 💜 |
Sure. Will try to do this. |
I've faced this issue as well in the past. I've found this happens when using Opted to just remove Bear in mind, you will need to purge the service worker using |
Nicholas, thanks for the suggestions. We tried, but it still did not work. |
As an update, when we tried with minimal reproduction with all plug ins, it seems to be generating html well. Is there anything else we can try ? |
gatsby-plugin-offline isn’t the cause of the problem, the HTML is generated as usual: It could be many things, so adding code step by step to your reproduction should uncover it. For example if you have logic that checks for window and as a result it'll only render on the client. |
@LekoArt Please find the attached repo, where we have added our plug ins and configs. we are able to simulate the problem. https://github.com/KalaiarasanAyyanar/website-reproducible You can clone the repo. do "npm install", then "gatsby build" and then "gatsby serve". Please do let me know if any issues in replicating the issues. |
@LekoArts Please find the attached repo, where we have added our plug ins and configs. we are able to simulate the problem. https://github.com/KalaiarasanAyyanar/website-reproducible You can clone the repo. do "npm install", then "gatsby build" and then "gatsby serve". Please do let me know if any issues in replicating the issues. |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
@LekoArts an update on this. We managed to resolve the issue. Below is the solution repo. https://github.com/mageshpurpleslate/gatsby_ssr_with_mui Thanks for your help |
We have built a website using gatsby and strapi. It has a monthly hit of close to 2 million page views and a monthly average of 700k users. We have been recently hit with performance issues and when we looked in detail the server side rendering not happening.
During build, we do see the path getting split and index.html being generated for each path. In that html, we see the js and css and being included as well. However, actual content is being rendered only during run time.
Below is the gatsby-config.js
Below is the gatsby-ssr.js
below is the index.html
The text was updated successfully, but these errors were encountered: