@ JSExport and webpack in dev mode are exporting my bundle in slightly different namespaces - is thi...

# javascript

[Reuben Firmin]

@ JSExport and webpack in dev mode are exporting my bundle in slightly different namespaces - is this a known issue / is there a workaround? (details in thread)

[Reuben Firmin]

the entrypoint to my bundle is :

package rcp.view

...
@OptIn(ExperimentalJsExport::class)
@JsExport
class Recipe {

[Reuben Firmin]

when I compile the bundle, I have to initialize it (from html) as:

recipe.rcp.view.Recipe();

when running via webpack, the "recipe" namespace is changed to "rcp", so this becomes:

rcp.rcp.view.Recipe();

[Reuben Firmin]

i don't even understand why there's anything prefixing the package - can i get rid of that somehow?

[turansky]

anything prefixing the package

In UMD - it's your library name

[Reuben Firmin]

@turansky where is this specified in the project?

[Reuben Firmin]

(and is it a bug that it differs based on compiled vs webpack? i can file)

[turansky]

where is this specified in the project?

AFAIK In webpack task

[Reuben Firmin]

hm, I can't seem to get rid of the namespace, but specifying:

webpackTask {
    output.libraryTarget = "umd2"
}

at least makes the namespace consistent. whatever the default is seems to differ