Replacing `rollup` and `esbuild` with `rolldown` #3054

RobinTail · 2025-11-10T07:17:32Z

Includes:

Replacing tsx with unrun #3051
Override vite to rolldown-vite #3053
overriding vite to its v8

Summary by CodeRabbit

Chores
- Switched project tooling from TSX to Unrun across scripts and dev dependencies; updated workspace configuration and dependency overrides.
Tests
- Updated test runtimes to use the new runner; minor test expectation formatting tweak with no behavioral impact.

coderabbitai · 2025-11-10T07:17:41Z

📝 Walkthrough

Walkthrough

Replaced tsx with unrun across CI, package scripts, examples, and tests; updated root devDependencies and pnpm workspace overrides/exclusions; adjusted one test expectation formatting.

Changes

Cohort / File(s)	Summary
CI / Workflow `/.github/workflows/headers.yml`	Invocation changed from `pnpm tsx tools/headers.ts` → `pnpm unrun tools/headers.ts`.
Test specs `compat-test/quick-start.spec.ts`, `esm-test/quick-start.spec.ts`, `example/index.spec.ts`	Switched spawned runtime from `tsx` → `unrun` when executing example/test scripts.
Example package `example/package.json`	Scripts `start`, `build:docs`, `build:client` changed from `tsx ...` → `unrun ...`.
Root package `package.json`	`prebuild`/`pretest` scripts updated to use `unrun`; removed `tsx` devDependency; added `unrun@^0.2.17`.
Workspace config `pnpm-workspace.yaml`	Removed `esbuild` from `onlyBuiltDependencies`; removed `tsx` from `minimumReleaseAgeExclude`; added overrides for `lightningcss` and `vite`.
Test expectation `express-zod-api/tests/common-helpers.spec.ts`	Adjusted expected function string formatting from multi-line `() => {\n }` to single-line `() => {}`.

Sequence Diagram(s)

(skipped)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Well known headers in typescript file #3014 — touches tools/headers.ts, which this PR now invokes via unrun.
Upgrading dependencies #3161 — overlaps in removing/changing tsx devDependency and related scripts.
Upgrading tsdown #3033 — related workspace and dependency/script adjustments involving unrun/tsx.

Suggested labels

refactoring, external bug

Poem

🐇 I hopped from tsx to unrun with cheer,
Swapped scripts and CI, made the path clear.
One test line tidied, workspace leaves blown,
I nibble a carrot and then I am gone. 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title claims to replace 'rollup' and 'esbuild' with 'rolldown', but the actual changes show migration from 'tsx' to 'unrun' for script execution and dependency updates unrelated to rolldown.	Update the PR title to accurately reflect the primary changes, such as 'Replace tsx with unrun for script execution' or provide context showing how rolldown integration relates to the tsx/unrun changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch exp-no-esbuild

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coveralls-official · 2025-11-10T07:37:34Z

coverage: 100.0%. remained the same
when pulling 8ae01bc on exp-no-esbuild
into eb875ef on master.

coveralls-official · 2025-11-10T07:37:37Z

coverage: 100.0%. remained the same
when pulling dd05042 on exp-no-esbuild
into c6ba0da on master.

.github/workflows/node.js.yml

Does not work well for `unrun`, causes unclear crashes and resolution uncertainty over `ramda` in #3054  ## Summary by CodeRabbit * **Chores** * Updated module import paths and TypeScript compilation configuration for improved build compatibility. * Standardized JSON module import syntax across the codebase. * Enhanced internal API infrastructure with extended interface support for advanced use cases. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub>

Copy of #3055 , because the issue in #3054 is not caused by it

Since `tsdown` is going to keep it anyway, it can replace `tsx`

Should go along with #3051 All that will help to get rid of `esbuild` and use faster approach based on Rust.

RobinTail · 2025-11-22T19:04:42Z

unrun after certain update is failing to import ramda and it's causing failure

Filed an issue to unrun:
Gugustinette/unrun#11

# Conflicts: # cjs-test/quick-start.spec.ts # pnpm-lock.yaml

# Conflicts: # package.json # pnpm-lock.yaml # pnpm-workspace.yaml

RobinTail · 2025-11-29T09:27:34Z

