Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Kotlin 1.8.21 #379

Closed
dariuszkuc opened this issue May 24, 2023 · 2 comments 路 Fixed by #388
Closed

Support Kotlin 1.8.21 #379

dariuszkuc opened this issue May 24, 2023 · 2 comments 路 Fixed by #388

Comments

@dariuszkuc
Copy link
Contributor

Hello 馃憢

Awesome work on the library! By any chance there will be a new version released soon that supports Kotlin v1.8.21?

I tried updating it (link) but sadly there is some change in behavior in v1.8.20 that breaks JS compiler. Nothing jumps out from the release notes - they did add alpha support for new JS IR compiler but that "shouldn't" affect the legacy compiler.

After updating to v1.8.20+ JS compilation fails asking to set some IR properties (-ir-output-dir and -ir-output-name). I tried updating the default KotlinJsCompilation#jsArgs() args to include those but that didn't work either, i.e. I added the following

args.moduleName = "KCT"
args.outputDir = outputDir.toString()

With the above JS compilation runs but does not produce any outputs.... Any help would be appreciated!

@tschuchortdev
Copy link
Owner

I'm glad to hear that you like it. In cases like this, I find it often helps to grep the Kotlin repository to look for any changes that suggest how to use the new options.

With the above JS compilation runs but does not produce any outputs

With that change are your tests failing or are they green? In the linked PR, all tests are green and they seem to do some rudimentary tests for the contents of the generated JS file.

@dariuszkuc
Copy link
Contributor Author

dariuszkuc commented May 26, 2023

With that change are your tests failing or are they green? In the linked PR, all tests are green and they seem to do some rudimentary tests for the contents of the generated JS file.

Tests were failing on my machine - there were no generated JS files so assertions were failing. Thanks for taking a look!


edit: Doh! I did a toString on a file vs using absolute path

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants