Anyone any idea why the Dukat generated file that ...
# javascript
v
Anyone any idea why the Dukat generated file that compiled perfectly fine yesterday does not compile anymore today without me having anything changed? https://github.com/Vampire/setup-wsl/runs/2443493925?check_suite_focus=true#step:4:114
r
perhaps the ts definitions changed?
v
How can they change? I use only fixed versions
t
You have dependency on plugins in SNAPSHOT version, perhaps change in those plugins broken the build.
v
Is that a question or a statement? I don't think I depend on anything SNAPSHOT, at least not intentionally
m
If it possible that dukat started generating a dependency that wasn’t generated before, I saw this as well. Although I ended up just manually removing the file and the project still compiles. I think most of the dependencies in that file are included via the kotlinx-nodejs package
v
But why should it suddenly start building that, I didn't push anything
Literally nothing changed on my side
m
yeah, thats the weird thing. Maybe the fixed versioning with npm is not as fixed as we thought. After all, I think npm uses the package-lock.json to fix the versions, which (and note that I’ve just started with kotlin js) I don’t think kjs is fully reading
v
Ah, of course, I only use static versions for my direct dependencies, not for the transitive dependencies
Probably one of the transitives changed and broke it somehow
m
Yeah, if I’m not mistaken the package-lock.json includes all transitive dependencies as well, curious as to how kjs implemented that, if any. Specially when its re-created when you run the build command
v
I don't have a package-lock.json
m
Yeah, that might be the issue then…
v
I have a yarn.lock but that is autogenerated in build/js
m
I think the concept is the same, but since its autogenerated its not really a lock lol
v
No, it's just as input for running yarn probably
m
Well it is for your direct dependencies, but as you stated, not sure if it’ll work for transitive ones