deno tasks don't use deno.jsonc

[ThisGuyCodes]

I'm working on a Slack platform app, which creates / uses a deno.jsonc file (which Deno works with just find), but the deno task esm:* commands seem hard-coded to expect a deno.json file, and creates one rather than modifying my existing deno.jsonc.

[ije]

@ThisGuyCodes hi! since deno has builtin pakcage manager now, we're planning to depreacte to esm.sh deno CLI tool. instead i'm working on a vscode extension that allows you to search npm module and add it to the import map: https://github.com/esm-dev/vscode

[ThisGuyCodes]

That would be very unfortunate for anyone not using vscode (I'm using zed.dev)