remove babel-runtime and extract-text-webpack-plugin from dependencies to devDependencies about butter-toast HOT 4 CLOSED

Good catch. Must have missed it.
babel-runtime needs to be a dependency, but extract-text-webpack-plugin is definitely a devDependency.
Will push a fix soon.
Thanks! 👍

from butter-toast.

Published 2.1.2. Should be fixed now.

from butter-toast.

any reason why you need babel-runtime to be a dependency?

I also noticed you locked down react to a specific version as dev dependency:

"react": "16.2.0",
"react-dom": "16.2.0",

you should move it to peerDependencies without a locked version like so:

"peerDependencies": {
    "react": "^16.2.0",
    "react-dom": "^16.2.0"
  },

from butter-toast.

any reason why you need babel-runtime to be a dependency?

Yes. I use babel transform-runtime as an alternative to babel-polyfill - which pollutes the global scope. Babel runtime specifically prevents duplication even in shared space.
See here:

This is where the transform-runtime plugin comes in: all of the helpers will reference the module babel-runtime to avoid duplication across your compiled output. The runtime will be compiled into your build.

I also noticed you locked down react to a specific version as dev dependency:

Setting it as devDependency means that npm install won't install react in development, which is unwanted.
Currently this package supports React15. I might add "react": "15.0.0" as a peerDependency.

from butter-toast.