Build more, bundle less.

Create react apps without bundling.

Bundless.js: A 36kb browser shim that resolves and tanspiles React JSX code at runtime.

Try it out - Examples - Benchmarks

Usage

All type='text/jsx', /tsx, and /babel scripts will be transpiled onDomLoad when you place the following tag in your html page:

JSX & Typescript link: 52Kb | source-maps

</script src="./bundless.sucrase.min.js"> 

JSX Only link: 36Kb | no source-maps

</script src="./bundless.acorn.min.js"> 

• Add to="preact" if you want your react code transpiled to preact.
• Tips on Toubleshooting

That's it!

How it works

1. Modules resolve using <script type="importmap">
2. Imports are inserted into the page as modules
3. Dynamic import() behavior gets modified

Publication

• Git tags now drive the release flow through GitHub Actions.
• Release builds are expected to be created locally before you tag and push a release.
• Release bundles are attached to GitHub Releases and can be fetched from the GitHub-backed jsDelivr CDN, for example https://cdn.jsdelivr.net/gh/karpatic/[email protected]/dist/bundless.acorn.min.js.
• GitHub Releases are live through v1.0.6, and the GitHub-backed jsDelivr route is the current verified CDN path.
• The npm package bundlessdev is published to npmjs, and the same release flow can also publish a GitHub Packages variant as @karpatic/bundlessdev.
• Run the local release build, bump package.json, and then push a version tag like v1.0.9; GitHub Actions will use the checked-in dist files to create the GitHub Release, publish bundlessdev to npm through trusted publishing via OIDC, and publish @karpatic/bundlessdev to GitHub Packages with GITHUB_TOKEN.
• The release workflow now runs on version tags instead of every main push so release history stays focused on real versioned releases.

Memes