(Replying to PARENT post)

One of the things I love about Deno is that since it implements standard web APIs, many libraries built for the browser just work. For example, I recently made a simple static site generator with Deno to make my blog, and I found that I could use Marked for markdown support simply by importing it like this:

  import 'https://cdn.jsdelivr.net/npm/marked@3.0.7/marked.min.js';
  // now I can use window.marked()
👤binarynate🕑3y🔼0🗨️0

(Replying to PARENT post)

One of the many things about Node that Dahl explicitly wanted to "fix"* when building Deno was that the global namespace should be `window`, because that's what it is in JavaScript's natural habitat.

*scare-quotes because the reader might feel strongly opposed to the term, not because I have an agenda

👤favorited🕑3y🔼0🗨️0

(Replying to PARENT post)

That just seems worse than what npm/yarn have. Despite Node's flaws, at least those have a hash check on the downloaded package against what's in the lock file.

EDIT: I was wrong. See @spoiler's reply.

👤colejohnson66🕑3y🔼0🗨️0

(Replying to PARENT post)

> import 'https://cdn.jsdelivr.net/npm/marked@3.0.7/marked.min.js';

Doesn't this mean your code won't run if the website https://cdn.jsdelivr.net goes down?

In Node.js you download modules you need, to a local folder under you dev-folder. So you can run and develop and test your code whether you have internet connection or not.

👤galaxyLogic🕑3y🔼0🗨️0