The experiment is a success.
I'm going to wait vite to stabilize on migrating to rolldown

# Conflicts: # pnpm-lock.yaml

pnpm-lock.yaml

# Conflicts: # pnpm-lock.yaml

RobinTail

✅ Looking good

coderabbitai

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5df6352 and c53b3f9.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

pnpm-workspace.yaml (1 hunks)

🧰 Additional context used

🧠 Learnings (8)

📓 Common learnings

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2697
File: CHANGELOG.md:5-5
Timestamp: 2025-06-02T21:11:20.768Z
Learning: In the express-zod-api repository, RobinTail follows a release workflow where package.json version is only updated on the master branch after merging all planned release changes. Changelog entries may show future version numbers while package.json remains at the previous version during feature development, and this is intentional workflow, not a version inconsistency that needs to be flagged.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 0
File: :0-0
Timestamp: 2025-10-02T17:42:48.840Z
Learning: In express-zod-api v25 (ESM-only), the `.example()` method error occurs when user code runs as CommonJS. Express Zod API patches Zod's ESM bundle with `.example()`, but CommonJS code requires a separate CJS bundle instance that lacks this patch. Users must run their code as ESM by: (1) setting `"type": "module"` in package.json, (2) using `.mts` or `.mjs` file extensions, or (3) using tools like `tsx` or `vite-node` that provide their own ESM-compatible compilation.

📚 Learning: 2025-05-28T19:19:27.727Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 0
File: :0-0
Timestamp: 2025-05-28T19:19:27.727Z
Learning: In pnpm workspaces, most configuration can now be done directly in pnpm-workspace.yaml using the `settings` section instead of requiring .npmrc files. This includes workspace linking, dependency resolution, and performance settings.

Applied to files:

pnpm-workspace.yaml

📚 Learning: 2025-09-29T06:00:16.488Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2974
File: express-zod-api/src/documentation-helpers.ts:48-48
Timestamp: 2025-09-29T06:00:16.488Z
Learning: In the express-zod-api repository, the project uses pnpm workspaces with autoInstallPeers: false, meaning peerDependencies are not installed. The actual TypeScript version used for development comes from devDependencies which references "catalog:dev" in pnpm-workspace.yaml where it's set to a recent version (^5.9.2), not the peerDependency version which is just the minimum consumer requirement.

Applied to files:

pnpm-workspace.yaml

📚 Learning: 2025-06-02T21:08:56.475Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2697
File: CHANGELOG.md:5-5
Timestamp: 2025-06-02T21:08:56.475Z
Learning: The `cjs-test` directory in the express-zod-api repository is a test workspace and should be excluded when checking for main project version consistency with changelog entries.

Applied to files:

pnpm-workspace.yaml

📚 Learning: 2025-05-27T19:35:57.357Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2546
File: express-zod-api/tests/buffer-schema.spec.ts:32-37
Timestamp: 2025-05-27T19:35:57.357Z
Learning: In the express-zod-api project, tests are run from the `express-zod-api` workspace directory, and the project uses an ESM-first environment without `__dirname`. Relative paths like `../logo.svg` in test files correctly resolve to the repository root due to this test execution context.

Applied to files:

pnpm-workspace.yaml

📚 Learning: 2025-05-27T19:30:51.885Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2546
File: compat-test/sample.ts:1-1
Timestamp: 2025-05-27T19:30:51.885Z
Learning: Files in compat-test/ directories, especially those named sample.ts or similar, are often test fixtures for migration scripts and may intentionally contain deprecated or "incorrect" code that the migration tooling is designed to fix. These should not be flagged as issues.

Applied to files:

pnpm-workspace.yaml

📚 Learning: 2025-10-02T17:42:48.840Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 0
File: :0-0
Timestamp: 2025-10-02T17:42:48.840Z
Learning: In express-zod-api v25 (ESM-only), the `.example()` method error occurs when user code runs as CommonJS. Express Zod API patches Zod's ESM bundle with `.example()`, but CommonJS code requires a separate CJS bundle instance that lacks this patch. Users must run their code as ESM by: (1) setting `"type": "module"` in package.json, (2) using `.mts` or `.mjs` file extensions, or (3) using tools like `tsx` or `vite-node` that provide their own ESM-compatible compilation.

Applied to files:

pnpm-workspace.yaml

📚 Learning: 2025-09-29T03:35:55.561Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 0
File: :0-0
Timestamp: 2025-09-29T03:35:55.561Z
Learning: In the express-zod-api repository, packages are built using tsdown before publishing. Source code with .ts extensions is not published - only the built JavaScript bundles and declaration files in the dist/ directory are published to npm. This means .ts extensions in source imports don't affect consumers.

Applied to files:

pnpm-workspace.yaml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

GitHub Check: build (24.x)

🔇 Additional comments (1)

pnpm-workspace.yaml (1)

67-67: No issues found. Verification confirms that lightningcss is not imported or directly used anywhere in the codebase. The package appears only as a transitive dependency (through unplugin-lightningcss), making the override to an empty package safe and intentional for the rolldown migration.

pnpm-workspace.yaml

# Conflicts: # pnpm-lock.yaml

# Conflicts: # package.json # pnpm-lock.yaml

coderabbitai

Actionable comments posted: 2

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9c6a5a7 and 7cbea0e.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

example/package.json
package.json
pnpm-workspace.yaml

🚧 Files skipped from review as they are similar to previous changes (2)

package.json
pnpm-workspace.yaml

🧰 Additional context used

🧠 Learnings (10)

📓 Common learnings

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 3054
File: pnpm-workspace.yaml:68-68
Timestamp: 2025-12-18T13:42:39.225Z
Learning: In the express-zod-api repository, Vite is overridden to v8 beta in pnpm-workspace.yaml specifically to ensure vitest (which depends on Vite) uses the same rolldown bundler as tsdown and unrun. This override is intentional for toolchain consistency, as Vite is only used for testing purposes (not production).

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2697
File: CHANGELOG.md:5-5
Timestamp: 2025-06-02T21:11:20.768Z
Learning: In the express-zod-api repository, RobinTail follows a release workflow where package.json version is only updated on the master branch after merging all planned release changes. Changelog entries may show future version numbers while package.json remains at the previous version during feature development, and this is intentional workflow, not a version inconsistency that needs to be flagged.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2546
File: express-zod-api/src/json-schema-helpers.ts:1-3
Timestamp: 2025-05-27T20:27:17.015Z
Learning: Ramda is correctly listed as a dependency in express-zod-api/package.json, so imports of ramda utilities are properly supported.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2546
File: express-zod-api/src/json-schema-helpers.ts:1-3
Timestamp: 2025-05-27T20:27:17.015Z
Learning: Ramda is correctly listed as a dependency in express-zod-api/package.json, so imports of ramda utilities are properly supported.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 0
File: :0-0
Timestamp: 2025-10-02T17:42:48.840Z
Learning: In express-zod-api v25 (ESM-only), the `.example()` method error occurs when user code runs as CommonJS. Express Zod API patches Zod's ESM bundle with `.example()`, but CommonJS code requires a separate CJS bundle instance that lacks this patch. Users must run their code as ESM by: (1) setting `"type": "module"` in package.json, (2) using `.mts` or `.mjs` file extensions, or (3) using tools like `tsx` or `vite-node` that provide their own ESM-compatible compilation.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2873
File: package.json:8-10
Timestamp: 2025-08-05T21:02:01.413Z
Learning: In pnpm workspaces, the `-r` (recursive) flag excludes the root workspace by default when running commands. Using `pnpm -r test` will execute test scripts only in child workspace packages, not in the root workspace, so it does not cause recursive execution issues.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2697
File: CHANGELOG.md:5-5
Timestamp: 2025-06-02T21:08:56.475Z
Learning: The `cjs-test` directory in the express-zod-api repository is a test workspace and should be excluded when checking for main project version consistency with changelog entries.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2974
File: express-zod-api/src/documentation-helpers.ts:48-48
Timestamp: 2025-09-29T06:00:16.488Z
Learning: In the express-zod-api repository, the project uses pnpm workspaces with autoInstallPeers: false, meaning peerDependencies are not installed. The actual TypeScript version used for development comes from devDependencies which references "catalog:dev" in pnpm-workspace.yaml where it's set to a recent version (^5.9.2), not the peerDependency version which is just the minimum consumer requirement.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2873
File: package.json:8-10
Timestamp: 2025-08-05T21:02:01.413Z
Learning: In pnpm workspaces, the `-r` (recursive) flag excludes the root workspace by default when running commands. Using `pnpm -r test` will execute test scripts only in child workspaces, not in the root workspace, so it does not cause recursive execution issues.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2546
File: express-zod-api/tests/buffer-schema.spec.ts:32-37
Timestamp: 2025-05-27T19:35:57.357Z
Learning: In the express-zod-api project, tests are run from the `express-zod-api` workspace directory, and the project uses an ESM-first environment without `__dirname`. Relative paths like `../logo.svg` in test files correctly resolve to the repository root due to this test execution context.

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 0
File: :0-0
Timestamp: 2025-09-29T03:35:55.561Z
Learning: In the express-zod-api repository, packages are built using tsdown before publishing. Source code with .ts extensions is not published - only the built JavaScript bundles and declaration files in the dist/ directory are published to npm. This means .ts extensions in source imports don't affect consumers.

