build: Update swc_core to v57.0.0

[kdy1]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c09dde7

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]

Pull Request Review: Update swc_core to v57.0.0

Overview

This PR updates the core SWC dependency from v56.0.0 to v57.0.0 across all plugins in the monorepo. This is a dependency update that involves bumping versions across 68 files including Cargo manifests, lockfiles, package.json files, and changelogs.

Code Quality and Best Practices ✅

Positive observations:

• Clean and consistent version bumping across all packages
• Proper use of changesets for version management (deleted .changeset/little-cherries-compete.md after processing)
• All CHANGELOG.md and README.md files properly updated with the new version and release notes
• Package versions follow semantic versioning correctly (minor version bumps)
• Consistent commit message style following conventional commits

Structural Analysis ✅

Changes include:

1. Core dependency update: swc_core 56.0.0 → 57.0.0

2. Related dependency updates:

   • swc_ecma_minifier: 44.0.0 → 45.0.0
   • swc_ecma_parser: 33.0.1 → 34.0.0
   • swc_ecma_transforms: 46.0.0 → 47.0.0
   • swc_ecma_transforms_base: 36.0.1 → 37.0.0
   • swc_ecma_transforms_react: 40.0.0 → 41.0.0
   • swc_ecma_transforms_testing: 40.0.0 → 41.0.0
   • swc_ecma_quote_macros: 33.0.0 → 34.0.0
   • swc_ecma_transforms_optimization: 38.0.0 → 39.0.0

3. Package version bumps: All 18 plugins properly versioned with minor version bumps

Potential Issues ⚠️

Minor concerns:

1. No breaking change documentation: While this appears to be a minor version bump, updating the core compiler from v56 to v57 could introduce behavioral changes. Consider documenting:

   • What changed in swc_core v57?
   • Are there any API changes that plugin authors should be aware of?
   • Link to swc_core release notes/changelog

2. Test coverage: The PR description doesn't mention:

   • Whether existing tests pass
   • If any test updates were needed for the new version
   • Manual testing performed

Security Concerns ✅

No security concerns identified. This is a straightforward dependency update from the upstream SWC project.

Performance Considerations ✅

No performance concerns at the PR level. Performance characteristics will depend on what changed in swc_core v57, but that's an upstream concern.

Test Coverage ⚠️

Observations:

• CI checks are currently pending/running
• No test file changes in this PR (which is expected for a dependency update)
• Integration tests should validate that all plugins still work correctly with the new core version

Recommendation: Wait for CI to complete successfully before merging, especially:

• Integration Test (macos-latest)
• Integration Test (ubuntu-latest)
• Test - ubuntu-latest
• Test - windows-latest

Recommendations

Before Merging:

1. ✅ Wait for CI: Ensure all tests pass on all platforms
2. 📝 Consider adding context: Add a note about what's new in swc_core v57 (link to release notes or changelog)
3. 🔍 Verify compatibility: Confirm no breaking changes affect plugin APIs

Nice to have:

• Link to the swc_core v57 release notes in the PR description for future reference
• Document any migration steps if there are breaking changes (though this appears to be a clean update)

Summary

This is a well-executed dependency update PR that follows good practices:

• ✅ Consistent version management
• ✅ Proper changelog updates
• ✅ Clean changeset processing
• ✅ Follows conventional commits
• ⚠️ Pending CI validation

The PR structure is excellent and follows the repository's conventions. The main recommendation is to ensure all CI checks pass before merging and consider adding release note references for documentation purposes.

Overall: Looks good! Just wait for CI to complete. 🚀

---

Review generated by Claude Code