greenwood
react-native-web
greenwood | react-native-web | |
---|---|---|
21 | 62 | |
92 | 21,337 | |
- | - | |
8.0 | 6.7 | |
7 days ago | 9 days 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.
greenwood
-
Best SSG for resume website?
I have a project in called Greenwood that can probably help here if you're interested to check it out. Made to easily start with HTML (or markdown) and focused on web standards to make learning and development easy and familiar. Works great with Web Components and can even pre-render them! https://github.com/ProjectEvergreen/greenwood
-
Need an advice for frontend framework (beginner in frontend development)
Either is pretty easy to get started with and keep you nicely aligned with web standards if that's of interesting to you. I have a project that could help you work with either of those option you are so inclined, with the getting started guide of the website giving a brief overview of how to get started with native web components. https://www.greenwoodjs.io/
-
Server-Side Includes (SSI) - Porkbun static web hosting
My project Greenwood might be able to help here, depending on what your current setup looks like. Inspired by the old HTML Includes spec, I created a plugin for replicating this sort of edge side include behavior.
-
Do people build websites with just html/css/vanilla js anymore or is learning react almost mandatory?
I do, and that's a big part of why I started working on Greenwood. I wanted to always just be able to start from an index.html file, but also have some nice minimal glue like a dev server, file based routing, markdown, and leveraging Web Components for templating and SSR.
-
I'm not convinced that "modern" web dev is also "better"
That's a big part of why I started working on Greenwood. I wanted to always just be able to start from an index.html file, but also have some nice minimal glue like dev server, file based routing, markdown, and even leveraging Web Components for templating and SSR. Loving learning even more about the web and so for that reason I like to think of it less as a framework, and instead as your full-stack workbench for the web! https://github.com/ProjectEvergreen/greenwood
-
Are static websites still relevant? I'm an old dad (long time internet programmer) trying to help put a family member's animation portfolio online.
I created my project Greenwood as a way to support web standards based development (e.g. not a meta framework) that can be as easy to start with as an index.html, or a markdown file, and can do most architectures; SPA / CSR, MPA, SSR. I like to think of it as your full-stack workbench for the web.https://github.com/ProjectEvergreen/greenwoodStill a WIP and continuing to improve our design and feature set, so feel to give it a try, and any and all feedback welcome! Check out our blog if your curious about what we've been up to in 2022, and there will be a post soon about our plans for 2023![https://www.greenwoodjs.io/blog/](https://www.greenwoodjs.io/blog/)
-
Javascript And HTML Templates
Not sure if this would be of interest to you, but my project Greenwood let’s you start with just HTML / markdown and standard web dev to build out the rest, with a focus on supporting Web Components, even for SSR. https://www.greenwoodjs.io
-
Are frameworks basically an evolution towards low code/no code?
I like to think of my project Greenwood not so much of a framework, for similar sentiments as what you describe, and have come to refer to it as a "workbench for the web"; emphasizing web standards based development (e.g. so not a meta framework) and has great support for Web Components. (full stack web components, ftw!) https://github.com/ProjectEvergreen/greenwood
-
I want to make a small blog, but write everything .md and host it on the internet. What technology can I use?
My project Greenwood might be able to help. It supports web standards based development (e.g. not a meta framework) and has great support for Web Components. As easy to start as an index.html file or a markdown file, and can do most architectures; SPA / CSR, MPA, SSR. I like to think of it as your workbench for the web. https://github.com/ProjectEvergreen/greenwood Still a WIP and continuing to improve our design and feature set, so feel to give it a try, and any and all feedback welcome!
- Is there a technology for reusing HTML components?
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).
What are some alternatives?
PSWriteHTML - PSWriteHTML is PowerShell Module to generate beautiful HTML reports, pages, emails without any knowledge of HTML, CSS or JavaScript. To get started basics PowerShell knowledge is required.
react-native-keyboard-aware-scroll-view - A ScrollView component that handles keyboard appearance and automatically scrolls to focused TextInput.
twitch-nintendo-nes - NaNtendo: A visual Nintendo NES console with pure HTML/CSS/Javascript (WebComponents)
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
base64-transcode - Base64 encoding and decoding for both browser and node, with binary file support.
sciter-js-sdk - Sciter.JS - Sciter but with QuickJS on board instead of my TIScript
twitch-megadrive-genesis - SEGA MegaDrive (Sega Genesis) with CSS
metro - 🚇 The JavaScript bundler for React Native
script-type - Learn differences between script defer, async and modules
react-native-elements - Cross-Platform React Native UI Toolkit
quasar-app-extension-ssg - Static Site Generator App Extension for Quasar.
react-native-material-ui - Highly customizable material design components for React Native