3 ms·

I trialed Deno for an HTTP+WS side project [1] and have been loving it. The simplicity of having Typescript built-in, the nice async APIs, and the sandbox perm

I trialed Deno for an HTTP+WS side project [1] and have been loving it. The simplicity of having Typescript built-in, the nice async APIs, and the sandbox permission system all make it a great choice for green field projects. I don't mind the url-based dependency system as much as I thought I would; with the language server DX it's easy enough to maintain. Deno feels like Node from 10 years ago, in both good and bad ways: every Deno native community library I've pulled in (redis, S3) has had significant bugs. Fixing them has been fun but distracting. Looking under the covers, I've found the code to be really clean as a result of Deno's abstractions. The improving npm support helps to make mature libraries accessible, but the Deno native libs also have a bright future. [1] https://github.com/chromakode/coalesce/tree/main/project-server https://github.com/chromakode/coalesce/tree/main/project-ser...

dunham 3y ago
I tried deno a while ago (over a year) and could not find a way to get deno and typescript to accept the same files. They disagreed about filename extensions in import statements, and I couldn't find a format that was accepted by both.
- AgentME 3y ago
  Are you trying to use Typescript separately from Deno instead of Deno's builtin support for Typescript? Are you using VSCode without the Deno extension? I think you're overcomplicating something if you're running into this issue.
  - dunham 3y ago
    That would be yes on both points. I was unaware that deno needed a separate vscode extension and did not know that deno ran the typechecking itself. I may give it a try on some personal projects now that I know this.
- chromakode 3y ago
  The repo I linked to has an example of shared files between Deno and Vite. I'm using import maps to have a consistent `@shared/types` module between both (as well as consistent names for the requisite imports)

dunham 3y ago

I tried deno a while ago (over a year) and could not find a way to get deno and typescript to accept the same files. They disagreed about filename extensions in import statements, and I couldn't find a format that was accepted by both.

AgentME 3y ago
Are you trying to use Typescript separately from Deno instead of Deno's builtin support for Typescript? Are you using VSCode without the Deno extension? I think you're overcomplicating something if you're running into this issue.
- dunham 3y ago
  That would be yes on both points. I was unaware that deno needed a separate vscode extension and did not know that deno ran the typechecking itself. I may give it a try on some personal projects now that I know this.
chromakode 3y ago
The repo I linked to has an example of shared files between Deno and Vite. I'm using import maps to have a consistent `@shared/types` module between both (as well as consistent names for the requisite imports)