- v2.3.8Latest
- v2.3.7
- v2.3.6
- v2.3.5
- v2.3.4
- v2.3.3
- v2.3.2
- v2.3.1
- v2.3.0
- v2.2.4
- v2.2.3
- v2.2.2
- v2.2.1
- v2.2.0
- v2.1.7
- v2.1.7
- v2.1.6
- v2.1.5
- v2.1.4
- v2.1.3
- v2.1.2
- v2.1.1
- v2.1.0
- v2.0.1
- v2.0.0
- v2.0.0-beta.19
- v2.0.0-beta.18
- v2.0.0-beta.17
- v2.0.0-beta.16
- v2.0.0-beta.15
- v2.0.0-beta.14
- v2.0.0-beta.13
- v2.0.0-beta.12
- v2.0.0-beta.11
- v2.0.0-beta.10
- v2.0.0-beta.9
- v2.0.0-beta.8
- v2.0.0-beta.7
- v2.0.0-beta.6
- v2.0.0-beta.5
- v2.0.0-beta.4
- v2.0.0-beta.3
- v2.0.0-beta.2
- v2.0.0-beta.1
- v2.0.0-alpha.19
- v2.0.0-alpha.18
- v2.0.0-alpha.17
- v2.0.0-alpha.16
- v2.0.0-alpha.15
- v2.0.0-alpha.14
- v2.0.0-alpha.13
- v2.0.0-alpha.12
- v2.0.0-alpha.11
- v2.0.0-alpha.10
- v2.0.0-alpha.9
- v2.0.0-alpha.8
- v2.0.0-alpha.7
- v2.0.0-alpha.6
- v2.0.0-alpha.5
- v2.0.0-alpha.5
- v2.0.0-alpha.4
- v2.0.0-alpha.3
- v2.0.0-alpha.2
- v2.0.0-alpha.1
- v2.0.0-alpha.0
- v1.0.1
- v1.0.0
- v0.8.2
- v0.8.1
- v0.8.0
- v0.7.6
- v0.7.5
- v0.7.4
- v0.7.3
- v0.7.2
- v0.7.1
- v0.7.0
- v0.7.0
- v0.6
- v0.5
- v0.4
- v0.3
- v0.2
- v0.1
- v0.0
* If you want to get very meta (not facebook), Ultra can be viewed as a tiny bridge to utilise native browser features 🌐 whilst using popular front-end libraries. 🧰
🧙 Start your journey
Here’s a basic Ultra project to set you on your way.
deno run -A https://deno.land/x/ultra@v2.0.0-alpha.1/init.ts
✨ What’s new
Ultra allows you to write web-apps which massively simplify your tool chain. You write ESM, we ship ESM. Where we are going, there is no “bundling” (it feels so 2018 just saying that word).
- Less opinionated, BYO routing, styling, data fetching, and head libraries
- Support for much of the React ecosystem by custom server/client controls**
- Native import maps in browser 🤖
- Localised import maps for production 🔥
- API routing
- Overhaul of internal source code
- Updated Deno Deploy support
** Examples include (but not limited to) react-query
twind
emotion
stiches
react-router
wouter
@__@
Does Ultra ‘ship js’?
Yes, Ultra creates rich web applications which allow complex client-side routing, allow components to persist through route changes (media players, interactive elements, etc).
Our goal is to both write AND ship source code that works the same way on server/runtime and client. We view the browser as more than just a “target”. Browser is life, and javascript is good.
Can I use TypeScript and/or JSX?
If you want.
What native browser features should we all be using more?
Unbundled ESM, service workers, universal import maps, cascading style sheets.
Ultra always has been (and always will be) powered by the following hot-takes:
- ESM is non-negotiable in {currentYear}
- SSR is non-negotiable in {currentYear}
- Bundling is an anti-pattern in {currentYear}
- Data can be requested anywhere, and is accessible on the server, always
- Lazy routing with dynamic imports trumps FS routing
- Less magic in tooling and frameworks is a good thing
- Simplify your workflow and tech stack at all costs - life is too short
- Streams are neat
👨👩👧👦 Community
We have the Discord. Come say ‘sup.
🧟 Contributions
The Ultra community welcomes outside contributions. See the Contributor Guidelines for details.
🦥 Wishlist
Here some things we are interested in for the future of JS and/or Ultra:
- React ESM exports
- AbTs: Anything but TypeScript
- Libraries supporting optimal JavaScript module design
- React resources for streaming head management
- Native import maps support in Safari
- Dynamic import support on Deno Deploy
- Native CSS modules
- More and better ESM CDNs
Thank you for going on this journey with us.