📚 Learning: 2025-09-29T03:35:55.561Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 0
File: :0-0
Timestamp: 2025-09-29T03:35:55.561Z
Learning: In the express-zod-api repository, packages are built using tsdown before publishing. Source code with .ts extensions is not published - only the built JavaScript bundles and declaration files in the dist/ directory are published to npm. This means .ts extensions in source imports don't affect consumers.

Applied to files:

example/package.json

📚 Learning: 2025-10-02T17:42:48.840Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 0
File: :0-0
Timestamp: 2025-10-02T17:42:48.840Z
Learning: In express-zod-api v25 (ESM-only), the `.example()` method error occurs when user code runs as CommonJS. Express Zod API patches Zod's ESM bundle with `.example()`, but CommonJS code requires a separate CJS bundle instance that lacks this patch. Users must run their code as ESM by: (1) setting `"type": "module"` in package.json, (2) using `.mts` or `.mjs` file extensions, or (3) using tools like `tsx` or `vite-node` that provide their own ESM-compatible compilation.

Applied to files:

example/package.json

📚 Learning: 2025-09-29T06:00:16.488Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2974
File: express-zod-api/src/documentation-helpers.ts:48-48
Timestamp: 2025-09-29T06:00:16.488Z
Learning: In the express-zod-api repository, the project uses pnpm workspaces with autoInstallPeers: false, meaning peerDependencies are not installed. The actual TypeScript version used for development comes from devDependencies which references "catalog:dev" in pnpm-workspace.yaml where it's set to a recent version (^5.9.2), not the peerDependency version which is just the minimum consumer requirement.

Applied to files:

example/package.json

📚 Learning: 2025-05-27T20:03:34.213Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2546
File: example/factories.ts:35-42
Timestamp: 2025-05-27T20:03:34.213Z
Learning: The `./example` directory in the express-zod-api repository contains demonstration code for educational purposes only, not intended for production use. Example code can make simplified assumptions for brevity and clarity, and should not be flagged for missing production-level error handling, security measures, or edge case handling.

Applied to files:

example/package.json

📚 Learning: 2025-12-18T13:42:39.225Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 3054
File: pnpm-workspace.yaml:68-68
Timestamp: 2025-12-18T13:42:39.225Z
Learning: In the express-zod-api repository, Vite is overridden to v8 beta in pnpm-workspace.yaml specifically to ensure vitest (which depends on Vite) uses the same rolldown bundler as tsdown and unrun. This override is intentional for toolchain consistency, as Vite is only used for testing purposes (not production).

Applied to files:

example/package.json

📚 Learning: 2025-06-14T16:42:52.972Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2736
File: express-zod-api/tsup.config.ts:12-26
Timestamp: 2025-06-14T16:42:52.972Z
Learning: In express-zod-api tsup configurations, the direct mutation of `options.supported` in the `esbuildOptions` callback is intentional behavior and should not be flagged as a side effect issue.

Applied to files:

example/package.json

📚 Learning: 2025-06-02T21:08:56.475Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2697
File: CHANGELOG.md:5-5
Timestamp: 2025-06-02T21:08:56.475Z
Learning: The `cjs-test` directory in the express-zod-api repository is a test workspace and should be excluded when checking for main project version consistency with changelog entries.

