Deno 1.0 - Hackdot

Re:Deno 1.0 by mrkurt on Wednesday May 13, 2020 @08:53PM (#23173845)

I like it because it's simpler. I know what happens when I import from a URL. I'd have a hard time whiteboarding exactly what happens when I `npm install`.

[ Parent | on HN ]

Re:Deno 1.0 by searchableguy on Wednesday May 13, 2020 @09:16PM (#23174029)

What happens?

[ Parent | on HN ]

Re:Deno 1.0 by sakarisson on Thursday May 14, 2020 @01:33AM (#23175707)

My least favorite thing about importing from NPM is that I don't actually know what I'm importing. Sure, there might be a GitHub repository, but code is uploaded to NPM separately, and it is often minified. A malicious library owner could relatively easily inject some code before minifying, while still maintaining a clean-looking repo alongside the package.

Imports from URL would allow me to know exactly what I'm getting.

[ Parent | on HN ]

Re:Deno 1.0 by _630w on Thursday May 14, 2020 @02:48AM (#23176219)

install from the repo then?

You can install a specific version from git via yarn/npm.

How do you trust a url more without reading the code?

What's going to stop deno ecosystem from putting minified js files on cdns and import them?

[ Parent | on HN ]