Why We Added package.json Support to Deno

The latest release of Deno introduced a significant change: providing enhanced Node and NPM compatibility through package.json support. This update led to questions regarding whether our priorities have shifted, as Deno has long been associated with forging a path distinct from Node. Indeed, package.json was explicitly mentioned as a regret in the first Deno presentation. Thus, many users were sur

[dec123456789]

deps.ts, lock.json, deno.json, package.json...なんかどんどん複雑になっていくな…これがDenoの目指したかった世界観なのか？