Re: [whatwg/url] Changes to file URL path normalization (#544)

There is a concern here for Node.js modules that `import '//path'` and `import '///path'` will effectively now reference separate module URL specifiers despite referring to the same file path which might lead to unexpected identity issues. In turn this might affect scope lookups for import maps as well.

There are also xisting examples of `new URL('file:///' + path.resolve(path))` as well to get cross-platform path resolution which will now similarly return a non unique URL.

Are these properties hard constraints on the change here? The alternative in the Node.js modules system might be to throw for these `file:///////path` return cases in the resolver and hope that isn't too much of a breaking change. We are discussing it at the meeting on Wednesday so I can report back further here, but any thoughts on the above would help to hear before then too.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/544#issuecomment-703639743