-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(ssr): format ssrTransform
parse error
#18644
Merged
sapphi-red
merged 10 commits into
vitejs:main
from
hi-ogawa:fix-format-ssr-transform-parse-error
Nov 14, 2024
Merged
Changes from 4 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
71ec17c
fix(ssr): format ssrTransform parse error
hi-ogawa a8c7905
test: add test
hi-ogawa 5d30090
chore: replace test
hi-ogawa fb6ab11
fix: err.id too
hi-ogawa 77ca432
chore: tweak message
hi-ogawa fce167f
fix: err.pos might be missing
hi-ogawa 514a0de
chore: tweak
hi-ogawa 2bc211a
chore: typo
hi-ogawa e33f473
chore: f
hi-ogawa 42eec0c
chore: f
hi-ogawa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should keep the error message (
Parse failure:
...) so thatconsole.log(err)
shows the position and contents (#5192, #12060).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know when
err.loc
exsits (when it passes the previous code path) though.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, it looks better to keep
Parse failure: ...
for clarity. I remembered esbuild transform error also includes location details in its message (cf. #18626).Probably
loc
check was for acorn based parser error, so it's no longer relevant. Since Rollup 4, it now only hascode, message, pos
properties https://github.com/rollup/rollup/blob/42e587e0e37bc0661aa39fe7ad6f1d7fd33f825c/src/utils/bufferToAst.ts#L20-L22, so we only need to target these. It looks likepos
is missing on rust side panic, so I covered that case too.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for checking! That makes sense.