Replies: 4 comments 11 replies
-
This might be a bit of a hack but can you do this in a separate file and just import that file instead? // @deno-types="npm:@types/react@18"
export * from "npm:react@18" |
Beta Was this translation helpful? Give feedback.
-
To use
Then optionally, you can configure your import mapping in a
Then, update your
That's it! You shouldn't need to use |
Beta Was this translation helpful? Give feedback.
-
I'm also running into issues with the Vite template (WebStorm not recognizing It still doesn't fix everything, but it at least helps with autocomplete. |
Beta Was this translation helpful? Give feedback.
-
I've found that for migrating all of my More in #27569. I created an example repo for the issue, with a PR showcasing the workaround here: liamfd/test_deno_types#1 Not sure if this is intentional or not - YMMV. I'm on deno |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, in my project I have
deno.json
and my project contains some utilities for React.How can I properly add
@types/react
to whole my project?It's very inconvenient to do this:
...each time I import something from
react
.Is there some guide about how to properly add
@types/*
types for NPM-package?UPD, found the example of React with Deno but types is not working:
denoland/react-vite-ts-template#1
Beta Was this translation helpful? Give feedback.
All reactions