-
Notifications
You must be signed in to change notification settings - Fork 146
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
Type information (module augmentation) doesn't work properly with the library effect
#967
Comments
@nayeemrmn or @bartlomieju any ideas about how to move this one forward? All of my code uses |
@evelant Have you tried using |
Unfortunately I can't use npm specifiers yet. I'm using Supabase and npm specifiers aren't supported by their Deno edge runtime yet. |
@nayeemrmn any update on this? I still can't import effect from esm.sh and have types work in vscode_deno. It runs without issue but it's nearly impossible to develop effect code without typescript support. |
@evelant I also get these errors from running |
Describe the bug
When importing effect from
https://esm.sh/[email protected]?target=denonext
the extension fails to provide correct types to the editor.effect
uses standard module augmentation for many of its types.effect
works fine with normal typescript, and Deno can run it without issue, it is only the vscode_deno extension that fails to load the types correctly.To Reproduce
Reproduction here: https://github.com/evelant/deno_effect_test
Expected behavior
vscode_deno should load types correctly
Screenshots
N/A
Versions
vscode: 1.84.0-insider deno: 1.37.1 extension: 3.25.1
The text was updated successfully, but these errors were encountered: