DEV Community

loading...

Discussion on: From Node to Deno

Collapse
maskedman99 profile image
Rohit Prasad

Anything that gets rid of the bloated node_modules folder is a win for me.

Collapse
yuripredborskiy profile image
Yuri Predborskiy • Edited

I'm not a fan of all the bloat either, but it doesn't seem like we can change much, other than pulling all that code directly into our project and bloating the project files instead.

And then again, deno gets rid of bloated node modules folder how? By creating deno crates or something? My guess is it will be just as bloated very soon. It is a side effect from the ecosystem that relies on updateable plug-ins which use other plug-ins.

Thread Thread
quantumfillet profile image
QuantumFillet

Where would the bloat come from? Managing dependencies is as easy as creating a single typescript file with all the imports and Deno does the rest. No need to deal with node_modules. Here is a github issue discussing your grievances

Thread Thread
yuripredborskiy profile image
Yuri Predborskiy

This talks a lot about all the issues I have with deno way. Sadly, the discussion is simply closed without an answer.

Thread Thread
quantumfillet profile image
QuantumFillet

How about this reply

P.S. I'm not here to convert you to Deno xD, but if you dislike the idea of learning another technology in the already overwhelming web dev environment then I totally get where you are coming from.

Thread Thread
yuripredborskiy profile image
Yuri Predborskiy

It's actually CTCI + leetcode that take up all of my time. Including weekends.
I plan to devote some time to hobby projects down the line (including getting to know typescript, which seems to blend well with Deno), but it is not very high on my priority list at the moment.

Thread Thread
quantumfillet profile image
QuantumFillet

CTCI... oh boy.

I also have rather limited time atm, but if you want create something down the line with deno, let me know.