Skip to content
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

Merged
merged 9 commits into from
Jan 11, 2023
Merged

chore: bump swc #1587

merged 9 commits into from
Jan 11, 2023

Conversation

IWANABETHATGUY
Copy link
Contributor

@IWANABETHATGUY IWANABETHATGUY commented Jan 10, 2023

Summary

Backgrounds

Test Plan

Related issue (if exists)

How does Webpack handle this? (if exists)

Is this a workaround for the Webpack's implementation?

Check if Webpack has the same feature and but we're taking a workaround for it.

  • Yes. Issue for resolving the workaround:
  • No

Further reading

@changeset-bot
Copy link

changeset-bot bot commented Jan 10, 2023

🦋 Changeset detected

Latest commit: 847c4e6

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

This PR includes changesets to release 15 packages
Name Type
@rspack/binding Patch
@rspack/postcss-loader Patch
@rspack/core Patch
@rspack/cli Patch
@rspack/dev-middleware Patch
@rspack/dev-server Patch
@rspack/plugin-html Patch
@rspack/less-loader Patch
@rspack/dev-client Patch
@rspack/plugin-minify Patch
@rspack/plugin-node-polyfill Patch
@rspack/binding-darwin-arm64 Patch
@rspack/binding-darwin-x64 Patch
@rspack/binding-linux-x64-gnu Patch
@rspack/binding-win32-x64-msvc Patch

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

@IWANABETHATGUY IWANABETHATGUY changed the title chore: 🤖 init chore: bump swc Jan 10, 2023
@IWANABETHATGUY
Copy link
Contributor Author

!bench

@@ -29,7 +29,7 @@ nav a {
border-radius: 10px;
}
.foo:before {
content: "\e0c6";
content: "";
Copy link
Contributor Author

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

@github-actions
Copy link
Contributor

Benchmark Results

group                                                 baseline                               pr
-----                                                 --------                               --
criterion_benchmark/css_heavy                         1.00     54.5±3.29ms        ? ?/sec    1.06     57.5±3.70ms        ? ?/sec
criterion_benchmark/lodash                            1.00     75.6±1.47ms        ? ?/sec    1.02     76.9±1.42ms        ? ?/sec
criterion_benchmark/ten_copy_of_threejs               1.00   800.8±12.20ms        ? ?/sec    1.00   803.9±13.78ms        ? ?/sec
high_cost_benchmark/ten_copy_of_threejs_production    1.00       5.3±0.02s        ? ?/sec    1.02       5.4±0.02s        ? ?/sec

@@ -41,7 +41,7 @@ try {
error_count += 1;
Copy link
Contributor Author

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

@IWANABETHATGUY IWANABETHATGUY changed the title chore: bump swc WIP: chore: bump swc Jan 10, 2023
@@ -12,9 +11,9 @@ expression: should_not_replace_values_with_an_uppercase_P_or_X.css

# Actual
.rule {
margin: 0.75rem calc(100% - 14PX);
Copy link
Contributor Author

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

Copy link
Collaborator

@hyf0 hyf0 Jan 10, 2023

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?

Copy link
Contributor Author

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.

@IWANABETHATGUY
Copy link
Contributor Author

!bench

@github-actions
Copy link
Contributor

Benchmark Results

group                                                 baseline                               pr
-----                                                 --------                               --
criterion_benchmark/css_heavy                         1.00     54.2±3.48ms        ? ?/sec    1.09     59.3±3.64ms        ? ?/sec
criterion_benchmark/lodash                            1.00     72.0±1.27ms        ? ?/sec    1.04     74.6±1.34ms        ? ?/sec
criterion_benchmark/ten_copy_of_threejs               1.00    765.5±9.38ms        ? ?/sec    1.03    789.7±9.80ms        ? ?/sec
high_cost_benchmark/ten_copy_of_threejs_production    1.00       4.7±0.03s        ? ?/sec    1.06       4.9±0.02s        ? ?/sec

@hyf0
Copy link
Collaborator

hyf0 commented Jan 11, 2023

Could you bump swc_core to 0.55.2
There's a bug need to fixed with swc-project/swc#6783

@hyf0 hyf0 merged commit cd77363 into main Jan 11, 2023
@hyf0 hyf0 deleted the chore/bump-swc branch January 11, 2023 06:27
@hardfist
Copy link
Contributor

please add background about why we bump swc

@hyf0
Copy link
Collaborator

hyf0 commented Jan 11, 2023

please add background about why we bump swc

Done

@hyf0 hyf0 changed the title WIP: chore: bump swc chore: bump swc Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants