The casing of CodelensProvider.ts is inconsistent. I run into problems when I try to build this extension myself.
I tried to solve this in my PR earlier, but I believe that you ran into problems with that change and reverted it. Since you can build the extension, you must have a different casing on your computer than in the Git repo...
I suggest that you either change the casing of your local file to the same as in the repo (easiest way in VSC is to delete the file and revert the change - it will restore the file with correct casing) and change the import in extension.ts to match that one - or, you can rename the file in the repo to the desired casing. The last one can be a bit tricky if you only want to change the casing, but I believe that you can use git mv -f for that (ref. https://stackoverflow.com/questions/1793735/change-case-of-a-file-on-windows).
I could do this in a new PR, but I believe that I would only mess things up on your side - so I rather see that you did this instead. 😉
The casing of CodelensProvider.ts is inconsistent. I run into problems when I try to build this extension myself.
I tried to solve this in my PR earlier, but I believe that you ran into problems with that change and reverted it. Since you can build the extension, you must have a different casing on your computer than in the Git repo...
I suggest that you either change the casing of your local file to the same as in the repo (easiest way in VSC is to delete the file and revert the change - it will restore the file with correct casing) and change the import in extension.ts to match that one - or, you can rename the file in the repo to the desired casing. The last one can be a bit tricky if you only want to change the casing, but I believe that you can use
git mv -ffor that (ref. https://stackoverflow.com/questions/1793735/change-case-of-a-file-on-windows).I could do this in a new PR, but I believe that I would only mess things up on your side - so I rather see that you did this instead. 😉