Applied to files:

example/package.json

📚 Learning: 2025-05-27T19:35:57.357Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2546
File: express-zod-api/tests/buffer-schema.spec.ts:32-37
Timestamp: 2025-05-27T19:35:57.357Z
Learning: In the express-zod-api project, tests are run from the `express-zod-api` workspace directory, and the project uses an ESM-first environment without `__dirname`. Relative paths like `../logo.svg` in test files correctly resolve to the repository root due to this test execution context.

Applied to files:

example/package.json

📚 Learning: 2025-05-28T18:58:10.064Z

Learnt from: RobinTail
Repo: RobinTail/express-zod-api PR: 2428
File: express-zod-api/src/index.ts:44-44
Timestamp: 2025-05-28T18:58:10.064Z
Learning: The type-only import `import type {} from "qs";` in express-zod-api/src/index.ts is necessary to avoid TS2742 errors for exported functions like attachRouting, makeRequestMock, testEndpoint, and testMiddleware that have types depending on types/qs. This import provides the reference TypeScript needs to infer portable type names.

Applied to files:

example/package.json

example/package.json

# Conflicts: # pnpm-lock.yaml

RobinTail · 2026-01-25T20:02:58Z

Need #3188 to upgrade to latest vite

RobinTail · 2026-01-25T20:15:18Z

⚠️ there is an issue with coverage

Related issue: vitejs/rolldown-vite#575

Reported to be fixed in vite beta 11 by using rolldown rc.2

# Conflicts: # pnpm-lock.yaml

RobinTail · 2026-02-05T03:07:04Z

rolldown updated to rc3 in #3203

… sync).

pnpm-lock.yaml

RobinTail

reviewed, ok

RobinTail added dependencies Pull requests that update a dependency file CI/CD labels Nov 10, 2025

RobinTail commented Nov 10, 2025

View reviewed changes

.github/workflows/node.js.yml Outdated Show resolved Hide resolved

RobinTail commented Nov 10, 2025

View reviewed changes

.github/workflows/node.js.yml Outdated Show resolved Hide resolved

RobinTail changed the title ~~Exp: replacing esbuild with rolldown~~ Replacing esbuild with rolldown Nov 22, 2025

RobinTail mentioned this pull request Nov 22, 2025

Revert "Rev: Import extensions" #3080

Merged

RobinTail mentioned this pull request Nov 22, 2025

Rev: Import extensions (2) #3081

Merged

RobinTail added a commit that referenced this pull request Nov 22, 2025

