4 ms·
I don't know why deno is veered off hard from package.json and node ecosystem rather than supporting it and enhancing from it. It makes adapting deno a hassle a
by fendy3002 4y ago
I don't know why deno is veered off hard from package.json and node ecosystem rather than supporting it and enhancing from it. It makes adapting deno a hassle and hard than transitioning nicely from node.
- verdverm 4y agoIt's going to be a hard case to make to management, while bun is a drop in replacement, for npm, that does make a small part of JS better I wonder if Deno as a word is a premonition for what it will do to node, split in the middle and rearranged to look shinny again
- verdverm 4y agoTurns out bun is not a drop in replacement and has decided to make its equivalent of package.json a binary file... smh
- eyelidlessness 4y agoMy understanding (which I’m sympathetic but not married to) is because Deno’s module system, along with those of the web APIs it embraces, provide a sufficient abstraction layer for `npm` (the client, not the business) to be built on. Various approximations of this are good enough that people are using Node and Deno almost interchangeably. The extent to which they don’t work mostly boil down to packages expecting a fully complete Node environment or a fully complete browser environment.