It seems kotlin-js pulls in the latest webpack with a new bug that is preventing
jsBrowserDevelopmentRun
from doing its thing. Is anyone else running into this? Or better still, have a workaround?
Basically, started happening after I did a gradle clean on my fritz2 project. After this it pulled in the latest npm dependencies. Was working fine before the gradle clean.
Copy code
[webpack-cli] Unable to load '@webpack-cli/serve' command
[webpack-cli] TypeError: options.forEach is not a function
[webpack-cli] TypeError: options.forEach is not a function
at WebpackCLI.makeCommand (/Volumes/SAMSUNG_2TB/git/formation/maptool/build/js/node_modules/webpack-cli/lib/webpack-cli.js:173:21)
at ServeCommand.apply (/Volumes/SAMSUNG_2TB/git/formation/maptool/build/js/node_modules/@webpack-cli/serve/lib/index.js:41:19)
at loadCommandByName (/Volumes/SAMSUNG_2TB/git/formation/maptool/build/js/node_modules/webpack-cli/lib/webpack-cli.js:907:35)
at async Command.<anonymous> (/Volumes/SAMSUNG_2TB/git/formation/maptool/build/js/node_modules/webpack-cli/lib/webpack-cli.js:1462:17)
at async Promise.all (index 0)
at async WebpackCLI.run (/Volumes/SAMSUNG_2TB/git/formation/maptool/build/js/node_modules/webpack-cli/lib/webpack-cli.js:1500:9)
at async runCLI (/Volumes/SAMSUNG_2TB/git/formation/maptool/build/js/node_modules/webpack-cli/lib/bootstrap.js:11:9)