build: Update swc_core to v74.0.0

[kdy1]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 90ebd5c

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​swc_ecma_transforms_base@​45.0.0 ⏵ 46.0.0	-12		-7
	cargo/​swc_core@​73.0.0 ⏵ 74.0.0
	cargo/​swc_ecma_visit@​25.0.0 ⏵ 26.0.0
	cargo/​swc_ecma_minifier@​57.0.1 ⏵ 58.0.0	+1
	cargo/​clap@​4.6.1 ⏵ 4.6.2
	cargo/​regex@​1.13.0 ⏵ 1.13.1
	cargo/​swc_ecma_ast@​25.0.0 ⏵ 26.0.0
	cargo/​swc_ecma_codegen@​28.0.2 ⏵ 29.0.0
	cargo/​swc_ecma_parser@​41.1.2 ⏵ 42.0.0
	cargo/​swc_ecma_transforms_testing@​49.0.0 ⏵ 50.0.0
	cargo/​swc_ecma_utils@​31.0.2 ⏵ 32.0.0
	cargo/​swc_plugin_proxy@​26.0.0 ⏵ 27.0.0
	cargo/​testing@​24.0.1 ⏵ 25.0.0
	cargo/​swc_css_ast@​23.0.0 ⏵ 24.0.0			+1
	cargo/​swc_css_codegen@​23.0.0 ⏵ 24.0.0			+1
	cargo/​swc_css_compat@​23.0.0 ⏵ 24.0.0			+1
	cargo/​swc_css_minifier@​23.0.0 ⏵ 24.0.0			+1
	cargo/​swc_css_parser@​23.0.0 ⏵ 24.0.0			+1
	cargo/​swc_css_visit@​23.0.0 ⏵ 24.0.0			+1
	cargo/​swc_ecma_transforms@​58.0.0 ⏵ 59.0.0			+1
	cargo/​swc_ecma_transforms_react@​51.0.0 ⏵ 52.0.0			+1
	cargo/​swc_common@​23.0.2 ⏵ 24.0.0
	cargo/​swc_atoms@​9.0.3 ⏵ 10.0.0
	cargo/​swc_css_prefixer@​28.0.0 ⏵ 29.0.0

View full report

[claude]

PR Review — build: Update swc_core to v74.0.0

Thanks for keeping the plugins in sync with core. This is a mechanical dependency bump and looks clean overall. A few notes:

✅ Looks good

• Workspace Cargo.toml versions bumped consistently (swc_core 73→74, swc_atoms 9→10, swc_common 23→24, the swc_css_* / swc_ecma_* families, testing, etc.), and Cargo.lock was regenerated — verified swc_core = 74.0.0 and swc_atoms = 10.0.0 resolved in the lockfile.
• Per-package version / package.json / CHANGELOG.md bumps and changeset entries are present and consistent across all 20+ plugins.
• No .rs changes needed, which is a good signal that v74 is source-compatible for these transforms.

🔎 Points worth confirming / minor nits

1. scripts/bump-crates.sh — generate-lockfile runs after the commit.

   cargo mono bump $@
   git commit -a -m "Bump crates" || true
   
   cargo generate-lockfile

   cargo generate-lockfile runs after git commit -a, so any Cargo.lock changes it produces are left uncommitted by the script. If the intent is for the regenerated lockfile to land in the bump commit, move generate-lockfile before the commit (and let -a pick it up), e.g.:

   cargo mono bump $@
   cargo generate-lockfile
   git commit -a -m "Bump crates" || true

   Otherwise the lockfile has to be committed as a separate manual step (which is presumably what happened for this PR).

2. Missing trailing newline in scripts/bump-crates.sh (\ No newline at end of file). Minor, but worth adding one to keep POSIX-friendly / avoid lint noise.

3. Major core bump = host ABI expectations. Since swc_core had a major bump (73→74), the compiled .wasm plugins will require a host swc/@swc/core runtime compatible with the v74 plugin ABI. The package versions are bumped only as minor — worth double-checking that's the intended semver signal for consumers, given plugin/host version mismatches are a common source of runtime errors for users.

4. CI is the real gate here. With a major core bump and no code changes, the confidence comes entirely from the build + snapshot tests passing. Please make sure the full workspace cargo build/test and the plugin snapshot suites are green before merging.

Nothing blocking from a code-quality standpoint — items #1 and #2 are the only concrete fix suggestions, and both are in the bump script rather than the shipped plugins.