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

ES2015 branch doesn't run #20

Open
awkale opened this issue May 12, 2017 · 1 comment
Open

ES2015 branch doesn't run #20

awkale opened this issue May 12, 2017 · 1 comment

Comments

@awkale
Copy link

awkale commented May 12, 2017

There is an issue with the webpack.config.js when using sass-loader. The following error occurs when trying to run locally

$ webpack-dev-server -d --progress --colors --inline --hot --https --open --content-base bin/
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration has an unknown property 'sassLoader'. These properties are valid:
   object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
   For typos: please correct them.
   For loader options: webpack 2 no longer allows custom properties in configuration.
     Loaders should be updated to allow passing options via loader options in module.rules.
     Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
     plugins: [
       new webpack.LoaderOptionsPlugin({
         // test: /\.xxx$/, // may apply this only for some modules
         options: {
           sassLoader: ...
         }
       })
     ]
error Command failed with exit code 1.
@Nibblesh
Copy link

Hope this helps, if you want to fix this locally just for yourself you can fork the project and run

npm i --save-dev [email protected]

To explain what happened, you have webpack-dev-server installed globally, which is webpack-dev-server version 2, compatible with webpack2, which has a different structure for configuration objects, and the options were made invalid due to the command searching in the node_modules folder for a webpack-dev-server launcher, which it failed to do, and then fell back to your global version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants