Haxe dependency explorer still shows (dev) version of library

[zagortenej]

I cloned Lime from git and set the folder where I checked it out as library path for dev version in haxelib:

haxelib dev lime /path/to/lime

I created another project that had Lime as dependency and vshaxe dependency explorer shows lime (dev), as it should. After a while, maybe few days, I installed latest Lime version via haxelib and removed dev:

haxelib dev lime
haxelib update lime

Now Lime is at 7.3.0 but when I open my project I still see lime (dev) there and it still points to the folder where I cloned Lime (I didn't remove the folder). This hasn't changed after I restarted VSCode, my workstation, my parrot or my cat. I even left out for an hour to play ball and when I got back it was still there 😉

I notice when loading the project that very shortly dependency explorer shows Lime version 7.3.0 and then reverts to show lime (dev).

The only way I found to fix this is to switch from Lime "Haxe Completion Provider" (which I use by default when working with Lime projects) to Haxe completion provider and then switch back to Lime completion provider. Restarting VSCode does not work.

In any case, if this is not lime-vscode-extension bug, the trick with switching completion providers might help if someone else has the same issue.

[Gama11]

Have you recently rebuilt the target that's selected in the status bar? What does lime display <selected target> say?