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

Documentation: when to use react-snap and when choose something else #118

Open
stereobooster opened this issue Jan 14, 2018 · 5 comments
Open

Comments

@stereobooster
Copy link
Owner Author

stereobooster commented Jan 23, 2018

Create https://hnpwa.com/ demo with react-snap to show what is it capable of.

UPD: tastejs/hacker-news-pwas#137

@stereobooster
Copy link
Owner Author

stereobooster commented Feb 23, 2018

Just converted a very small project from gatsby back to my normal react boilerplate setup and used react-snap to generate static pages.

A few weeks ago I was looking for a headless chrome static site generator. react-snap is exactly that.https://t.co/HCWtNRoXnU

— Jake Deichert (@jakedeichert) January 1, 2018

Last week I learned that Gatsby breaks down when you have a large site. I ended up using create-react-app and react-snap.

— Aaron Shafovaloff (@aaronshaf) October 30, 2017

I looked into it for my own stuff. Ended up going with create-react-app plus react-snap. Runtime code hasn’t been the issue for us for a while.

— Josh Duck (@joshduck) July 19, 2018

@jacobdeichert
Copy link

This project is so valuable and does its job very well. It's amazing that I can use any boilerplate app setup and not have to worry about generating static pages nor being tied to some static framework!

Just saying thanks! If you hadn't of made this, I would have been tempted to very soon... 😄

@stereobooster
Copy link
Owner Author

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

No branches or pull requests

2 participants