build: Update swc_core to v65.0.0

[kdy1]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ddf6a45

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[claude]

Code Review: build: Update swc_core to v65.0.0

Overview

This PR performs a routine dependency upgrade of swc_core from v63.1.0 to v65.0.0 (skipping v64), along with cascading bumps across all dependent crates and npm packages. It also bundles the previously staged emotion keyframes auto-label regression fix (from the deleted changeset mean-bulldogs-pretend.md) into this release.

---

What's Changed

• swc_core: 63.1.0 → 65.0.0
• All downstream swc_* crates (parser, codegen, transforms, minifier, etc.) updated in lockstep
• 16 internal plugin crates bumped one major version (e.g., 3.0.0 → 4.0.0)
• 18 npm packages bumped from x.8.0 → x.9.0 (minor)
• Emotion keyframes fix correctly folded into the @swc/plugin-emotion@14.9.0 changelog entry

---

Observations

Cargo.lock is out of sync with internal crate versions

Every local path crate shows a version discrepancy between the Cargo.toml and Cargo.lock. For example:

Crate	Cargo.toml (new)	Cargo.lock (new)
modularize_imports	4.0.0	3.0.0
swc_icu_messageformat_parser	23.0.0	22.0.0
swc_emotion	4.0.0	3.0.0
swc_formatjs_transform	27.0.0	26.0.0
... (all 16 crates)

The lock file consistently reflects versions that are one step behind the Cargo.toml declarations after the version bumps. This suggests the version bump commit (chore(release): bump 16 crate(s)) updated Cargo.toml files but did not regenerate the lock file. While this doesn't break path-based local builds (Cargo resolves path deps by path, not version), it means the published lock file doesn't accurately represent the workspace state and could cause confusion for contributors.

Question: Why was swc_core v64 skipped?

The bump goes directly from 63.1.0 → 65.0.0. The PR body is empty, so there's no explanation. Was v64 a bad release? It would be helpful to note this in the PR description, even briefly.

swc_ecma_minifier major version jump

The minifier goes from 51.1.0 → 52.0.1, which is a major bump. Since plugins consume this transitively through swc_core, this is likely fine — but it's worth confirming that no plugin directly references minifier APIs that may have changed.

---

Positives

• Version bump pattern is completely consistent across all 18 packages — no packages missed.
• The bundled emotion fix is correctly reflected in the CHANGELOG with both the minor (core update) and patch (keyframes fix) entries.
• The changeset file is properly cleaned up after being merged into the CHANGELOG.
• No logic changes — purely a dependency update, so behavioral risk is low.

---

Suggestions

1. Regenerate Cargo.lock after the internal crate version bumps to keep it in sync. Running cargo generate-lockfile or cargo check from the workspace root after bumping versions should resolve this.
2. Add a brief PR description noting why v64 was skipped (if intentional) so future bisectors understand the jump.

---

Overall this is a clean, well-structured release PR following the established conventions of this repo. The Cargo.lock discrepancy is the main technical issue worth addressing before merge.