What's the path of the JS file in the dev server?

[edgarogh]

The documentation says

The generated file will be served from http://localhost:***/***/***.js, where placeholders correspond to configuration properties.

I'm not sure what "configuration properties" refers to. I have set a port and the server seems to respond with 404s, so that's that, but how do I know the path?

[konsoletyper]

You configure you path. In configuration you set file name and relative path to it. How are you running dev server? Can you share configuration?

[edgarogh]

Sure, currently I'm just using

teavm.js {
    mainClass = 'my.game.web.Main'
    obfuscated = false
    sourceMap = true

    devServer {
        port = 8080
    }
}

The docs say:

Available configuration properties:

• stackDeobfuscated – whether all JS stacks should be deobfuscated and proper Java stack traces generated.
• indicator – injects a small indicator in the lower-left corner of the page to display compilation progress right in the wev page.
• autoReload – indicates whether page should be reloaded as soon as compilation completes.
• processMemory – amount of memory, in megabytes, to allocate for server process.
• proxyUrl – when specified, development server will not only serve generated JavaScript, but also proxy all incoming requests to given URL.
• proxyPath – used in conjunction with proxyUrl. When specified, only requests starting with specified path, will be proxied.

I don't see anything related to the file name or path. Maybe it's not documented yet? since port isn't documented either apart from the example.

[konsoletyper]

So, you are running dev server from Gradle plugin, not as IDEA run configuration? Then you have two points which influence location in dev server:

• relativePathInOutputDir (which is js by default)
• targetFileName (which is gradle project name by default + '.js' suffix)

The same rule is applied when building JS file by generateJavaScript task. The base dir is $BUILD_DIR/generated/teavm, and then particular task adds ${relativePathInOutputDir}/${targetFileName}. BTW, when your project also has war plugin, TeaVM plugin will add TeaVM base build dir (i.e. $BUILD_DIR/generated/teavm) into war file output, so you can find JS, generated by TeaVM, under the same relative path (i.e. ${relativePathInOutputDir}/${targetFileName}). This was done intentionally, so that no matter you use TeaVM-generated files when deployed to server or from development server, you get the same path.

So in you case full address should be http://localhost:8080/js/$MODULE_NAME.js.

[edgarogh]

Thank you! My web entry point for my project was a Gradle subproject called :web and the URL was indeed http://localhost:8080/js/web.js. I remembered trying that, but by the look of things, my memory is failing me.

Thanks for TeaVM btw!