Bug in dependency inspector

[mathiasbynens]

@cdata reported the following resolution error for a module graph that fully resolves in Chrome:

$ deno --info https://unpkg.com/@google/[email protected]/lib/model-viewer.js?module
Downloading https://unpkg.com/@google/[email protected]/lib/model-viewer.js?module
Downloading https://unpkg.com/@google/[email protected]/lib/features/animation.js?module
Downloading https://unpkg.com/lit-element@^2.0.0?module
Downloading https://unpkg.com/lit-html@^1.0.0?module
Downloading https://unpkg.com/lib/default-template-processor.js?module
Cannot resolve module "./lib/default-template-processor.js?module" from "https://unpkg.com/lit-html@^1.0.0?module"

[cdata]

This was tested on a Mac, if it helps.

[kt3k]

This seems like the same bug as this one.

https://unpkg.com/lit-html@^1.0.0?module redirects to https://unpkg.com/[email protected]/lit-html.js?module, but deno tries to resolve ./lib/default-template-processor.js?module from https://unpkg.com/, not https://unpkg.com/[email protected]/.

[ry]

Unfortunately still broken

> ./target/debug/deno https://unpkg.com/@google/[email protected]/lib/model-viewer.js?module
https://unpkg.com/[email protected]/lib/updating-element.js?module:74:37
export class UpdatingElement extends HTMLElement {
                                     ^
Uncaught ReferenceError: HTMLElement is not defined
    at https://unpkg.com/[email protected]/lib/updating-element.js?module:74:38

But it's no longer the redirect error - we just don't have HTMLElement in there...

[kt3k]

I think this issue can be closed because --info option now works for the given url https://unpkg.com/@google/[email protected]/lib/model-viewer.js?module and the entire dependency tree is visible. ( log )

[ry]

Ok closing. Didn’t realize my above command was missing —info 🤦🏻‍♂️