You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I create a new "react-app" webpack1 is still being used, even though I noticed that an upgrade from webpack1 to webpack2 was about a week ago.
Expected behavior
Should use webpack": "2.2.1 (or whatever is specified under packages/react-scripts/package.json)
Actual behavior
When I create an app I see that webpack@1.14.0 in yarn installation logs.
When I eject the app it uses� webpack@1.14 as well.
Environment
Run these commands in the project folder and fill in their results: └── react-scripts@0.9.0 $ node -v v7.0.0 $ npm -v 4.2.0 $ yarn --version 0.17.10 // tried to do yarn cache clean as well
Then, specify:
osx 10.12.3
--/--
The text was updated successfully, but these errors were encountered:
We develop on master, just like most repositories do, including React. This means you'll see many things on master that haven't made it yet into a release. Please consult the Releases page for available features, not what's in master. Webpack 2 support is not released yet (and there some issues we still need to iron out before including it).
Description
When I create a new "react-app" webpack1 is still being used, even though I noticed that an upgrade from webpack1 to webpack2 was about a week ago.
Expected behavior
Should use
webpack": "2.2.1
(or whatever is specified under packages/react-scripts/package.json)Actual behavior
When I create an app I see that
webpack@1.14.0
in yarn installation logs.When I
eject
the app it uses� webpack@1.14 as well.Environment
Run these commands in the project folder and fill in their results:
└── react-scripts@0.9.0
$ node -v v7.0.0
$ npm -v 4.2.0
$ yarn --version 0.17.10
// tried to do yarn cache clean as wellThen, specify:
The text was updated successfully, but these errors were encountered: