-
Notifications
You must be signed in to change notification settings - Fork 469
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
chore: bump swc #1587
chore: bump swc #1587
Conversation
🦋 Changeset detectedLatest commit: 847c4e6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 15 packages
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 |
!bench |
@@ -29,7 +29,7 @@ nav a { | |||
border-radius: 10px; | |||
} | |||
.foo:before { | |||
content: "\e0c6"; | |||
content: ""; |
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.
This diff is due to swc version upgrade
Benchmark Results
|
@@ -41,7 +41,7 @@ try { | |||
error_count += 1; |
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.
The diff is because of this pr swc-project/swc#6670
48f7c1d
to
fd09e27
Compare
@@ -12,9 +11,9 @@ expression: should_not_replace_values_with_an_uppercase_P_or_X.css | |||
|
|||
# Actual | |||
.rule { | |||
margin: 0.75rem calc(100% - 14PX); |
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.
This diff is controversial, and I filed an issue here #1590
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.
Is only the problem blocking us to bump version of SWC?
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 think this is an issue that blocking us to bump swc.
!bench |
Benchmark Results
|
fd09e27
to
5e2620f
Compare
Could you bump |
5e2620f
to
e86f956
Compare
please add background about why we bump swc |
Done |
Summary
Backgrounds
import.meta
should not throw error usingparse_file_as_expr
swc-project/swc#6783Test Plan
Related issue (if exists)
How does Webpack handle this? (if exists)
Is this a workaround for the Webpack's implementation?
Further reading