After migration on `6 4 0` from `6 3 3` doesn t work followi kotlinlang #kodein

After migration on `6.4.0` from `6.3.3` doesn't wo...

turansky

10/04/2019, 2:26 PM

After migration on

6.4.0

from

6.3.3

doesn't work following JS tests JS lib (target browser) -> MPP lib (jvm { target 1.8 }, js { browser {} }) If JS lib contains test, than:

Copy code

Caused by: java.lang.NullPointerException
        at org.jetbrains.kotlin.gradle.targets.js.yarn.YarnImportedPackagesVersionResolver.updateVersionsMap(YarnImportedPackagesVersionResolver.kt:79)
        at org.jetbrains.kotlin.gradle.targets.js.yarn.YarnImportedPackagesVersionResolver.updatePackageJson(YarnImportedPackagesVersionResolver.kt:71)
        at org.jetbrains.kotlin.gradle.targets.js.yarn.YarnImportedPackagesVersionResolver.updatePackages(YarnImportedPackagesVersionResolver.kt:63)
        at org.jetbrains.kotlin.gradle.targets.js.yarn.YarnImportedPackagesVersionResolver.resolveAndUpdatePackages(YarnImportedPackagesVersionResolver.kt:29)
        at org.jetbrains.kotlin.gradle.targets.js.yarn.YarnWorkspaces.saveRootProjectWorkspacesPackageJson(YarnWorkspaces.kt:51)
        at org.jetbrains.kotlin.gradle.targets.js.yarn.YarnWorkspaces.resolveWorkspaces(YarnWorkspaces.kt:35)
        at org.jetbrains.kotlin.gradle.targets.js.yarn.YarnWorkspaces.resolveRootProject(YarnWorkspaces.kt:24)
        at org.jetbrains.kotlin.gradle.targets.js.yarn.Yarn.resolveRootProject(Yarn.kt:27)

Kotlin

1.3.50

romainbsl

10/05/2019, 6:06 PM

Hi, not sure this that this is kodein specific, with kotlin 1.3.50 jetbrains has released some new plugins for JS, maybe this is linked, we will have to reproduce this to be able to find a solution.

turansky

10/05/2019, 9:05 PM

I create test project for this problem with described plugin configuration https://github.com/turansky/kodein-or-kotlin-bug Reproducing in progress. Also I check latest EAP -

1.3.60-eap-16

- problem also reproduced.

turansky

10/05/2019, 9:13 PM

not sure this that this is kodein specific

I also think that Kodein isn’t root cause, but migration from

6.3.3

6.4.0

reveals the problem. Is there any

package.json

files in Kodein

6.4.0

projects?

romainbsl

10/06/2019, 4:30 AM

I also think that Kodein isn’t root cause, but migration from
6.3.3
to
6.4.0
reveals the problem.

This is related somwhow, we also migrate our build plugins between

6. 3

and

6.4

. Now we'll have to find what...

romainbsl

10/06/2019, 4:32 AM

Is there any
package.json
files in Kodein `6.4.0`projects?

I haven't been that much on the JS side lately. I'll need to work on this to give you a proper answer.

turansky

10/08/2019, 9:12 AM

No problem with

6.4.1

romainbsl

10/08/2019, 9:29 AM

😮 did you change something on your side ? because this is just a bugfix with on line of code correction...

turansky

10/08/2019, 9:33 AM

turansky

10/08/2019, 9:34 AM

Also I found WA for

6.4.0

turansky

10/08/2019, 9:36 AM

WA for

6.4.0

- add

devDependencies

block to custom

package.json

With

6.4.1

WA not required https://github.com/turansky/yfiles-kotlin/blob/master/libraries/yfiles-kotlin/package.json

2 Views

Open in Slack

Previous Next