3 ms·
This is not (just) about adding a compatibility layer. The original deno presentation complained about the whole concept of a module that Node introduced (rathe
by tsimionescu 4y ago
This is not (just) about adding a compatibility layer. The original deno presentation complained about the whole concept of a module that Node introduced (rather than "simply" referencing script files the way an HTML page does), it complained about the need of an additional file to specify imports etc.
The blog post explains in detail why these things are actually required and useful, and introduces the new deno.js file that is functionally equivalent to package.json. So even purely deno packages meant to be used entirely in the deno ecosystem are encouraged to use the new package.json 2.0, for many of the same reasons package.json was introduced in Node all those years ago.