What do you guys think about this idea: for kotlin-js gradle plugin (and MPP counterpart of it) move...

# javascript

[Big Chungus]

What do you guys think about this idea: for kotlin-js gradle plugin (and MPP counterpart of it) move the yarn.lock files outside of build directory to either project root or some external structure so those would be pushed to git and serve their purpose?

[Sam Garfinkel]

The build.gradle(.kts) serves this purpose especially since npm dependencies require explicit version numbers.

[Big Chungus]

Not quite. With yarn lock the versions are resolved and locked without having to specify them explicitly

[Big Chungus]

P.s. versions for npm dependencies can be omitted in gradlefile

[ribesg]

They can be omitted, but should they be?

[Ilya Goncharov [JB]]

It sounds logically
There is issue on YouTrack
https://youtrack.jetbrains.com/issue/KT-34014

[snrostov]

They can be omitted, but should they be?

Well, even they are not omitted for your dependencies, it may be still omitted for transitive dependencies. yarn.lock should help in this case too.

The main problem here is that it will look scary for people not familiar with yarn (I mean to commit something that was created during build). But we may do special mode when the root package.json is located outside of build directory. This will be also useful when you need to include a handcrafted js package (with your own package.json).

[Big Chungus]

Something as simple as a config to override yarn.lock location would be super useful