colon in filename oddity?

[bmeck]

colons appear to make files never able to be found?

// a.mjs
import './colons%3Awork'
import './colons:work'

// colons:work.js
// this space left blank

[bmeck]

might look into using require('url').URL if possible.

[jdalton]

What is the expected behavior for both './colons&3awork' and './colons:work'

[bmeck]

in URL resolution they are just colons since ./ kicks it to pathname bit.

[bmeck]

oh. yes, both should work. forgot to actually state that.

[jdalton]

Would it be possible for you to show a vanilla WHATWG URL usage that produces a decoded file:// protocol path containing a ":".

[bmeck]

new URL('file://localhost/test:123')
new URL('./test:123', 'file:///')

[jdalton]

and the &3a encoded one...

[bmeck]

sleepy typo, should use %

new URL('file://localhost/test%3A123')
new URL('./%3A', 'file:///')

When canonicalized in https://github.com/nodejs/node/blob/master/lib/internal/url.js#L1370 it becomes :

[jdalton]

Ah 👌,

I was super confused, thinking maybe there was another form of escapes besides percent 😋

What form of decode do you do? I noticed that decodeURI doesn't decode %3a.
Is it more the old school unescape() or decodeURIComponent()?

[bmeck]

That function does things in very specific ordering, but uses decodeURIComponent for the split up chunks it makes.

[jdalton]

Closed by 3b0244a.
I'll be adding a round of unit tests over the next couple of days to solidify support.