How is Deno coming along?

Deno was the new hotness a little while ago. Basically every JS post was Deno for a while.

... How are things going now that things have settled down? Who's using Deno?

Comments

[Aral Roca]

Interesting question. I'm also intrigated. Personally I used Deno only on dummy side-projects, but not yet in a real one.

[Clavin June]

evenif it's prod ready, but I don't think the community is big enough to handle most use cases.

wdt?

[Jonathan Boudreau]

I'm still waiting for package management to become stable.

[Zane Milakovic]

There is no package management. It’s not ideal.

Create a deps.ts file and export any thing you need to import.

If you want to use a interface in your code similar to node where you regency the “module”, then use the import map feature.

Not sure what you are waiting on. The package managers for deno, just make it easier to create a import map. It’s not like NPM by design.

[Pacharapol Withayasakpunt]

I think it depends on how much it can replace frontend tool set.

For backend, I think it works well, but cannot replace Node, not to mention other languages' competitors.

[Jakub Patočka]

I often use Deno for my small automation scripts / local tools.
I like that I can use TypeScript based on the V8 JavaScript engine and modules without using third-party tools like Babel. It also comes with its own bundler and tester. No more npm install whatever --save-dev. Deno handles packages by itself just from code. Deno gives me free hands when I want to write a small script without any configuration and that's why I personally like it. I also like its permission policy.

[***]

Do you have some tutorial for creating modules with Deno?

[Erisan Olasheni]

lyty.dev/deno/deno-module.html

[Pacharapol Withayasakpunt]

I am currently looking for esbuild or esbuild wrapper (like snowpack) that doesn't need node or npm.

I am not sure if deno's native can minify yet?

[Shravan Kumar B]

There should be some bridge, to move Node projects to Deno projects.

I understand that it's not possible, taking consideration that they are two different environments. But there should be away to handle this.

Taking NPM packages as url based package like in Deno.

If we have this bridge to build Node projects to Deno, I believe won't take more than a 3-4 years for Deno to prevail.

[Zane Milakovic]

Pika package, skypack, and unpkg.

Basically those services take NPM package and wrap a module around it. Most of them work today.

Node has module support. If the NPM package has it, it works in deno.

Node specific calls that can’t be emulated in deno, or dependencies that won’t work through the services I said above won’t work. But many things just do.

[Pacharapol Withayasakpunt]

Deno also has Node's commonjs and module's compatibility layer.

github.com/denoland/deno/blob/mast...

[Matthieu Cneude]

I asked myself the same question two days ago. I concluded in 2 minutes that it was again a trend dying off as fast as it came.

[Galuh Utama]

I tried it a bit for a while and can’t really see its appeal for me to move from node.

I‘d like to be proven wrong though but it seems to me deno is just another huge effort to solve workable problems that exist on node.

I guess only time will tell whether it will replace node or die because of insignificant userbase.

[Zane Milakovic]

Many issues can’t be solved in node that deno solves.

I don’t think you want to migrate, as much as when you do a new project, check it out.

[Dong Nguyen]

I have installed and tested some features since last year. Deno is cool but not great enough to push me switch to it from Node. Converting would take so much time.