-
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
fix for "external" PageRenderer not working in production #5986
Conversation
Deploy preview for gatsbygram ready! Built with commit 13be14f |
Deploy preview for using-drupal ready! Built with commit 13be14f |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
…epending on NODE_ENV
78a302f
to
f75fe16
Compare
c342341
to
13be14f
Compare
This can be reviewed now. Here's example of this working in production - https://deploy-preview-5986--gatsbyjs.netlify.com/showcase (click on any site - dimmed showcase listing should stay in background) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is much nicer 👍
I guess all the process.env.NODE_ENV
checks can be removed from JSONStore now? That can be a separate PR though.
Yeah, right now we don't use JSONStore in production code and I think it's desireable. We probably could remove those checks in component itself so code is more readable and maybe add check outside of component to exit build if we are using JSONStore in production |
this also allow to not bundle "./pages.json" in entry point production bundle and to not bundle JSONStore in production
closes #5920