What are the downsides if you dont call `binaries....

# javascript

[hfhbd]

What are the downsides if you dont call binaries.executable() or binaries.library() in your gradle config?

[andylamax]

you won't get a javascript executable to run or publish

[hfhbd]

Yes, and in internal intermediate modules?

[Big Chungus]

If you're building kotlin.js lib, you should never need either as your output stops at klib. Those two are only needed if you want actual js output.

[hfhbd]

Thanks!

[shaktiman_droid]

@Big Chungus but without binaries.library() , there won't be packJsNpmPublication task right? isn't kotlin.js lib means an npm module as well? Or just the module to be used from kotlin.js web project?

[Big Chungus]

No, kotlin.js lib is just a .klib file that can be used in other kotlin projects (like .jar for jvm projects). If you want your lib accessible from js projects, then you need binaries.library() and packJsNpmPublication

[shaktiman_droid]

Yeah makes sense. Thanks for confirming @Big Chungus