Guy Bedford

We've been able to support Webpack builds of google cloud libraries in ncc through the use of static analysis in our asset relocation loader (https://github.com/zeit/webpack-asset-relocator-loader), which should support both client...

@bcoe more than happy to share how we achieved this with ncc, and possibly even make our approach available to other webpack users, but it does involve an asset analysis...

Thanks for the feedback, very good point with regards to the options bag second argument possibly being a more future-extensible design. I've posted https://github.com/whatwg/html/issues/8077 for further discussion on the topic.

Treating a feature like this as part of equivalence instead of canonical serialization would mean it definitely wouldn't apply to JS module system instance identification. For example, all JS module...

I think the proposal would be to just dedupe `pathname` in the `file:` scheme URLs and not any other URL parts (so leaving the Windows hostname etc). @alwinb do you...

Certainly agreed, I think for the most part we've accepted the state of percent encoding at this point. This issue was specifically about the `/` separator deduping only in the...

@rmisev the UNC string in a file URL, as far as I'm aware, is always of the form `file://host/pathname` and not `file:///host/pathname`. As a result `new URL()` treats the UNC...

@rmisev in Node.js we explicitly create `file://host.example.com/...` in these cases so I wasn't aware of this more verbose form. That seems like a good counter example.

I guess this isn't a blocker though - it just complicates the story a little: 1. Is the file URL a UNC form (`file:////` detection being non-ambiguous as the indicator...

> or example, a relative URL from https://example.com/full/ to https://example.com/full/path/resource could return a string in the form //example.com/full/path/resource I'd like to explicitly state that the use case of getting `//example.com/full/path/resource`...