-
Notifications
You must be signed in to change notification settings - Fork 192
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
WebPack --watch command is giving exception #26
Comments
I have the same exception, then I comment the colors. It passed. webpack --watch --config webpack.config.jsWebpack is watching the files… /usr/local/lib/node_modules/webpack/lib/Chunk.js:49 Error: Chunk.entry was removed. Use hasRuntime() |
how to solve this problem? |
and I have same error... |
Solved this in my fork https://github.com/spacegangster/treed |
Hi,
When i am trying to run the application as per the instructions, i am getting following error Kindly let me know where i am doing wrong:
Invalid configuration object. Webpack has been initialised using a configuration
object that does not match the API schema.
object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?,
entry, externals?, loader?, module?, name?, node?, output?, performance?, plugin
s?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, res
olveLoader?, stats?, target?, watch?, watchOptions? }
For typos: please correct them.
For loader options: webpack 2 no longer allows custom properties in configura
tion.
Loaders should be updated to allow passing options via loader options in mo
dule.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: {
colors: ...
}
})
]
Regards,
HariKrishna
The text was updated successfully, but these errors were encountered: