customize-cra VS next.js

Install react-app-rewired and customize-cra:

If Create React App supported Yarn workspaces out-of-the-box, what we've done so far would have been enough to run the app... unfortunately, it doesn't. Luckily, we can use CRACO (or other tools such as customize-cra or react-app-rewired) to customize the Webpack configuration used by Create React App to resolve packages imported from other workspaces.

Now, for customize-cra to work we need to modify the config-overrides.js file once again. The override method from customize-cra receives a list of functions, so we need to change the signature like this:

Eventually, you might need to customize your project beyond what Create React App allows you to do. Most of these customizations will probably be just slight changes to the Webpack and Babel configuration of Create React App where ejecting would be overkill — which is why you might wanna use something like react-app-rewired, customize-cra, or craco to apply these changes without ejecting.

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 (