2 ms·
This is the right way to go. Nodejs is “good enough”. package.json is entrenched. Deno gains nothing from not supporting package.json, and has everything to
by andrewstuart 4y ago
This is the right way to go.
Nodejs is “good enough”.
package.json is entrenched.
Deno gains nothing from not supporting package.json, and has everything to gain from becoming a “better node than node”.
Deno will pick up steam if it can become a drop in replacement for nodejs. Then people can start to exploit its unique features.
Ideally I could replace node and switch to deno by doing “npm install deno” from within an existing node project