swc-project/swc - CodSpeed

swc

Blog Docs Changelog

Performance History

Latest Results

fix(flow): avoid restoring esm context for type-only module decls

oblador:flow-strip-type-only-export

9 hours ago

fix(ts): address flow pragma strip review feedback

oblador:strip-flow-pragma

9 hours ago

fix(es/transforms): strip `@flow` and `@noflow` pragma comments when transforming Flow syntax

oblador:strip-flow-pragma

13 hours ago

fix(es/transforms/typescript): Omit empty `export {}` when flow module has only type exports

oblador:flow-strip-type-only-export

14 hours ago

fix(deploy): build package ts before Linux GNU binding tests (#11806) **Description:** This fixes the `test-linux-x64-gnu-binding` workflow path so the package under test builds its own TypeScript entrypoint before the Docker test step runs. The failing `Publish minifier@1.15.29-nightly-20260418.1 / Test bindings on Linux-x64-gnu - node@22` job from [run 24609515249](https://github.com/swc-project/swc/actions/runs/24609515249/job/71962047938) failed with: - `Error: Cannot find module '../index.js'` That happened because the job was running `yarn build:ts` from the workspace root, which only builds `packages/core`. For `@swc/minifier`, the test suite loads `packages/minifier/index.js`, so the GNU binding test never generated the entrypoint it needed. This change makes the GNU binding test mirror the package-scoped TypeScript build already used by the other binding jobs by running `yarn build:ts` in `./packages/${{ inputs.package }}`. Validation used: - inspected the failing Actions log and confirmed the missing `../index.js` error - `git submodule update --init --recursive` - `corepack enable && yarn install --mode=skip-build` - `(cd packages/minifier && yarn build:ts)` - `cargo fmt --all` - `cargo clippy --all --all-targets -- -D warnings` - `(cd packages/minifier && yarn build:dev && yarn test)`

main

1 day ago

fix(deploy): build package ts before linux gnu binding tests

kdy1:kdy1/fix-linux-gnu-binding-tests

1 day ago

fix(deploy): Fix musl binding test workflow (#11804) **Description:** This updates the `test-linux-x64-musl-binding` job in `publish-npm-package.yml` so the musl binding tests only do the work they actually need. It fixes two failure modes seen in the `Publish 1.15.28` workflow: - `node@20` failed during dependency installation because `yarn install` ran unnecessary build scripts and hit a flaky `dprint` postinstall download (`504 Gateway Time-out`) - `node@22` failed during test execution because the workflow built TypeScript from the workspace root, which only generated `packages/core` outputs and left `packages/minifier/index.js` missing The workflow change now: - uses `yarn install --mode=skip-build` in the musl test job to avoid unrelated lifecycle scripts during setup - runs `yarn build:ts` inside `./packages/${{ inputs.package }}` so the package under test gets its own generated JS entrypoint before the docker test step This keeps the fix scoped to the failing musl binding test path without changing the other binding jobs. Validation used: - disposable clone with `yarn config set supportedArchitectures.libc musl` - `yarn install --mode=skip-build` - package-level `yarn build:ts` for `minifier`, `core`, and `html` - `cargo fmt --all` - `git submodule update --init --recursive` - `cargo clippy --all --all-targets -- -D warnings` **BREAKING CHANGE:** None. **Related issue (if exists):** None.

main

1 day ago

perf(parser): trim ts speculative parse hot path

kdy1:kdy1/ts-speculative-parse-hot-path

1 day ago

Latest Branches

0%

Omit empty `export {}` when flow module has only type exports#11809

9 hours ago

09df75d

oblador:flow-strip-type-only-export

0%

fix(es/transforms): strip `@flow` and `@noflow` pragma comments#11810

9 hours ago

fad0bb3

oblador:strip-flow-pragma

0%

fix(deploy): build package ts before Linux GNU binding tests#11806

1 day ago

9f3b61b

kdy1:kdy1/fix-linux-gnu-binding-tests

© 2026 CodSpeed Technology

Home Terms Privacy Docs