Skip to content

fix(es/parser): Do not parse empty stmt after using decl #9798

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

Merged
merged 2 commits into from
Dec 15, 2024

Conversation

dsherret
Copy link
Contributor

Description:

See test output. It was parsing an empty statement after a using declaration.

Related issue (if exists): None

@dsherret dsherret requested a review from a team as a code owner December 14, 2024 17:52
Copy link

changeset-bot bot commented Dec 14, 2024

🦋 Changeset detected

Latest commit: 06d9caa

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

codspeed-hq bot commented Dec 14, 2024

CodSpeed Performance Report

Merging #9798 will not alter performance

Comparing dsherret:fix_do_not_parse_empty_stmt (06d9caa) with main (e04c7b3)

Summary

✅ 194 untouched benchmarks

@kdy1 kdy1 requested a review from a team as a code owner December 15, 2024 03:05
@kdy1 kdy1 added this to the Planned milestone Dec 15, 2024
@kdy1 kdy1 merged commit c2696db into swc-project:main Dec 15, 2024
20 of 22 checks passed
@kdy1 kdy1 modified the milestones: Planned, v1.10.2 Dec 26, 2024
kdy1 added a commit that referenced this pull request Dec 27, 2024
@swc-project swc-project locked as resolved and limited conversation to collaborators Jan 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants