You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure this is a bug report, but I thought it worth mentioning that I've encountered this issue. It might make sense to call out in the README.
I hit this in my work on cspotcode/node-source-map-support#38 source-map-support did not handle conversion between spaces and %20 correctly. Sometimes it would output a file:///path/to/file with spaces.ts instead of file%20with...
I'm improving the test coverage and will now ensure that file URLs are percent-encoded and paths are not. I'm doing this with some normalization steps before calling resolve-uri. It's ambiguous for relative stuff, since we can't know if it's a relative path or a relative URI, so we don't know if the filename has the three-character sequence %20 or if it has a filename. But at least we can differentiate absolute paths from absolute file URIs
The text was updated successfully, but these errors were encountered:
I'm not sure this is a bug report, but I thought it worth mentioning that I've encountered this issue. It might make sense to call out in the README.
I hit this in my work on cspotcode/node-source-map-support#38 source-map-support did not handle conversion between spaces and
%20
correctly. Sometimes it would output afile:///path/to/file with spaces.ts
instead offile%20with
...I'm improving the test coverage and will now ensure that file URLs are percent-encoded and paths are not. I'm doing this with some normalization steps before calling resolve-uri. It's ambiguous for relative stuff, since we can't know if it's a relative path or a relative URI, so we don't know if the filename has the three-character sequence
%20
or if it has a filename. But at least we can differentiate absolute paths from absolute file URIsThe text was updated successfully, but these errors were encountered: