I've suddenly started to get ```> [webpack-cli] Invalid configuration object. Object has been ini...

# javascript

[altavir]

I've suddenly started to get

> [webpack-cli] Invalid configuration object. Object has been initialized using a configuration object that does not match the API schema.
   - configuration has an unknown property '_assetEmittingPreviousFiles'. These properties are valid:
     object { bonjour?, client?, compress?, dev?, firewall?, headers?, historyApiFallback?, host?, hot?, http2?, https?, liveReload?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, public?, setupExitSignals?, static?, transportMode?, watchFiles? }

error in webpack run tasks. I am not sure what changed. Does anybody else have the promblem?

[andylamax]

https://kotlinlang.slack.com/archives/C0B8L3U69/p1629069160242100?thread_ts=1629069160.242100&cid=C0B8L3U69

[Robert Jaros]

Everyone ;(

[Robert Jaros]

https://youtrack.jetbrains.com/issue/KT-48273

[altavir]

Thanks @Robert Jaros. I tried to search the youtrack. Probably it does not include code samples.

[altavir]

It is strange that it was working yesterday

[Marius Ailinca]

yes, switch to webpack v4 and it will work. In gradle.properties append: kotlin.js.webpack.major.version=4

[altavir]

I am not sure that all my projects will be compatible with webpack 4, I used @Ilya Goncharov [JB] suggestion and switched the version of dev-server. Seems to be working propely at least with one demo

[Marius Ailinca]

oh, didn't know about switching the dev-server. Will have a look. Sorry if I mislead you in any way! 🙂

[altavir]

It is there in the issue.

[Marius Ailinca]

Got it, thanks!