solito
turbo
solito | turbo | |
---|---|---|
26 | 145 | |
3,254 | 6,424 | |
- | 0.9% | |
8.1 | 8.7 | |
11 days ago | 12 days ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
solito
-
React Native in Next.JS for Hybrid Web/Mobile Monorepo: Should I give up? ($250 Bounty)
I've been building for the past 3-4 months on the Solito starter repo that uses React Native to build the shared components that are used by both Next.JS for web and Expo for mobile. This theoretically should be harder/longer to build than one of these alone, but easier/shorter than building both separate projects. Has anyone built this kind of monorepo to completion/production before and can share this experience? Am I on the right path and this is a hump during the package configuration phase or would I be better off just using React and constantly maintaining two codebases that have to match feature parity?
-
Easiest Way to Build a Cross-Platform App (Web & Mobile) with Minimal Code Duplication
I think this is what you are looking for: https://solito.dev/ ๐
-
How to edit Next.Config.js to add plugins like Skia?
We're encountering an issues on the web side while trying to run React Native Skia in NextJS as part of a Solito monorepo. Mobile (Expo) seems to work fine, but the "warning" Skia throws of not finding reanimated is causing Next.js builds to error out with the following error:
-
Tamagui โ UI kit that unify React Native and Web
Iโve only just started using it but https://solito.dev/ seems to do exactly that.
-
Suggestions for converting a Next.js (app router) / Tailwind CSS website hosted on Vercel to a OSX app
I found Solito and see that it may perhaps support react-native-macos - does anyone have experience here?
-
Expo โ open-source platform for making universal apps for Android, iOS, and web
It has become very practical / doable in the recent year or so. In my experience, if you have lot of frontend web experience, the easiest way to ship a RN app is by using Solito [0]. Also check out Nativewind [1] which allows you to style native apps the same way like you would on web. I was able to ship the first version of our app in about 1.5 weeks with this stack. Also checkout Tamagui [2].
[0] - https://solito.dev
-
2 big announcements - Tamagui Takeout & Solito 4
Solito 4 - https://github.com/nandorojo/solito/releases/tag/v4.0.0
- NextJS on iOS & Android????? How???
-
Deciding between RNW and React
Another option is the Solito stack which has a single code base for react native and next js. https://solito.dev/
-
NextJS + Expo question: What's does @expo/next-adapter and Solito do? Can they be used Together?
The [Expo docs for NextJS](https://docs.expo.dev/guides/using-nextjs/) recommends @expo/next-adapter, while I have a sense of what [Solito](https://github.com/nandorojo/solito) does as [explained by the author](https://www.youtube.com/watch?v=H1gSWXA3qfw). I'm not fully clear what the difference these two libraries are and whether they can or should be used together.
turbo
-
Turbo Streaming Modals in Ruby on Rails
I also recommend checking out the docs for Stimulus and Turbo to familiarise yourself with all their features and the APIs used in this series.
-
Htmx vs. React: A Complete Comparison โ Semaphore
https://github.com/hotwired/turbo
- Turbo 8 has been released
-
What is JSDoc and why you may not need typescript for your next project?
Turbo 8 remove typescript without using JSDOC
-
Coming to grips with JS: a Rubyist's deep dive
Experiment using Turbo to drive front-end behavior: "Turbo 7.2.0 (currently in beta) allows you to define your own Stream actions which can be any JS code you want. By combining a custom Stream action or two with web components, you can essentially drive reactive frontend behavior from the backend stupidly easily. Loooove it! ๐ [โฆ] For a turnkey example, you could check out https://github.com/hopsoft/turbo_ready " โJared White on The Spicy Web Discord
-
Improving a web component, one step at a time
This handles disconnection (as could be done by any destructive change to the DOM, like navigating with Turbo or htmx, I'm not even talking about using the element in a JavaScript-heavy web app) but not reconnection though, and we've exited early from the connectedCallback to avoid initializing the element twice, so this change actually broke our component in these situations where it's moved around, or stashed and then reinserted. To fix that, we need to always call addSparkles in connectedCallback, so move all the rest into an if, that's actually as simple as thatโฆ except that when the user prefers reduced motion, sparkles are never removed, so they keep piling in each time the element is connected again. One way to handle that, without introducing our housekeeping of individual timers, is to just remove all sparkles on disconnection. Either that or conditionally add them in connectedCallback if either we're initializing the element (including attaching the shadow DOM) or the user doesn't prefer reduced motion. The difference between both approaches is in whether we want the small animation when the sparkles appear (and appearing at new random locations). I went with the latter.
-
Mastering Rails Web Navigation with link_to and button_to Helpers - Part 2
If you think you have seen enough Rails magic, you are mistaken my friend. Rails have a new trick up its sleeve: Hotwire. And with the magical Turbo tool that comes with it, you can create modern, interactive web applications with minimal, or sometimes no JavaScript at all, providing users with an incredibly smooth experience.
-
Why you should choose HTMX for your next project
There is also Turbo and the frameworks who adopt them, Ruby on Rails, PHP Symphony and possibly others that solves the same issue in the same manner as HTMX. And the choice for HTMX is only a personal taste in this, but you should definitely learn about this, this is as cool as HTMX!
-
JavaScript First, Then TypeScript
Most controversially, the Turbo framework dropped TypeScript support altogether after assessing that strong typing was the culprit behind poor developer experience.
-
Rack Attack โ Rails Tricks
Turbo[0] has been solving this for years. Quite the contrary, front-end frameworks have started to think "sending JSON is good, but actually sending HTML could be great!".
DHH's presentation[1] during Rails World 2023 is quite interesting in that regard, I recommend you give it a go (start around minute 16). I am actually very excited with his vision of the web.
[0] https://turbo.hotwired.dev/
What are some alternatives?
t3-turbo-and-clerk - A t3 Turbo starter with Clerk as the auth provider.
htmx - </> htmx - high power tools for HTML
create-t3-turbo - Clean and simple starter repo using the T3 Stack along with Expo React Native
Turbolinks - Turbolinks makes navigating your web application faster
moti - ๐ผ The React Native (+ Web) animation library, powered by Reanimated 3.
hotwire-rails - Use Hotwire in your Ruby on Rails app
showtime-frontend - Showtime makes digital collectibles useful, accessible and social.
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
tamagui - Style React fast with 100% parity on React Native, an optional UI kit, and optimizing compiler.
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)
react-native - A framework for building native applications using React
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.