Hi, I am trying out 1.3.70 but don't see the brows...

# multiplatform

[Janelle Fullen]

Hi, I am trying out 1.3.70 but don't see the browserProductionWebpack task in my IntelliJ Gradle menu. I have updated my IntelliJ Kotlin plugin, and bumped the version of Kotlin I'm using for my gradle plugin to 1.3.70. I am also using the multiplatform plugin. Not sure what I'm doing wrong.

[jw]

do you have kotlin { js { browser() } }?

[Janelle Fullen]

it works when I add the browser target

[Janelle Fullen]

I didn't have it previously

[Janelle Fullen]

However, we were using nodejs { }

[Janelle Fullen]

Is there a difference using browser as the target?

[jw]

Yes it only works for browser targets

[Brandon Saunders]

what is the distinction between nodejs and js?

[Brandon Saunders]

with respect to why the dce only works on js rather than nodejs

[jw]

size is not an issue on servers, presumably

[jw]

you should be able to force the webpack mode yourself, if you need it https://kotlinlang.slack.com/archives/C0B8L3U69/p1583223716113000?thread_ts=1583209401.112100&cid=C0B8L3U69

[Brandon Saunders]

got it, then if that's the case is there a way to get the jsBrowserProductionWebpack task to work with an output librarytarget of commonjs?

[Brandon Saunders]

currently for our project it doesn't seem to be using the same webpack.config we had been using prior to 1.3.70

[Brandon Saunders]

ahh i think i may have found the issue. We had previously been calling webpack on our own. The task seems to assume the existence of a webpack.config.d folder. I'll try that

[Brandon Saunders]

hmm... no that didn't see to fix it. I'm still not getting a commonjs library despite the webpack.config.js file in my webpack.config.d folder saying to make it so

[Brandon Saunders]

we're pretty sure the file is being used, because syntax errors in it cause the jsBrowserProductionWebpack task to fail