<@U092308M7> Any plans to update <https://github.com/orangy/multiplatform-lib> to gradle 5.3? I’ve b...

# multiplatform

[russhwolf]

@orangy Any plans to update https://github.com/orangy/multiplatform-lib to gradle 5.3? I’ve been having trouble figuring out the right changes I need to make on the JS side in gradle 5.x and haven’t been able to find a good up-to-date library publishing sample.

[orangy]

I didn’t have any plans, but I think I should…

[russhwolf]

I’m sure you have plenty of other things going on, but I’d certainly appreciate it if you get the time

[russhwolf]

If anyone else is looking for help here, my main issue updating a setup similar to that sample to gradle 5.3.1, gradle-node-plugin 1.3.1, and kotlin 1.3.30 was that the build was looking for package.json and package-lock.json files in the build directory (next to node_modules) when it was running my tests.

My first pass fix was to copy files with just the body {} into that directly as part of the prepareNodePackage task from the sample. That works but generates a couple of warnings, so another option is to take those files after a successful build and check them in.

I suspect there might be a cleaner way to do all that, though, since there’s node configuration happening at the gradle level which I would think should be able to generate the necessary json.