Rev: Import extensions (2) (#3081)

cd4f151

Copy of #3055 , because the issue in #3054 is not caused by it

RobinTail added 5 commits November 22, 2025 19:50

Introducing experiment branch.

3494b19

Replacing tsx with unrun (#3051)

259e57f

Since `tsdown` is going to keep it anyway, it can replace `tsx`

Override vite to rolldown-vite (#3053)

d8b6378

Should go along with #3051 All that will help to get rid of `esbuild` and use faster approach based on Rust.

Ensure esbuild is nullified, sort overrides.

f97ef6c

Rev: trigger branch

9913bdd

RobinTail force-pushed the exp-no-esbuild branch from 53dfa2a to 9913bdd Compare November 22, 2025 19:02

RobinTail changed the title ~~Replacing esbuild with rolldown~~ Exp: Replacing esbuild with rolldown Nov 22, 2025

RobinTail added the external bug it's a bug, but in a dependency label Nov 22, 2025

RobinTail and others added 6 commits November 28, 2025 08:46

Merge branch 'master' into exp-no-esbuild

280f879

# Conflicts: # cjs-test/quick-start.spec.ts # pnpm-lock.yaml

Using unrun 0.2.14.

5f54bad

Add unresolved peers to example ws from dev catalog.

a914694

Merge branch 'master' into exp-no-esbuild

8a2078f

# Conflicts: # package.json # pnpm-lock.yaml # pnpm-workspace.yaml

Bump rolldown-vite to latest.

6b16c36

minor: todo.

ffc5c30

RobinTail changed the title ~~Exp: Replacing esbuild with rolldown~~ Replacing esbuild with rolldown Nov 29, 2025

RobinTail removed the external bug it's a bug, but in a dependency label Nov 29, 2025

RobinTail marked this pull request as ready for review December 6, 2025 08:20

RobinTail added 2 commits December 8, 2025 14:20

Using vite 8 beta 1.

b51ee8e

Merge branch 'master' into exp-no-esbuild

a331d90

# Conflicts: # pnpm-lock.yaml

RobinTail commented Dec 8, 2025

View reviewed changes

pnpm-lock.yaml Outdated Show resolved Hide resolved

Merge branch 'master' into exp-no-esbuild

bb5f3c2

RobinTail force-pushed the exp-no-esbuild branch from 90fcd3e to bb5f3c2 Compare December 8, 2025 18:23

RobinTail added 4 commits December 9, 2025 18:14

Merge branch 'master' into exp-no-esbuild

2e37a07

# Conflicts: # pnpm-lock.yaml

Merge branch 'master' into exp-no-esbuild

7485523

Merge branch 'master' into exp-no-esbuild

5df6352

Merge from master and use vite 8 beta 3.

c53b3f9

RobinTail commented Dec 18, 2025

View reviewed changes

coderabbitai bot reviewed Dec 18, 2025

View reviewed changes

pnpm-workspace.yaml Outdated Show resolved Hide resolved

RobinTail changed the title ~~Replacing esbuild with rolldown~~ Replacing rollup and esbuild with rolldown Dec 18, 2025

RobinTail added 3 commits December 21, 2025 21:17

Merge branch 'master' into exp-no-esbuild

955575c

# Conflicts: # pnpm-lock.yaml

Merge branch 'master' into exp-no-esbuild

9c6a5a7

# Conflicts: # pnpm-lock.yaml

Merge branch 'master' into exp-no-esbuild

7cbea0e

# Conflicts: # package.json # pnpm-lock.yaml

coderabbitai bot reviewed Jan 2, 2026

View reviewed changes

example/package.json Show resolved Hide resolved

example/package.json Outdated Show resolved Hide resolved

RobinTail added 4 commits January 10, 2026 16:00

Merge from master and use vite 8 beta 7.

ccf687d

rm resolution supporting deps from example.

7ad8c65

Merge branch 'master' into exp-no-esbuild

d328b2d

Merge branch 'master' into exp-no-esbuild

be3d7ee

# Conflicts: # pnpm-lock.yaml

merge from master and use vite 8 beta 10.

de35a18

Merge branch 'master' into exp-no-esbuild

93c9bc9

# Conflicts: # pnpm-lock.yaml

merge from master and using vite 8 beta 12 (rolldown rc2 - not yet in…

5edc225

… sync).

RobinTail commented Feb 5, 2026

View reviewed changes

pnpm-lock.yaml Outdated Show resolved Hide resolved

vite 8 beta 13, rolldown rc 3 in sync.

dd05042

RobinTail commented Feb 5, 2026

View reviewed changes

Uh oh!

Replacing rollup and esbuild with rolldown #3054

Are you sure you want to change the base?

Replacing rollup and esbuild with rolldown #3054

Uh oh!

Conversation

RobinTail commented Nov 10, 2025 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai bot commented Nov 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Sequence Diagram(s)

Estimated code review effort

Possibly related PRs

Suggested labels

Poem

Uh oh!

coveralls-official bot commented Nov 10, 2025

Uh oh!

coveralls-official bot commented Nov 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

RobinTail commented Nov 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

RobinTail commented Nov 29, 2025

Uh oh!

Uh oh!

RobinTail left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

RobinTail commented Jan 25, 2026

Uh oh!

RobinTail commented Jan 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

RobinTail commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

RobinTail left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Replacing `rollup` and `esbuild` with `rolldown` #3054

Replacing `rollup` and `esbuild` with `rolldown` #3054

RobinTail commented Nov 10, 2025 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Nov 10, 2025 •

edited

Loading

coveralls-official bot commented Nov 10, 2025 •

edited

Loading

RobinTail commented Nov 22, 2025 •

edited

Loading

RobinTail commented Jan 25, 2026 •

edited

Loading

RobinTail commented Feb 5, 2026 •

edited

Loading