Not working on Kotlin 1.4.0
See original GitHub issueI get no compile-time errors, but a runtime one in the browser console:
TypeError: e.child_2usv9w$ is not a function
cr Base.kt:50
vc Icon.kt:40
gt kotlin-wrappers-kotlin-react-jsLegacy.js:250
sr Base.kt:22
mg.mExpansionPanel_2s8yu5$/< ExpansionPanel.kt:35
cr Base.kt:49
mExpansionPanel_2s8yu5$ ExpansionPanel.kt:30
gt Player.kt:124
sr Base.kt:22
fg.mPaper_1l6flt$/< Paper.kt:41
cr Base.kt:49
mPaper_1l6flt$ Paper.kt:35
render_ss14n$ Player.kt:70
render kotlin-wrappers-kotlin-react-jsLegacy.js:220
j kotlin-wrappers-kotlin-react-jsLegacy.js:140
render kotlin-wrappers-kotlin-react-jsLegacy.js:225
React 12
render_2955dm$ kotlin-wrappers-kotlin-react-dom-jsLegacy.js:145
Lt main.kt:8
<anonymous> web.js:53
<anonymous> web.js:53
Webpack 7
react-dom.production.min.js:209:194
Uncaught TypeError: e.child_2usv9w$ is not a function
cr Base.kt:50
vc Icon.kt:40
gt kotlin-wrappers-kotlin-react-jsLegacy.js:250
sr Base.kt:22
mg.mExpansionPanel_2s8yu5$/< ExpansionPanel.kt:35
cr Base.kt:49
mExpansionPanel_2s8yu5$ ExpansionPanel.kt:30
gt Player.kt:124
sr Base.kt:22
fg.mPaper_1l6flt$/< Paper.kt:41
cr Base.kt:49
mPaper_1l6flt$ Paper.kt:35
render_ss14n$ Player.kt:70
render kotlin-wrappers-kotlin-react-jsLegacy.js:220
j kotlin-wrappers-kotlin-react-jsLegacy.js:140
render kotlin-wrappers-kotlin-react-jsLegacy.js:225
React 12
render_2955dm$ kotlin-wrappers-kotlin-react-dom-jsLegacy.js:145
Lt main.kt:8
<anonymous> web.js:53
<anonymous> web.js:53
Webpack 7
Base.kt:50:27
See my working branch: https://github.com/krzema12/fsynth/commits/1.4.0 (just bumping Kotlin to 1.4.0 and React wrappers to pre.112 is truly meaningful there and enough to reproduce).
I compared if Kotlin JS and Kotlin-React work fine if there’s no Muirwik (using my custom Material UI wrappers), and they do. See https://github.com/krzema12/fsynth/commits/1.4.0-without-muirwik
I tried to track down what’s the problem, but I failed. Source maps don’t load in my browser which is also weird. I only managed to find out that not using Muirwik makes the app work fine on 1.4.0.
Could you check it out?
Thanks, Piotr
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Getting weird bugs when trying to update to Kotlin 1.4.0. How ...
Configure project :buildSrc WARNING: Unsupported Kotlin plugin version. The `embedded-kotlin` and `kotlin-dsl` plugins rely on features of ...
Read more >What's new in Kotlin 1.4
What's new in Kotlin 1.4. Release date: 17 August 2020. In Kotlin 1.4.0, we ship a number of improvements in all of its...
Read more >Support Kotlin 1.4 with ktlint 0.38.0 · Issue #383 - GitHub
The plugin doesn't work with Kotlin 1.4.0 for me – I've tried versions 9.2.1 and 9.3.0. I've set ktlint version to 0.38.1:.
Read more >Kotlin version conflict when using Kotlin Gradle plugins in pre ...
Relates to 5 Next step 1 Subtask of 1. Relates to 5 issues (0 unresolved) ... But now I want to apply the...
Read more >Changelog and Migration Guide - Detekt
This version of Detekt is built with Gradle v7.5.1 , AGP 7.3.1 , Kotlin 1.7.21 and ... Don't show the number of issues...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You could have a look at the separate starter project as an example and see if that works for you.
For 0.6.0 I use pre.112-kotlin-1.4.0 versions which might be important.
And no, you shouldn’t need material-UI as a direct dependency now-a-days.
Thanks, confirmed it works fine so far! (https://github.com/krzema12/fsynth/commit/536e5a443973c1d0f7afae804968709566325a49) From my point of view, this issue can be resolved.
Note: keep it mind that Muirwik v0.6 is not compatible with Kotlin earlier than 1.4.0, so you’re forcing all clients wanting to use v0.6+ it to migrate to 1.4.0. It’s probably fine for a moving-fast kind of project.