▲ | tracker1 4 days ago | |||||||
I'm somewhat curious how Deno stands up with this... also, not sure what packages are being installed. I'd probably start a vite template project for react+ts+mui as a baseline, since that's a relatively typical application combo for tooling. Maybe hono+zod+openapi as well. | ||||||||
▲ | tracker1 4 days ago | parent | next [-] | |||||||
For my own curiousity on a React app on my work desktop.
So, looks like if Deno added a package-lock.json conversion similar to bun the installs would be very similar all around. I have no control over the security software used on this machine, was just convenience as I was in front of it.Hopefully someone can put eyes on this issue: https://github.com/denoland/deno/issues/25815 | ||||||||
▲ | steve_adams_86 4 days ago | parent | prev [-] | |||||||
I think Deno isn't included in the benchmark because it's a harder comparison to make than it might seem. Deno's dependency architecture isn't built around npm; that compatibility layer is a retrofit on top of the core (which is evident in the source code, if you ever want to see). Deno's core architecture around dependency management uses a different, URL-based paradigm. It's not as fast, but... It's different. It also allows for improved security and cool features like the ability to easily host your own secure registry. You don't have to use npm or jsr. It's very cool, but different from what is being benchmarked here. | ||||||||
|