Deno 1.34: Deno compile supports NPM packages

Re:Deno 1.34: Deno compile supports NPM packages by lytedev on Thursday May 25, 2023 @09:22AM (#36070388)

For an admin, I'm not sure. The deployment and CI/CD story may be cleaner? The real win to me is the developer experience. Deno comes with everything: test runner, linter, typescript, language server, etc. That's the winner for me.

[ Parent | on HN ]

Re:Deno 1.34: Deno compile supports NPM packages by _joel on Thursday May 25, 2023 @01:37PM (#36073663)

Cheers, I worded that badly I suppose but you answered the question I meant :)

[ Parent | on HN ]

Re:Deno 1.34: Deno compile supports NPM packages by satyarohith on Thursday May 25, 2023 @02:22PM (#36074182)

Disclosure: I work at Deno

For example, if you use Deno first frameworks like fresh and use Deno Deploy, you’re eliminating build steps. You git push and the application is live across the world in 1-2 seconds. It feels like magic.

[ Parent | on HN ]

Re:Deno 1.34: Deno compile supports NPM packages by simultsop on Thursday May 25, 2023 @03:53PM (#36075302)

Honestly it would feel magic back in 2009. Currently there are huge waves of changes. Everyone trying to offer utopian ecosystem. If the tendency is to gather community, it seems they need to chase companies given that many have somewhat stable stacks. Reshaping existing projects requires way more sacrifices. For example the major shift of Vue 2 to Vue 3, disrupted entire plugins ecosystem for Vue 2. People barely get motivated rewriting same thing for sake of composition api while options API remained. Idk exact reasoning, but there is a huge tech debt on Vue 2 plugin ecosystem. So again sacrifices, sacrifices.

[ Parent | on HN ]