fix(register/esm): pass file urls as paths #840
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
compile() expects a filename, not a url: it passes the value directly to the bindings module, which immediately parses it as a `Path` unconditionally. This causes input file source maps to fail to load, as it attempts to find the URL as if it were a file on disk. (see swc-project/swc#9422) This is a targeted fix which hopefully minimizes the chance of things breaking.
kdy1
pushed a commit
to swc-project/swc
that referenced
this pull request
Aug 14, 2024
**Description:**
Parse based on the provided prefix: inline urls must start with "data:",
so only trying one will ensure the correct and more helpful error
message will be shown.
Currently, any error while trying to load a sourcemap file will give the
unhelpful error:
```
ERROR failed to read input source map: failed to parse inline source map url
index.js.map
Caused by:
relative URL without a base
at <snip>/swc-<ver>/src/lib.rs:386
```
Further, for the common "missing file" error, give a better message that
hopefully describes the two paths tried, rather than increasing
confusion by talking about a `.js.map.map` file if it was correct.
Now it will show, for example:
```
ERROR failed to read input source map: failed to find input source map file "index.js.map" in "file:///D:/github/skilitics/billing/api-client/lib/services/index.js" file as either "file:///D:/github/skilitics/billing/api-client/lib/services\\index.js.map" or with appended .map
at D:\github\swc-project\swc\crates\swc\src\lib.rs:400
```
(This example appears to be an issue in swc-node, where it is passing a
file URL which is treated as a path, and therefore never exists, I'm
working on a PR for there too)
There are more improvements that could make this code clearer and more
reliable, but this should resolve many of the confused users (including
me!)
**Related issue:**
See (maybe can be considered to fix): #8944, #8910
[PR in swc-node to fix the originating
issue](swc-project/swc-node#840)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
compile() expects a filename, not a url: it passes the value directly to the bindings module, which immediately parses it as a
Pathunconditionally.This causes input file source maps to fail to load, as it attempts to find the URL as if it were a file on disk. (see swc-project/swc#9422)
This is a targeted fix which hopefully minimizes the chance of things breaking.