Better UX, Better DX ➊ One is a cross-platform React framework built for sync engines · “one.js" in the streets
- Tweets 259
- Following 90
- Followers 2,611
- Likes 552
we fixed a bug with useParams in One that's also in @expo Router - took a couple hours to isolate but the fix is just a one-liner so just tagging them here so they know 😊
github.com/expo/expo/issues/…
4
27
2,869
We're doing things differently
I'm excited for @LynxJS_org and I think React universal really needs a kick in the pants.
But also - the only way @one__js would support it is if someone forked it. Or, if Lynx became the clear best solution and we migrated over to only Lynx.
I've been using a lot of libraries lately that are "cross-framework" and honestly not having a good time. They seemingly check all the right boxes, but in reality they have gaps everywhere because they can't invest their focus into doing, well, one thing well.
The entire point of One is to be opinionated and consistent. Vibe coding gets exponentially better the less divergence there is between not just your framework, but all libraries in your stack, and all stacks in the ecosystem. It's a non-linear return on value that we are specifically aimed at.
1
15
1,647
Try it out!
github.com/onejs/one/release…
1
696
⏶ Vercel support is here
✓ Build Output API v3
✓ Skew protection
✓ One line configuration
Contributed by community member @PineapplesDev
6
4
66
5,387
You can start with plain Vite and transition into a One app at any time simply by:
npm i one
And adding it as a plugin to your Vite config.
“Framework in a plugin” - it’s pretty great.
Its not really hard to add SSR or SSG to Vite.
There’s Vike, and One which both are just a plugin and basically are plain Vite apps that add more framework like features.
“Framework in a plugin”. It’s pretty amazing actually that you can start simply and still do that.
21
1,745
One retweeted
Would love to see @one__js mentioned. It’s been a lot of work and I think another native framework is great for the ecosystem.
Also incredibly easy migration from CRA:
onestack.dev/docs/guides-mig…
3
2
60
7,969
One retweeted
I guess it is not clear enough on the website, because we keep receiving comments. I'll have to find some way to improve them.
Zero is 100% open source, and has been since day one:
github.com/rocicorp/mono/tre…
Although our prior products were closed-source, Zero is a different kind of thing. It's a big change to web app architecture and we felt it could only achieve its maximum potential as an open project. There will be tons of connections and integrations needed with all kinds of projects in the ecosystem. We didn't want anyone to have a reason to not use or build around Zero.
We've already gotten contributions to this effect for: svelte, solidjs, vue, next.js, prisma, drizzle, gcp, sst, windows, linux, various js build tools, and mongo, among myriad more minor contributions to the zero itself and the docs.
On a wider note, I've spent the majority of my career building open source software (greasemonkey, chrome, webkit, blink) and am very glad to get back to it. We could not figure out a reasonable OSS business model for our prior projects because they were client-centric. Zero doesn't have that problem.
Our loose plan is to make a business by offering a SaaS version of zero-cache, and also white-glove on prem support for larger enterprises. But bigger picture, it's clear that the web is moving to sync. This is such a big shift and will create so many opportunities, that we're not *that* worried about finding a business model immediately. Just focused on making Zero as good as it can be.
cc: @theo
17
19
268
23,073
spread across a few recent releases
github.com/onejs/one/release…
436
- getServerData, setServerData
- useServerHeadInsertion
- react-native-bottom-tabs
- postcss config fix
- docs++
see you next month 😘
2
10
1,453
