is anybody else having problems updating to 1.2 fo...
# javascriptn
Nicholas Bilyk
07/08/2017, 12:33 AMis anybody else having problems updating to 1.2 for JS? I'm hitting a ton of issues, it's like modules aren't working correctly anymore...
k
konsoletyper
07/08/2017, 6:55 AMnbilyk: What kind of issues do you have?
n
Nicholas Bilyk
07/08/2017, 4:46 PMI have a project that is JS, JVM, and common modules. The common modules in the IDE are JVM, but compiled both to JS and JVM.
The JS side uses AMD modules and require.js. (May be relevant for #1)
The problems:
1) I have package level variables that are being set, but when they're read, they're still null.
2) stdlib things like HashMap and Exception aren't working in the IDE (compiles fine) when a JS module references an API from the JVM module that uses one. This is an old problem but it went away at some point and now is back.
k
konsoletyper
07/09/2017, 6:33 AMCan you share the code that reproduces the problem?
konsoletyper
07/09/2017, 6:36 AMAs for package level variables. Did you try to debug your app? You shoud notice that, unlike JVM, JS backend does not produce lazy initializers for files. This means you may have problems when you are initializing top-level propertiles from one file with values of top-level properties from another file.
konsoletyper
07/09/2017, 6:36 AMAs for (2), I can't tell you anything. You better ask on #multiplatform channel
n
Nicholas Bilyk
07/10/2017, 4:44 PMfor #2 I got help - I need to replace my APIs so that instead of Hashmap (no import) I either use kotlin.collections.MutableMap or kotlin.collections.HashMap
Nicholas Bilyk
07/10/2017, 4:45 PM#1 I'm still very stuck though, it's as if it's using an entirely different package object or something
Nicholas Bilyk
07/10/2017, 4:45 PMbut I'll keep trying to isolate
Nicholas Bilyk
07/10/2017, 6:06 PMSo here was the biggest reason I was having so many problems:
I told IDEA to update my kotlin plugin to 1.1.2 stable, when I hit issues with that, I went to 1.2-M1, but when that was even worse I told it to go back to 1.1.2. Apparently what happened there is that 1.2-M1 got placed in my users directory, so when I told the configure kotlin updates to go back to stable 1.1.2 it didn't actually do anything and I was using 1.2-M1 unwittingly.
Nicholas Bilyk
07/10/2017, 6:08 PM1.2-M1 feels like a branch that doesn't have dozens of bug fixes I've seen put in over the last year
b
bashor
07/10/2017, 6:15 PM1.2-M1 should be very close to 1.1.3