Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> There's no need in the deno world to even use a package manager

That doesn't sound like I thing I would want.



It is a package manager. It's just integrated into the runtime to the point where you import things and it "just works".


How does that pan out as an application grows and you're pulling in the same dep across numerous files?


You still get one shared copy of that dependency. Why would it be any different?


How do you ensure that across files on a large project?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: