build: Update swc_core to v58.0.1

[kdy1]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a973d8c

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]

PR Review: build: Update swc_core to v58.0.1

This is a routine dependency update PR that upgrades swc_core from v57.0.0 to v58.0.1 along with all related SWC crates. The changes are mechanical and well-structured. A few observations below.

---

Summary of Changes

• swc_core: 57.0.0 → 58.0.1
• Multiple SWC crates bumped (all major/minor version increments): swc_common, swc_ecma_ast, swc_ecma_codegen, swc_ecma_parser, swc_ecma_transforms, swc_css_*, etc.
• New transitive dependency: swc_sourcemap 10.0.2 (pulled in by updated swc_common/swc_config)
• All plugin crate and npm package versions bumped with changelogs updated

---

Observations

1. Dual swc_sourcemap versions in dependency tree

The updated SWC core crates (swc_common 19.0.0, swc_config 4.0.0, swc_ecma_transforms_testing 42.0.0) now pull in swc_sourcemap 10.0.2 as a transitive dependency. However, the workspace-level pin in Cargo.toml remains at:

swc_sourcemap = "9.3.0"

This means the build will include two versions of swc_sourcemap simultaneously:

• 9.3.4 — used directly by swc_emotion (via { workspace = true })
• 10.0.2 — used transitively by swc_common, swc_config, and swc_ecma_transforms_testing

Since swc_emotion also depends on swc_common, any code path that threads swc_sourcemap types between the two could hit type-mismatch compilation errors. If the current build is passing CI, the types are likely not interleaved. That said, it's worth considering whether the workspace should be updated to 10.0.2 to unify the dependency tree and reduce WASM binary size, particularly for a plugin ecosystem where output size matters.

2. swc_config major version bump (3.1.2 → 4.0.0)

swc_config received a major version bump. Since plugins consume this transitively through swc_core, they're shielded from the raw API — but it's worth confirming whether any custom config handling in the plugins is affected.

3. PR is still in DRAFT

Since this is marked as DRAFT, CI results and any final adjustments may still be pending. The automated release commits (RELEASING: Releasing 18 package(s), Merge CHANGELOG into README) are already included, which is consistent with the repo's changeset-driven release workflow.

---

What's Done Well

• Version bumps are consistent across Cargo.toml, Cargo.lock, all Cargo.toml crate manifests, and package.json files
• CHANGELOGs and READMEs are updated for every package
• The changeset entry accurately describes the change
• No functional/logic code changes — purely a dependency update, which reduces review risk

---

Suggestion

Consider updating the workspace swc_sourcemap to 10.0.2 to consolidate to a single version and avoid carrying duplicate copies of the crate in the compiled WASM artifacts:

# Cargo.toml
swc_sourcemap = "10.0.2"

This would also require verifying that the public API changes in swc_sourcemap 10.x are compatible with how swc_emotion uses it.