Nicole Galbraith

Note: The release with webpack 4 will be react-scripts 2 [sauce](https://github.com/facebook/create-react-app/issues/3815)

https://reactjs.org/blog/2018/10/01/create-react-app-v2.html It has arrived! :champagne: Thanks for finding the link @karikushi

Note: Standalone modules that are not a react app will need to be upgraded to a corresponding webpack config. This means moving from webpack 3-4 and from babel 6-7. Goodness...

I've started on this, but as it's the weekend now I'm just going to leave a log of what's been happening on the branch over at issue-708-upgrade-react-scripts. > Right now...

Error about not using mode to run webpack, defaulting to production - updated `package.json`s to use a `--mode` flag for all build/dev scripts Crypto of undefined, where are you coming...

@karikushi noticed this again, after pushing the fix for #726 which only removes the service worker in production... There have been many changes since this bug was opened. The build...

We are using [this serve](https://www.npmjs.com/package/serve) v 7.0.0, docs are not versioned. Docs are checked in source [here](https://github.com/zeit/serve/tree/a8ef723004fb7344af82471f579882fff5d3bda9) Links are kind of broken since they just link to working master branch...

Looked into it a little bit: Serve is not the issue it does not set NODE_ENV. react-scripts sets the NODE_ENV to production for built applications, and our built apps are...

Hi @jared-dykstra , Thanks for your contribution. We have been documenting functions as we modify/touch them but will shift this one up the priority queue. To answer your question for...

https://itnext.io/how-to-package-your-react-component-for-distribution-via-npm-d32d4bf71b4f