Why We Added Package.json Support to Deno

It doesn't really talk about why support for `package.json` was necessary. Is Deno aiming to be a drop-in replacement for Node? Because with the plans outlined here I see a path forward for enabling developers use npm packages easier but I'm still not clear why it had to be specified in `package.json`.