[UPDATE TASK] - update task is incompatible with esm.sh scripts

[bjesuiter]

Description

esm.sh allows managing esm imports in import maps via it's cli

The Command

deno run -A -r https://esm.sh init

sets up the following scripts in deno.json:

  "tasks": {
    "esm:add": "deno run -A https://esm.sh/v129 add",
    "esm:update": "deno run -A https://esm.sh/v129 update",
    "esm:remove": "deno run -A https://esm.sh/v129 remove"
  },

For example: Running deno task esm:add zod , results in a change in import_map.json of:

"imports": {
    "zod": "https://esm.sh/v129/zod@3.22.2",
    "zod/": "https://esm.sh/v129/zod@3.22.2/"
}

The basic problem

• The esm.sh cli does not support import maps inside deno.json/deon.jsonc (currently)
  => Open Issue: CLI assumes import_map.json even if deno.json has imports esm-dev/esm.sh#687
• The fresh update script forces migration from an external import_map.json to "imports" inside deno.json/deno.jsonc

Possible Solutions

QuickFix: Publish a manual migration guide for each fresh version

This allows skipping the fresh update command altogether

Preferred solution: Make fresh upgrade script not force-migrate import_map.json

Why should fresh care at all, which import map solution is used?
For new projects, the inlined version can be used, but for existing projects it should simply keep the existing format

Another Solution: Make this import map migration configureable in the update script

CAUTION: This might introduce a lot of complexity, therefore I'd recommend only detecting the used variant (deno.json with imports or external import_map.json) and keep using the existing one.