2 ms·
It's more of a framework than a boilerplate solution, but highly recommend checking it out! To answer your questions: 1) Because the router in next.js embeds
by rase- 9y ago
It's more of a framework than a boilerplate solution, but highly recommend checking it out!
To answer your questions:
1) Because the router in next.js embeds really well into the model of pages, prefetching, etc. while still keeping the mechanisms simple, here's how to use with redux: https://github.com/zeit/next.js/tree/master/examples/with-redux https://github.com/zeit/next.js/tree/master/examples/with-re...
2) now.sh is in no way mandatory. To deploy anywhere, `next build` and `next start` will run the node.js server, so you're free to deploy it anywhere you'd like: https://github.com/zeit/next.js#production-deployment https://github.com/zeit/next.js#production-deployment