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

(ReactJS + serverless) static served page vs virtual DOM bug #125

Closed
leongaban opened this issue May 18, 2017 · 2 comments
Closed

(ReactJS + serverless) static served page vs virtual DOM bug #125

leongaban opened this issue May 18, 2017 · 2 comments

Comments

@leongaban
Copy link

http://stackoverflow.com/questions/44052476/reactjs-serverless-static-served-page-vs-virtual-dom-bug?noredirect=1#comment75130440_44052476

Expected: We see our React app, rendered staticly with all the Markup and logic inside of the view, to be served up so Users & Web crawlers can read text and follow links.

Results: We see nothing in the page.

=====

We are rending serverside ReactJS components with serverless-webpack

Everything is working great, the component data/markup is rendered out. However the problem happens when we run serverless webpack serve

We hit the localhost link and for a split sec we see the app, then it's gone to a white page.

On deeper inspection if we do a View Source, we see ALL the markup, including CSS and JS, everything. However in the Chrome Inspector we only see the app

and nothing else. It's like once our app script line runs, we replace the static content with the Virtual DOM.

To those are who rendering static pages with React and serverless, how have you overcome this problem?

@HyperBrain
Copy link
Member

@leongaban With version 3 (available as 3.0.0-rc.2 now) we switched completely to use serverless-offline and serverless invoke local to concentrate on the packaging and not emulation. Does that solve your problem?

@HyperBrain
Copy link
Member

As there has been no recent feedback, I'll close the issue. Feel free to reopen it or create a new one for the latest plugin version if it persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants