webpack2 / extra-entry-webpack-plugin peculiarity

[jtadmor]

Hi,

Love this project. Having an odd issue.

This is my package.json:

"devDependencies": {
    "carte-blanche": "^0.3.1",
    "webpack": "^2.2.1"
  },
  "dependencies": {
    "elemental": "^0.6.1",
    "react": "^15.4.2",
    "react-addons-css-transition-group": "^15.4.2",
    "react-dom": "^15.4.2"
  },

The version of carte-blanche on this github page includes this in the package.json: "extra-entry-webpack-plugin": "0.0.3",

For whatever reason, package.json when I install with yarn looks like:

"dependencies": {
    "carte-blanche-react-plugin": "^0.3.0",
    "chai": "^3.5.0",
    "exenv": "^1.2.1",
    "extra-entry-webpack-plugin": "0.0.2",
    "loader-utils": "^0.2.15",
    "lodash": "^4.13.1",
    "mocha": "^2.5.3",
    "read-multiple-files": "^1.1.1"
  }

When I install with npm install, I similarly get:

"dependencies": {
    "carte-blanche-react-plugin": "^0.3.0",
    "chai": "^3.5.0",
    "exenv": "^1.2.1",
    "extra-entry-webpack-plugin": "0.0.2",
    "loader-utils": "^0.2.15",
    "lodash": "^4.13.1",
    "mocha": "^2.5.3",
    "read-multiple-files": "^1.1.1"
  }

extra-entry-webpack-plugin v0.0.2 is therefore being used, which in turn is incompatible with webpack v2.

If it helps, I'm seeing this in the npm install generated package.json:

"_resolved": "https://registry.npmjs.org/carte-blanche/-/carte-blanche-0.3.1.tgz"

I confirmed that downloading that directly does include the 0.0.2.

Any ideas on why this might be happening, or is an easy fix to just publish the correct version to npm (it looks like nothing from this commit made it onto the package hosted on npm: fdcb99d)