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

Refreshing app displays raw html without style for a while #6549

Closed
kboul opened this issue Mar 1, 2019 · 2 comments
Closed

Refreshing app displays raw html without style for a while #6549

kboul opened this issue Mar 1, 2019 · 2 comments

Comments

@kboul
Copy link

kboul commented Mar 1, 2019

Not sure whether this is a bug, but anyways I would like to listen to your opinion.

In the last couple of days after upgrading handlebars due to a security vulnerability (not sure if this is coincidental or not) if I hit the refresh button either on Chrome Version 70.0.3538.77 (Official Build) (64-bit)
or in Mozilla Firefox 65.0.1 using Ubuntu 18.04.2 LTS I am able to see for a second, for a blink of an eye the raw html of the page I am landing without the styles implemented in development mode. I tested in production after building the app and everything is ok there.

I am using sass ("node-sass": "^4.11.0") in my application if that makes any difference.

I tested with a newly created create-react-app and the same applies there. Specifically, if you hit refresh button on the browser you are able to see "Edit src/App.js and save to reload." and "learn React" in raw html on the top left corner on the screen for a second before style is applied instantly.

I can provide my package.json if it is necessary for my create-react-app.
Is this an expected behavior because I can assure you that before I did not notice something like this or is this something that is applied on my local machine due to a misconfiguration?

index.html is almost the same as in the boilerplate. Only have added this line of code
<link type="text/css" rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:300,400,500,700">

I also forgot to mention that I am using absolute paths in my application while having declared
NODE_PATH=src/ on .env and that recentry upgraded to node v11.10.0 with npm v. 6.8.0
I downgraded to node v 10.15.2 but that did not fix the issue.

Thank you in advance.

@petetnt
Copy link
Contributor

petetnt commented Mar 1, 2019

Hi @kboul!

Pretty sure that this is duplicate of #6399 and should be fixed in 2.1.6. when it comes out. Meanwhile you can try downgrading to [email protected]. Note that the issue should only affect development builds, not production builds.

@petetnt petetnt closed this as completed Mar 1, 2019
@kboul
Copy link
Author

kboul commented Mar 1, 2019 via email

@lock lock bot locked and limited conversation to collaborators Mar 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants