chore: update for deno 2

[load1n9]

Description

Related Issues

Check List

• Have you read the
  CODE OF CONDUCT
• Have you read the document
  CONTRIBUTING
  • One pull request per feature. If you want to do more than one thing,
    send multiple pull request.
  • Write tests.
  • Run deno fmt to fix the code format before commit.
  • Document any change in the CHANGELOG.md.

[marvinhagemeister]

FYI: Changing this is more personal preference. The task command will be the same in Deno 2 as it is today. I guess I'm just trying to get a feel if people like deno run more or if our messaging at Deno sent the wrong signal in that we would be deprecating deno task or something. If so, please let us know 😅

[load1n9]

I see, what do you think we should have it as

[oscarotero]

Honesty, I don't like this change in Deno because it opens the door to inconsitencies and makes the API even more complicated and confused than it's currently:

• deno run can run files and tasks
• deno ... only can run files but not tasks
• what does deno run npm:foo run? the npm:foo package or the npm:foo task?
• I have been eagerly waiting years for this Support deno run resolving bare specifiers with import map denoland/deno#19955 in order to simplify the lume task, but now, if it's merged it will create more inconsistencies. For example, what does deno fmt run? the fmt bare specifier from import maps (if exists) or the fmt command of Deno?

deno task ... and deno run ... were clear and easy to understand. You don't have to do ALL what Node/NPM do.

[oscarotero]

thank @load1n9 !!

In addition to the deno task/deno run CLI changes (of those I've expressed by disagreement, but I suppose it's how Deno is going to work until now, so I have to deal with it), I don't see any significant change, only code style. So I don't understand what this PR is trying to fix.