Any body else having problems with creating the ne...

# javascript

[hfhbd]

Any body else having problems with creating the new npm lockfile? I always need to run clean kotlinUpgradePackageLock multiple times because it often adds some missing lines to the lockfile, like the names of kotlin js dependencies or wrong api dependencies,

[Artem Kobzar]

@Ilya Goncharov [JB] ^^

[eygraber]

I've seen this also, but I have to use some combination of --no-build-cache --no-configuration-cache --rerun-tasks to get it to work

[Carter]

I had a conversation thread about this a while back. https://kotlinlang.slack.com/archives/C0KLZSCHF/p1712846061637619

One of the suggestions was to wipe the lockfiles and let it regenerate from scratch, since incremental generation doesn’t work as well.

[eygraber]

I think wiping the file didn't work for me. I had to use those flags to get it to work.

[Robert Jaros]

I had this problem with old yarn.lock 🙂 Changing to new npm lock fixed it for me 🙂

[hfhbd]

Yeah removing the lockfile and running a clean build without any caching works but it’s little bit annoying.