-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 BUG: losing intellisense on typescript imports inside .astro files until editor reload #958
Comments
Everything works as expected for me when following your instructions: Screen.Recording.2024-10-02.at.11.51.44.movI'm not sure how to debug this further. |
Hey, thanks for the response. Can I ask what OS and versions you're using? I haven't had a chance to test any others yet. |
This is on macOS, 2.14.2 of the Astro extension, VS Code 1.93.1. |
I am having this same problem, but on Ubuntu 22.04 with VS Code 1.92.1 |
I've noticed with further use that it also fails to recognise new exported functions in files that already existed, again resolved by restarting the language server. |
My dupe issue above was about autocompletions on components like |
Describe the Bug
MacOS
VS Code extension: 2.14.2
Npm: 10.8.3
Node: 22.9.0
VS Code: 1.93.1
Intelisense in frontmatter imports doesn't seem to be working as expected when dealing with new typescript files. Sometimes I can get it to work for the first instance of a file, but then it fails to import any other files. Either way, reloading the editor after creating any new files fixes the issue.
Steps to Reproduce
npm create astro@latest
(4.15.9 as of today)anything.ts
with the contentsexport const anything = "anything";
another.ts
with the contentsexport const another = "another";
index.astro
and try to import the exported const.import anyt...
I would expect the import to be listed at the top of the autocomplete list, however it does not appear there.Link to Minimal Reproducible Example
https://github.com/lee-arnold/astro-issue-example
The text was updated successfully, but these errors were encountered: