how can i get v1.2.4 with the auto-import fix?

[chase-moskal]

:wave: hello fine folks, i'm glad to see that this project is being maintained!

the auto-import bug has been a thorn in my team's side -- we're confused about how to obtain the fabled fix for this bug

it looks like the bug has been fixed, and it's been said that the fix has been released :thinking:

• 200

  • the bug is marked closed

• 250

  • the pull request for v1.2.4 is merged, and the 1.2.4 branch was deleted
  • this merged vscode-lit-plugin changelog entry for 1.2.4 that claims the auto-imports have been fixed
• @rictic even announced the fix has been released in issue 200

  Forgot to update here last week but the updated version is now released!

however, i don't seem to see this release anywhere? am i looking in the wrong places?

• vscode extensions tab and open-vsx show v1.2.1 as the latest
• ts-lit-plugin on npm shows v1.2.1 is the latest
• github releases page indicates v1.2.0

we're just very eager to get this fix!

is v1.2.4 with the fix under some different package/extension name? or perhaps there has been some mistake where this version failed to be published? maybe i'm just confused, and it hasn't been released yet?

we're even willing to follow some back-alley shell-scripted instructions, if it helps us install the development copy necessary to get this fix ;)

thanks friends for any help :beers:

[justinfagnani]

My VS Code installation just automatically updated. I don't know what open-vsx is, but the Visual Studio Marketplace where we publish to shows v1.2.4: https://marketplace.visualstudio.com/items?itemName=runem.lit-plugin

One thing I notice is that in my VS Code I see > 40k downloads, while yours shows just 1.1k. Something seems up there.

What happens if you uninstall and reinstall the extension?

[justinfagnani]

Ok, looks like from here that @runem had published this to open-vsx at some point and we need to resume doing that: https://github.com/runem/lit-analyzer/issues/151 We didn't get permissions to publish there yet like we did with Visual Studio Maketplace so we'll need to work that out with @runem and it could take a bit. cc @rictic

@chase-moskal can you install from the Visual Studio Maketplace in the mean time?

[chase-moskal]

ahah! thanks so much @justinfagnani, now i understand what's going on!

unbeknownst to me, here on manjaro linux, i was actually running a non-microsoft oss distribution of vscode — the official archlinux code package — this package has modified extensions support by using the open-vsx extensions registry (instead of the official visual studio marketplace)

as it turns out, many of the open-vsx extensions are out of date by comparison with the visual studio marketplace.

i solved this issue by

• uninstalling code package with sudo pacman -R code
• enabling AUR packages in manjaro's "add/remove software" program's preferences
• installing visual-studio-code-bin from the AUR (i just used the gui program "add/remove software" to do this)
• launching vscode with code . and now the extensions area within vscode provides access to lit-plugin v1.2.4
• now my auto imports work :tada: :tada:

i hadn't realized my vscode was using an alternative extensions registry (it's well-integrated in the oss distribution), and of course seeing the npm package being outdated had also confused me.

of course, i'm sure it would be nice if the deployment routine for lit-plugin included publishing to the open-vsx registry also — but this problem is solved from my perspective, so feel free to close this issue.

thanks again! :beers: