It's still installing webpack 1.4.1 for me. Is this intended behavior?

[coryhouse]

Unsure if I'm seeing a bug. I thought create react app was now using Webpack 2, but when I run create-react-app using the latest release, I still get 1.4.1 in react-scripts' package.json. Is this intended behavior?

Can you reproduce the problem with latest npm? Yes

Many errors, especially related to "missing modules", are due to npm bugs.

If you're using Windows, follow these instructions to update npm.

If you're using OS X or Linux, run this to update npm:

npm install -g npm@latest

cd your_project_directory
rm -rf node_modules
npm install

Then try to reproduce the issue again.

Can you still reproduce it?

Description

What are you reporting?

Expected behavior

Running create react app produces an application using webpack 2.

Actual behavior

I get a project that's using webpack 1.4

Environment

Run these commands in the project folder and fill in their results:

1. npm ls react-scripts (if you haven’t ejected):
2. node -v: 7.7.1
3. npm -v: 4.1.2

Then, specify:

1. Operating system: OSX
2. Browser and version: Sierra

Reproducible Demo

[Timer]

#1565, #1599

The behavior is correct. Webpack 2 support has just been merged to master a few days ago, and it will take a little while before it shows up in the stable release.

[Timer]

We're hesitant to cut a beta because of #1638 and #1305, if you would like to help triage and fix these issues, please feel welcome!