Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

From Node to Deno

dev.to

Post reply on HN
Print view View original

1–10 of 100 posts

Re: From Node to Deno

#2

Post by k__ »

Desktop apps build on Electron should be a good fit for Deno, because Denos API is more like a Browser API than like the Node API.

Re: From Node to Deno

#4

Post by littlestymaar »

milutinovici wrote: post #3

The one big thing missing is an ORM. And making those things is notoriously difficult. Hopefully something will turn up

Since the underlying DB driver exists, you could probably fork one existing node one, or even submit a pull-request for demo support in your favorite node ORM.

Re: From Node to Deno

#6

Post by ralusek »

Thanks for doing this. I have a few questions regarding packages/dependencies, and TypeScript in general.

I tried installing Deno, and I tried including a package, and immediately the TypeScript typechecking in my IDE (VSCode) failed, of course. The IDE doesn't know what to do with a URL as a dependency. Is this something Deno will be able to handle?

The next question is that TypeScript packages I have written in the past use `baseUrl` and `paths` in their own configs to allow for absolute import paths. When I look at third-party Deno repositories, I didn't see any that were building out to JS/declaration files, and were instead just meant to be included as the original TypeScript source code. Won't this break things like absolute import paths and other behaviors of the dependency's own tsconfig file, or does this work fine with Deno/TS?

Re: From Node to Deno

#7

Post by ralusek »

will_raw wrote: post #5
milutinovici wrote: post #3

The one big thing missing is an ORM. And making those things is notoriously difficult. Hopefully something will turn up

Curious, Why do you think it will be "notoriously" difficult?

If something is notoriously difficult, it isn't up to what one individual thinks. That's what makes it notorious.

Re: From Node to Deno

#8

Post by jdxcode »

milutinovici wrote: post #3

The one big thing missing is an ORM. And making those things is notoriously difficult. Hopefully something will turn up

Are ORMs even that great? In my experience they invariably end up just being a messy abstraction to work around.

Re: From Node to Deno

#9

Post by hn_throwaway_99 »

milutinovici wrote: post #3

The one big thing missing is an ORM. And making those things is notoriously difficult. Hopefully something will turn up

The idea that ORMs are a net-positive is definitely an open question. After 20+ years I'm certainly of the opinion they're not. I recently discovered Slonik (only for postgres, hope there is eventually a port for MySQL and others) and I'm a huge fan of the overall approach and the API. This blog post from the creator explains: https://medium.com/@gajus/stop-using-knex-js-and-earn-30-bf4...

Re: From Node to Deno

#10

Post by brlewis »

ralusek wrote: post #6

Thanks for doing this. I have a few questions regarding packages/dependencies, and TypeScript in general. I tried installing Deno, and I tried including a package, and immediately the TypeScript typechecking in my IDE (VSCode) failed, of course. The IDE doesn't know what to do with a URL as a dependency. Is this something Deno will be able to handle? The next question is that TypeScript packages I have written in the…

https://stackoverflow.com/questions/54794933/how-to-pull-typ...

Looks like there's a plug-in. Can't research much now, but I hope there's something like that for emacs tide.

Post reply on HN