next.js VS react-snap

While it's technically possible to do things like compile React entirely out of an exported NextJS site, it's far from trivial and doesn't fit most usage very well. It's certainly a harder mental model at the very least.

Disable all your chrome extensions. As recommended here https://github.com/zeit/next.js/issues/10246

Link: https://github.com/zeit/next.js/blob/canary/examples/with-graphql-faunadb/lib/useFetch.js

import React, { Component, Fragment } from 'react';import { withRouter } from 'next/router';import 'isomorphic-unfetch';class post extends Component { static async getInitialProps({ req }) { try { const res = await fetch(`http://localhost/api/posts/${req.params.postslug}`, { method: 'GET', // *GET, POST, PUT, DELETE, etc. mode: 'cors', // no-cors, cors, *same-origin }); const json = await res.json(); return { data: json.data }; } catch (err) { console.log('err'); } } render() { const { data } = this.props; return ( ); }}export default withRouter(post); I have already checked the next.js docs and it has this implementation which uses the node http module. I implemented this code on express by copying some parts from the documentation example. However it still seems to cause a page reload when i go to the article page using a .

next.js

NextJS: 8.0.3

Read more one the github issue

import React from 'react';import PropTypes from 'prop-types';class VerticalSlider extends React.Component { constructor(props) { super(props); this.ScrollMagic = null; this.controller = null; this.scenes = []; this.container = React.createRef(); } componentDidMount() { if (this.container.current) { // Why "require" here? // https://github.com/zeit/next.js/issues/219#issuecomment-393939863 // We can't render the component server-side, but we will still render // the HTML // eslint-disable-next-line global-require this.ScrollMagic = require('scrollmagic'); this.initScroller(); } } componentWillUnmount() { this.scenes.forEach(scene => { scene.destroy(); }); this.controller.destroy(); this.scenes = []; this.controller = null; } initScroller() { try { this.controller = new this.ScrollMagic.Controller(); if (this.container.current !== null && this.container.current.children) { [...this.container.current.children].forEach(children => { const scene = new this.ScrollMagic.Scene({ triggerElement: children, duration: window.innerHeight * 1.5, triggerHook: 0, reverse: true }); scene.setPin(children); this.scenes.push(scene); }); this.controller.addScene(this.scenes); } } catch (e) { console.log(e); } } render() { return (

react-snap is a tool to help with SSR; a while ago I wrote about it:

chrome headless prerendering (ex react-snap)

My react build scripts use https://github.com/stereobooster/react-snap to create static files which I deploy. Might be good enough for you. Otherwise I'd suggest moving the app to a different subdomain as someone else mentioned and having separate marketing pages. If you have a lot of dynamic content (ie user generated) that you want SEO'd, server side rendering is the most tried and tested.

react-snap - Zero-configuration framework-agnostic static prerendering for SPAs

Right now, Perseus needs its server, the architecture doesn't permit purely static operation. That said, something like perseus export will definitely be happening before 1.0.0! In the meantime, maybe try out react-snap?