Closed samtay closed 1 year ago
This is caused by some conflict in the typescript
and dart
packs. A minimal reproducible example is to take a fresh astrovim config from https://github.com/AstroNvim/user_example and change plugins/community.lua
to:
return {
-- Add the community repository of plugin specifications
"AstroNvim/astrocommunity",
-- example of imporing a plugin, comment out to use it or add your own
-- available plugins can be found at https://github.com/AstroNvim/astrocommunity
-- { import = "astrocommunity.colorscheme.catppuccin" },
{ import = "astrocommunity.pack.typescript" },
{ import = "astrocommunity.pack.dart" },
}
I can't reproduce locally. Got both pack's enabled in my config
Nor do I get the issue when using the Minimal rep. example from your post. Have you updated all packages, including all mason stuff?
Wow, that is bizarre. Yes, I'm up to date on everything. And when I used the minimal example I cleaned and synced the plugins and pakages. I'm on arch linux, don't know what else would be relevant :shrug:
Let me test on arch
Managed to recreate in Arch
Managed to Get this issue on Mac now
This seems to be an issue with typescript.nvim
based upon my chat with mehalter in #dev in discord
Actually, it's the other way around. flutter-tools seems to affect the lsp setup. 🤣
Nah, neither of the plugins are broken. The dart pack is very broken here
hey I was trying to live report your findings 🤣 The log here is just an transcription
This was working, but all of a sudden (presumably after some update of packages) now when I open TS files I just see this:
and the LSP fails to start.
This is just using a vanilla config:
{ import = "astrocommunity.pack.typescript" },