Ryan Cavanaugh
Ryan Cavanaugh
> A solution needs to be found in order to bring it back to a reasonable state. We looked for a solution and didn't find any that were acceptable, and...
@guest271314 I think you've weighed in on this enough now, thanks for the feedback
Please open a new issue with repro if you're still seeing this. Thanks!
Given the short future of language service plugins in this particular architecture going forward, and the risk of breaking other plugins, I don't think we want to mess with this....
For consistency, imports are generated if there's an apparent value reference, even if it's inlined at the end. You can use `import type` if you don't want this to appear.
🤖 Thank you for your issue! I've done some analysis to help get you started. This response is automatically generated; feel free to 👍 or 👎 this comment according to...
Unfortunately it's pretty easy to hold the compiler API the wrong way and cause weird exceptions. We need a complete runnable standalone repro in order to investigate.
Closing language service bugs related to the 6.0 implementation. For more information, see #62827
There isn't a huge amount of logging in this code (see `src/server/project.ts` around line 2500 for the `AutoImportProviderProject`). Given that package.json I'm guessing you have more than 10 entry points...
Totally. We're rewriting auto-imports in TS7 and it'll have smarter bail-out heuristics. If you can publish your package somewhere we can pull it, we could probably see why it's not...