bug: TypeScript 4.8 unable to discover @preact/signals for auto import
See original GitHub issueDescription
Not sure if this is the right place to post this TypeScript specific issue but I found out that auto importing @preact/signals fails in VSCode when using latest TypeScript 4.8. Auto importing works just fine when downgrading to TypeScript 4.7.
Affected TypeScript version: 4.8.3
Affected @preact/signals
version: 1.0.3
Steps to reproduce
- Create a
.ts
or.tsx
file with simple TSConfig file. - Write
signals
to trigger VSCode’s autocompletion to auto importsignals
from@preact/signals
Expected behavior
Auto imports should work when typing signals
Actual behavior
Auto imports fails to auto import anything from @preact/signals
when using TypeScript 4.8.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
TypeScript 4.8 fails to auto import @preact/signals #50705
Bug Report TypeScript 4.8.3 is causing auto import in VSCode to fail for @preact/signals. See similar reported bug here.
Read more >Issues · microsoft/TypeScript · GitHub
TypeScript 4.8 fails to auto import @preact/signals Needs More Info The issue still ... Fix import statement completions followed by interface declaration.
Read more >typescript auto imports not working macos - Stack Overflow
Yes. It may be the reason. Try the second fix. go to settings => search for 'tsdk' => click on edit in settings.json...
Read more >Aral Roca (@aralroca) / Twitter
Introducing Preact Signals: a reactive state primitive that is fast by default. ✓ feels like using plain values automatic updates when values change...
Read more >Creating a VDOM-less Renderer with Preact Signals - YouTube
Your browser can't play this video. Learn more. Switch camera.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@andrewbranch That sounds perfect 👍 We’ll move the
types
entry to the top of the list. Thanks again for reaching out that’s really awesome!@marvinhagemeister Thanks and I’ve moved this to the TypeScript Github repo.