After upgrading to Kotlin 2.0 and Compose to 1.6.10 I'm finding that jsRun produces an error `[webpa...

# compose-web

[Greg Steckman]

After upgrading to Kotlin 2.0 and Compose to 1.6.10 I'm finding that jsRun produces an error [webpack-cli] Invalid options object. Dev Server has been initialized using an options object that does not match the API schema. Is anyone else seeing this? More details in thread.

[Greg Steckman]

The full error is:

> [webpack-cli] Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.
   - options has an unknown property '_assetEmittingPreviousFiles'. These properties are valid:
     object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, ipc?, liveReload?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, setupM
iddlewares?, static?, watchFiles?, webSocketServer? }

[Oliver.O]

Maybe this one?

https://stackoverflow.com/questions/78072906/invalid-options-object-dev-server-has-been-initialized-using-an-options-object

[Greg Steckman]

Thanks for the suggestion, but since I am using Kotlin multiplatform all of this should be handled by the gradle plugin - from that it looks like a potential version mismatch, but I'm not even sure it is possible for me to control the webpack version (nor should I need to).

[Greg Steckman]

I found the issue, which was due to a different subproject from the one in which I was using the jsRun task. The other subproject had pinned the webpackCLI version in the build.gradle.kts to 4.10.0 to get around a problem I ran into long ago, and I used the fix described here. Removing that, now lets the other subproject execute jsRun successfully.