WebPack --watch command is giving exception
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 187
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the application instructions and locate the Webpack configuration used by the --watch command. Check the configuration entries identified in the error, especially colors and output.path; done means the watch command starts without the schema or non-absolute-path exceptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100