Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create-react-app installs with webpack 1.14 #1565

Closed
goztrk opened this issue Feb 15, 2017 · 1 comment
Closed

create-react-app installs with webpack 1.14 #1565

goztrk opened this issue Feb 15, 2017 · 1 comment

Comments

@goztrk
Copy link

goztrk commented Feb 15, 2017

Can you reproduce the problem with latest npm?

Yes

Description

create-react-app my-app installs the new app correctly. But it has Webpack 1.14 on dev-dependencies.
cleared npm-cache on %appdata%/npm-cache
checked package.tgz on npm-cache folder. This is what package.json has:

{
  "name": "react-scripts",
  "version": "0.9.0",
  "description": "Configuration and scripts for Create React App.",
  "repository": "facebookincubator/create-react-app",
  "license": "BSD-3-Clause",
  "engines": {
    "node": ">=4"
  },
  "bugs": {
    "url": "https://github.com/facebookincubator/create-react-app/issues"
  },
  "files": [
    ".babelrc",
    ".eslintrc",
    "bin",
    "config",
    "scripts",
    "template",
    "utils"
  ],
  "bin": {
    "react-scripts": "./bin/react-scripts.js"
  },
  "dependencies": {
    "autoprefixer": "6.7.2",
    "babel-core": "6.22.1",
    "babel-eslint": "7.1.1",
    "babel-jest": "18.0.0",
    "babel-loader": "6.2.10",
    "babel-preset-react-app": "^2.1.0",
    "babel-runtime": "^6.20.0",
    "case-sensitive-paths-webpack-plugin": "1.1.4",
    "chalk": "1.1.3",
    "connect-history-api-fallback": "1.3.0",
    "cross-spawn": "4.0.2",
    "css-loader": "0.26.1",
    "detect-port": "1.0.1",
    "dotenv": "2.0.0",
    "eslint": "3.8.1",
    "eslint-config-react-app": "^0.5.1",
    "eslint-loader": "1.6.0",
    "eslint-plugin-flowtype": "2.21.0",
    "eslint-plugin-import": "2.0.1",
    "eslint-plugin-jsx-a11y": "2.2.3",
    "eslint-plugin-react": "6.4.1",
    "extract-text-webpack-plugin": "1.0.1",
    "file-loader": "0.10.0",
    "filesize": "3.3.0",
    "fs-extra": "0.30.0",
    "gzip-size": "3.0.0",
    "html-webpack-plugin": "2.24.0",
    "http-proxy-middleware": "0.17.3",
    "jest": "18.1.0",
    "json-loader": "0.5.4",
    "object-assign": "4.1.1",
    "postcss-loader": "1.2.2",
    "promise": "7.1.1",
    "react-dev-utils": "^0.5.0",
    "recursive-readdir": "2.1.0",
    "strip-ansi": "3.0.1",
    "style-loader": "0.13.1",
    "url-loader": "0.5.7",
    "webpack": "1.14.0",
    "webpack-dev-server": "1.16.2",
    "webpack-manifest-plugin": "1.1.0",
    "whatwg-fetch": "2.0.2"
  },
  "devDependencies": {
    "react": "^15.3.0",
    "react-dom": "^15.3.0"
  },
  "optionalDependencies": {
    "fsevents": "1.0.17"
  }
}

Expected behavior

Webpack ^2 should be installed

Actual behavior

Webpack 1.14 being installed

Environment

  1. npm ls react-scripts (if you haven’t ejected): react-scripts@0.9.0
  2. node -v: 6.9.2
  3. npm -v: 4.2.0

Then, specify:

  1. Operating system: Windows 10
  2. Browser and version: Chrome 56

Reproducible Demo

None

@gaearon
Copy link
Contributor

gaearon commented Feb 15, 2017

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. The upside is it gives us some more time to test it and fix any issues. 😉

Hope this helps!

@gaearon gaearon closed this as completed Feb 15, 2017
@lock lock bot locked and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants