5 ms·
I don't buy it, you can already use stuff like skypack or other bundling CDNs to import npm modules in deno just by their URL. You have a very bizarre argument
by qbasic_forever 3y ago
I don't buy it, you can already use stuff like skypack or other bundling CDNs to import npm modules in deno just by their URL.
You have a very bizarre argument that I don't follow. I don't care about the "purity" of the project, I care about getting shit done and deno is helping greatly there.
- toastercat 3y ago> I don't buy it, you can already use stuff like skypack or other bundling CDNs to import npm modules in deno just by their URL. It's not that simple if the project you are importing uses Node-specific APIs. By the way, this is an area that can really confuse newbies.
- no_wizard 3y agothen you're stuck with a CDN you don't control. The runtime (Deno) being able to work directly with most packages on npm is a huge win because I don't have to trust a 3rd party for this anymore, and that to me is a big win.
- qbasic_forever 3y agoAgreed, I'm just refuting the reply above that deno recently besmirched some bizarre purity by adding friendly node NPM support. From the very beginning of deno you could import any JS code, including simple stuff from npm that didn't rely on then unsupported node APIs.