Support import maps

[jaydenseric]

Ideally there would be a way to specify, perhaps in a URL parameter, an import map that goes along with the documented module.

There could be UI to tweak the import map, which would update the parameter in the URL and regenerate the docs.

For example, the docs for this module breaks due to the bare react import specifier:

https://doc.deno.land/https://unpkg.com/[email protected]/waterfallRender.mjs

That module works great in Deno projects with an import map that assigns a Preact ESM URL to the react specifier.

I would absolutely 😍 love 😍 to be able to just link to Deno docs in the readme for all my universal Node.js/Deno packages that rely on import maps, instead of maintaining complicated API docs markdown by hand. Hardcoded docs can have mistakes that get permanently published for that package version; whereas having docs generated on demand allows them to just get better and better over time as Deno docs improves, for all versions of the package.

[kitsonk]

It is a useful feature.

I can see adding support for a query parameter like ?im=https://example.com/import_map.json or something like that.

Need to check to see how we need to expose it from deno_doc in the JavaScript API and then flow that through to the app.