Ok, so what happens is that I import the dat.GUI w...

# javascript

[laht]

Ok, so what happens is that I import the dat.GUI wrapper in one example -> I need to import dat.GUI.js for all my examples in the project even if I dont use the library. Becouse dat.GUI gets referenced in the single output file examples.js

[bashor]

what do you meen by “I need”?

[laht]

Without it, it crashes

[laht]

wont run

[laht]

If I were able to generate one output file for each example, I would not have a problem

[laht]

using modules perhaps?

[bashor]

could you please send me links to the example where it’s used

[bashor]

where it’s not used

[bashor]

do you write something like “require” explicitly?

[laht]

kotlin generated code or kotlin source?

[laht]

no

[bashor]

source

[bashor]

so that do you mean by “import dat.GUI.js”?

[laht]

import info.laht.threekt.external.libs.datgui.dat

[laht]

is causing the issue, becouse it gets referenced in the generated .js

[bashor]

w/o any usage?

[bashor]

just import?

[laht]

the class gets instantiated

[laht]

https://github.com/markaren/three.kt/tree/dev/example/src/main/kotlin

[laht]

here I use dat.GUI in one of the examples

[laht]

these three examples gets generated as a single output file "examples.js"

[bashor]

ok, as I see it’s single gradle project

[laht]

yes

[bashor]

so you will get one .js file

[laht]

indeed

[bashor]

where at the start we asserts that all required libraries available at runtime

[laht]

yes, which throws en error if I dont include it

[bashor]

it’s the reason why dat.GUI required for examples

[laht]

so, my question is how can I make it more relaxed / generate multiple files

[bashor]

maybe you wanted to load dependencies lazily?

[laht]

yes

[bashor]

https://youtrack.jetbrains.com/issue/KT-20679

[bashor]

feel free to vote or star to get notification about updates

[bashor]

unfortunately, right now it’s imposible

[laht]

ok, thanks for the assistance anyhow 🙂

[bashor]

welcome

[laht]

was nice with the link

[pdvrieze]

It would probably involve some manual hacking around. In particular you may want to use require as a (perhaps synchronous) lookup function. Basically having the wrapper available doesn't actually imply in all cases that the underlying library is available. You just can't rely on @JsModule for automatic dependency management.