Summary

Update storybook and switch to @rollup/plugin-babel.

Review Request #15125 — Created June 16, 2026 and submitted June 23, 2026, 3:54 p.m.

Information

Owner

david

Repository

Ink

Branch

master

Bugs

Depends On

Reviewers

Groups

beanbag-misc

People

Description

This change bumps us up to the latest storybook version for Ink, and
replaces @vitejs/plugin-react with @rollup/plugin-babel (we were
only using the react plugin because we needed a build setup that could
invoke babel).

In addition to simplifying things significantly by jettisoning the react
dependencies, this allows us to pull in the latest esbuild, fixing audit
errors.

Testing Done


Ran storybook and verified that things worked correctly.
Built a package and verified that it could be consumed.

Commits

Summary	ID
Update storybook and switch to @rollup/plugin-babel. This change bumps us up to the latest storybook version for Ink, and replaces `@vitejs/plugin-react` with `@rollup/plugin-babel` (we were only using the react plugin because we needed a build setup that could invoke babel). In addition to simplifying things significantly by jettisoning the react dependencies, this allows us to pull in the latest esbuild, fixing audit errors. Testing Done: - Ran storybook and verified that things worked correctly. - Built a package and verified the result.	qzosqkyuzvqvkqxwzrwqmqttnmwusrty

Summary

Update storybook and switch to @rollup/plugin-babel.

This change bumps us up to the latest storybook version for Ink, and replaces `@vitejs/plugin-react` with `@rollup/plugin-babel` (we were only using the react plugin because we needed a build setup that could invoke babel). In addition to simplifying things significantly by jettisoning the react dependencies, this allows us to pull in the latest esbuild, fixing audit errors. Testing Done: - Ran storybook and verified that things worked correctly. - Built a package and verified the result.

qzosqkyuzvqvkqxwzrwqmqttnmwusrty

Issues

Description	From	Last Updated
Can you verify (and update testing) that a package build works and can be consumed?	chipx86	June 22, 2026, 10:22 p.m.

flake8 passed.

JSHint passed.

The issue has been resolved. Show all issues

Can you verify (and update testing) that a package build works and can be consumed?

Testing Done:

~		Ran storybook and verified that things worked correctly.
	~	Ran storybook and verified that things worked correctly.
	+	Built a package and verified that it could be consumed.

Commits:

	Summary	ID
	Update storybook and switch to @rollup/plugin-babel. This change bumps us up to the latest storybook version for Ink, and replaces `@vitejs/plugin-react` with `@rollup/plugin-babel` (we were only using the react plugin because we needed a build setup that could invoke babel). In addition to simplifying things significantly by jettisoning the react dependencies, this allows us to pull in the latest esbuild, fixing audit errors. Testing Done: Ran storybook and verified that things worked correctly.	qzosqkyuzvqvkqxwzrwqmqttnmwusrty
	Update storybook and switch to @rollup/plugin-babel. This change bumps us up to the latest storybook version for Ink, and replaces `@vitejs/plugin-react` with `@rollup/plugin-babel` (we were only using the react plugin because we needed a build setup that could invoke babel). In addition to simplifying things significantly by jettisoning the react dependencies, this allows us to pull in the latest esbuild, fixing audit errors. Testing Done: - Ran storybook and verified that things worked correctly. - Built a package and verified the result.	qzosqkyuzvqvkqxwzrwqmqttnmwusrty

Diff:

Revision 2 (+74 -60)

Show changes

	package.json
	vite.config.js

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

Ship it!

```
Ship It!
```

Status:: Completed
Change Summary:: Pushed to master (44c350e)