Continuous Integration with Deno

1 Year Subscription

Node has gained a lot of popularity since it was introduced in 2009. Despite its success, Ryan Dahl, Node’s original creator, believes there’s room for improvement, and so he has recently released Deno, a new runtime for JavaScript and TypeScript, as its successor.

How is Deno different? Well, Deno, like Node, uses the V8 engine and event-driven architecture. But here is where the similarities end.

  • TypeScript gets first-class support at last. Deno compiles to JavaScript without additional packages.
  • Deno ships as a single executable with built-in, Go-inspired test runners and dependency management.
  • Deno has better security by default. Programs run in a sandbox that doesn’t have access to the network, the environment, or the filesystem unless explicitly granted.

The most significant difference, though, is that Deno doesn’t have a package manager (say goodbye to npm). That means Node.js modules are largely unsupported. Instead, Deno uses decentralized ES Modules. To…


Continue reading on source link

Leave a Comment

Your email address will not be published. Required fields are marked *

62 − 60 =