I have an application based on KVision 4.7.1. When...

# kvision

[Lars Erik Rojeras]

I have an application based on KVision 4.7.1. When I try to run it I get the following message:

[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 '_assetEmittingWrittenFiles'. 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? }

(From what I know) I have not changed any build configurations. When I check out an earlier commit, that used to work, I get the same error.
Have you got any ideas what can be wrong?

[Robert Jaros]

I've just seen this:
https://kotlinlang.slack.com/archives/C0B8L3U69/p1629069160242100

[Lars Erik Rojeras]

Thanks. I'll stay tuned...

[Robert Jaros]

I think some npm dependency was published with some kind of incompatibility but without new major release.

[Robert Jaros]

And probably all build will fail now ...

[Lars Erik Rojeras]

😕

[Robert Jaros]

yep, my builds are failing as well

[Rahim Klaber]

😞

[Robert Jaros]

I've added a workaround to all kvision examples.
https://github.com/rjaros/kvision-examples/commit/a77c4cd16b913053bf94c47c97d620d250e5539d#diff-f64e2db68672a2658d92cbbca01c4fe0f74dcb75117544c1dfab3f4c3aab69e3

[Lars Erik Rojeras]

Thank you! I can confirm that your workaround works for me.