| ▲ | 40four a day ago | |
Deno continues to impress me. It’s honestly been quite a while since I started a new project without it. It has fully won my support over Node.js, the ecosystem has really matured nicely. I don’t know how often I’ll use this feature, but it’s really nice to have the option! | ||
| ▲ | liamgm 11 hours ago | parent | next [-] | |
yes the big win from this is the Node API / NAPI support , if you write node_modules in nodejs , electron , raycast , edgejs you can reuse it . https://wasmer.io/posts/edgejs-safe-nodejs-using-wasm-sandbo... "NAPI allows native Node dependencies to target Node without actually depending on a specific version of Node or V8. NAPI abstracted the V8 JS engine away, by providing JS-like APIs for: creating an object, declaring a property, etc. NAPI is the contract that all modern native Node modules use to interact with Javascript." [1] 1: https://wasmer.io/posts/edgejs-safe-nodejs-using-wasm-sandbo... | ||
| ▲ | esperent 9 hours ago | parent | prev [-] | |
I'm still using node/npm and it's... fine. Every so often I read these posts and think I should change but node/npm is already a low friction part of my workflow. However, what I have seen is that a lot of other libraries I use have switched to Bun. I haven't seen any that switched to Deno, and so I've been under the impression that Bun is becoming a strong node replacement candidate while Deno is not, or at least that the community is making a strong preference for Bun. Anyone have more insight into this? | ||