react-native-web
Svelte
react-native-web | Svelte | |
---|---|---|
62 | 635 | |
21,345 | 76,639 | |
- | 0.8% | |
6.7 | 9.9 | |
5 days ago | 1 day ago | |
JavaScript | 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.
react-native-web
-
NextJS on iOS & Android????? How???
maybe https://necolas.github.io/react-native-web/? https://github.com/vercel/next.js/blob/canary/examples/with-react-native-web/README.md
-
What version of react native is compatible with react native web?
I am following a tutorial that is 4 years old that states that react native 0.55.4 is last compatible with react native web and anything later is not compatible yet. He showed the documentation page in the video as his source.
-
Rust and Next.js everywhere?
Personally, if you're trying to find a stack that can be applied everywhere with Next.js as your chosen framework, best bet would be React Native Web or similar. Which would let you share the maximum amount of frontend code between Web, iOS, and Android. Then you could reach for electron (barf) or something to bundle it for desktop if that was a requirement.
-
Here's what I'd like to do as a hobby project... what should I learn?
Some of the top cross-platform frameworks do have support for web targets. React-Native-Web and Flutter on the Web are both ways to target the web with your cross-platform app.
-
How do i intergrate vite.js with my current react-native project?
https://github.com/necolas/react-native-web/discussions/2201 it can be done.
-
Which is the best lib/framework option for a single code base for web, Android & iOS?
If you want a single codebase for web and mobile I would look into react-native and react-native-web. You could probably code the web app with react-native-web, make it responsive and build it through react-native for mobile. Designing an app for mobile and for web can lead to significant difference though since the experience is quite different. Some things might make sense for a mobile and not for a desktop or the opposite. So I wouldn't discard completely the idea of having separate codebases. Highly depends on the app though, totally valid for many use cases.
-
Need an advice for frontend framework (beginner in frontend development)
Another fun thing you could do is build it for mobile + web using React-Native through Expo or manually with https://necolas.github.io/react-native-web/
-
I lost $209,640 of my own money trying to start a business
If you're using Expo (which I assume most are on RN) they have web support. This is via React Native Web, which is a separate project if you wanted to use that directly too.
Personally though, I've found the DX of Flutter far above RN. I always had random packages break on RN that I had to fix every time, while with Flutter most of what you need is already included in the framework, including a component UI library for Android and iOS.
[0] https://docs.expo.dev/workflow/web/
[1] https://github.com/necolas/react-native-web
-
I made a template for making full-stack universal(web + mobile) apps! (tRPC, Expo, Next, Solito, Tamagui, Clerk Auth, Prisma!)
So the RN-R part is done by https://necolas.github.io/react-native-web/ and it's really good! However, there are some code that is kind of outside of the scope of React. Ie. Navigation, that's more in the realm of Next.
-
No, React Native is not the future
I don't have personal experience with this, but React Native Web claims to solve this issue: https://necolas.github.io/react-native-web/, not sure if anyone has had experience with this. Of course, you will have issues with dependency hell/package maintenance.
Another great option seems to be Flutter web. I was really impressed by the "batteries included" approach to Flutter, and Dart has a pretty comprehensive standard library. This is in contrast to React's "just find a random package on npm and pray it doesn't bite you in the future."
Obviously rewrites are expensive, but I personally think both approaches are worth considering versus abandoning native components completely. WebView isn't without problems (and also, you don't need React Native to use WebView).
Svelte
-
Securing SvelteKit Apps with Keycloak
Svelte and specifically, SvelteKit is an open source web framework that makes developing web applications easier.
-
My opinion about opinionated Prettier: ๐
the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:
-
Composable architecture example: Go headless (best practices)
Svelte
-
How to optimise React Apps?
React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.
-
Episode 24/13: Native Signals, Details on Angular/Wiz, Alan Agius on the Angular CLI
Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and moreโฆ
- Rich Harris: Svelte parses HTML all wrong
- Mario meets Pareto: multi-objective optimization of Mario Kart builds
- Svelte parses HTML all wrong
-
Svelte for Beginners: Easy Guide
Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.
What are some alternatives?
react-native-keyboard-aware-scroll-view - A ScrollView component that handles keyboard appearance and automatically scrolls to focused TextInput.
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
lit - Lit is a simple library for building fast, lightweight web components.
sciter-js-sdk - Sciter.JS - Sciter but with QuickJS on board instead of my TIScript
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces. [Moved to: https://github.com/solidui/solid]
metro - ๐ The JavaScript bundler for React Native
qwik - Instant-loading web apps, without effort
react-native-elements - Cross-Platform React Native UI Toolkit
awesome-blazor - Resources for Blazor, a .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly.
react-native-material-ui - Highly customizable material design components for React Native
Next.js - The React Framework