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

WebPack --watch command is giving exception #26

Open
harisaru opened this issue Jun 21, 2017 · 4 comments
Open

WebPack --watch command is giving exception #26

harisaru opened this issue Jun 21, 2017 · 4 comments

Comments

@harisaru
Copy link

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.

  • configuration has an unknown property 'colors'. These properties are valid:
    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: ...
    }
    })
    ]
  • configuration.output.path: The provided value "./" is not an absolute path!

Regards,
HariKrishna

@eyotang
Copy link

eyotang commented Aug 4, 2017

I have the same exception, then I comment the colors. It passed.
But a few minutes later, It throw another exception.

webpack --watch --config webpack.config.js

Webpack is watching the files…

/usr/local/lib/node_modules/webpack/lib/Chunk.js:49
throw new Error("Chunk.entry was removed. Use hasRuntime()");
^

Error: Chunk.entry was removed. Use hasRuntime()
at Chunk.get entry [as entry] (/usr/local/lib/node_modules/webpack/lib/Chunk.js:49:9)
at /root/sourcecode/treed/node_modules/extract-text-webpack-plugin/index.js:116:13
at Array.filter (native)
at ExtractTextPlugin. (/root/sourcecode/treed/node_modules/extract-text-webpack-plugin/index.js:115:37)
at Compilation.applyPlugins0 (/usr/local/lib/node_modules/webpack/node_modules/tapable/lib/Tapable.js:68:14)
at Compilation.seal (/usr/local/lib/node_modules/webpack/lib/Compilation.js:567:8)
at applyPluginsParallel.err (/usr/local/lib/node_modules/webpack/lib/Compiler.js:514:17)
at /usr/local/lib/node_modules/webpack/node_modules/tapable/lib/Tapable.js:289:11
at _addModuleChain (/usr/local/lib/node_modules/webpack/lib/Compilation.js:481:11)
at processModuleDependencies.err (/usr/local/lib/node_modules/webpack/lib/Compilation.js:452:13)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)

@Samdyddd
Copy link

how to solve this problem?

@hamidhaghdoost
Copy link

and I have same error...

@spacegangster
Copy link

Solved this in my fork https://github.com/spacegangster/treed

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

5 participants