-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add recipe for remote node modules #27
Comments
Yep! The answer to this is ata but the long answer is, whew, it's hard and we've poured days into improving type acquisition and it is still really tough. Making TypeScript and Deno get along is extremely hard - TypeScript doesn't support I've been planning on refactoring our code and might be able to make it OSS, but can't promise that it'll be all that robust 😭 |
We're also thinking about integrating with Deno LSP run on a server somewhere. In theory it could also be fun to try getting the Deno LSP server running in wasm on the browser but I am not very hopeful about that. |
would be very cool |
btw @tmcw thanks for sharing I'll play with this and share any updates. |
Even if it's not...anything helps! |
Just as a note: I managed to get this working with |
Possibly some relevant notes for Deno here: microsoft/TypeScript-Website#2097 |
I managed to get this working for |
All right - here's our Pretty unfinished/unpolished, this is derived from a refactor that I've been working on of this code. |
thank you! it’s private though btw |
Whoops - it's public now |
A useful feature is to let you use any node modules in the editor. However, this requires 1) parsing the file, 2) querying NPM for their types (potentially
@types/package-name
) and lastly inserting the types intocodemirror-ts
. It could be useful to document the ideal way to handle 2 or maybe abstract it into a functionFor deno, these would be URLs and/or
npm:package-name
, but it could be cool to support bothThe text was updated successfully, but these errors were encountered: