Custom path mapping starting with # failing because exec interprets it as a comment

[skeithtan]

I have a custom math mapping in deno.json.

The name of the mapping starts with a # character, e.g., #some-name.

When building in vite, this causes the build to fail:

vite v5.4.11 building for production...
✓ 62 modules transformed.
x Build failed in 591ms
error during build:
[commonjs--resolver] Cannot read properties of undefined (reading '0')
    at resolveDeno (file:///path/node_modules/.deno/@deno+vite-plugin@1.0.2/node_modules/@deno/vite-plugin/dist/resolver.js:34:32)

The stacktrace specifically references this line here:

deno-vite-plugin/src/resolver.ts

Line 90 in 9f6c6fe

const actualId = json.roots[0];

That's because the string passed to exec here looks like so:
deno info --json #some-name/some-path.ts

Since the name of the mapping starts with a # sign, this was interpreted as a comment, therefore only really running the command deno info --json which outputs something like so:

{
  "version": 1,
  "denoDir": "/REDACTED/Library/Caches/deno",
  "modulesCache": "/REDACTED/Library/Caches/deno/remote",
  "npmCache": "/REDACTED/Library/Caches/deno/npm",
  "typescriptCache": "/REDACTED/Library/Caches/deno/gen",
  "registryCache": "/REDACTED/Library/Caches/deno/registries",
  "originStorage": "/REDACTED/Library/Caches/deno/location_data",
  "webCacheStorage": "/REDACTED/deno_cache"
}

Which, when parsed, does not have a roots field, and therefore fails in this line.