HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
necolas
react-native-web
JavaScript2015–2023
necolas / react-native-web

react-native-web

Cross-platform React UI packages

Web DevelopmentMobile & Desktop
Explore on GitHubRead Hacker News discussions
45Distinct people
51Mentions
0Explicit recommenders
22.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Cross-platform React UI packages

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year51 dated mentions

Observed mentions: 2015-09-17 14:29:41 UTC to 2023-01-31 20:46:17 UTC.

0510152015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 14 mentions; 0 submissions, 14 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC303
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC12111
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC14014
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC716
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC606
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC505
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Development monorepo This is the development monorepo for "React Native for Web" and related projects. Structure .github Contains workflows used by GitHub Actions. Contains issue templates. packages react-native-web Contains the individual packages managed in the monorepo. scripts Contains Node.js scripts for miscellaneous tasks. Tasks build Use npm run build to run the build script in every package. Use npm run build -w <package-name> to run the build script for a specific package. dev Use npm run dev to run the dev script in every package. Use npm run dev -w <package-name> to run the dev script for a specific package. test Use npm run test to run tests for every package. More details can be found in the contributing guide below. Contributing Development happens in the open on GitHub and we are grateful for contributions including bugfixes, improvements, and ideas. Code of conduct This project expects all participants to adhere to Meta's OSS Code of Conduct. Please read the full text so that you can understand what actions will and will not be tolerated. Contributing guide Read the contributing guide to learn about the development process, how to propose bugfixes and improvements, and how to build and test your changes to React Native for Web. Good first issues To help you get you familiar with the contribution process, there is a list of good first issues that contain bugs which have a relatively limited scope. This is a great place to get started.
Read the full README on GitHub

What Hacker News says

14 sources
todd3834·Sep 20, 2017
So we've tried a lot of things to maximize code sharing. Our initial goal was to share non-visual code like reducers/action-creators/libs/utils etc… This was pretty interesting but it didn't give us the amount of sharing that we wanted. We were still building multiple versions of many things. The next approach we started on was using https://github.com/necolas/react-native-web. This was very exciting and very fun to work with. However, we found it difficult to optimize the web experience. Most of our traffic is on the website so we are spending a lot of time optimizing the web experience. This might not line up with other's experience but we kind of came to the conclusion that react-native-web works great for apps where the native app is the primary driver and you want to offer a web experience as a secondary experience. This became more
Read the rest
clear when we started trying to work with our SEO team. And again when we started trying to build responsive designs with react-native-web. Doable but we ended up spending a ton of time to make the web work the way we wanted to. Eventually we decided to go a different direction. Most of our display logic is the same or very similar between the mobile web/ios/android with a few exceptions. We found that mixing ReactNative with the webview component gave us the ability to use webviews to share the majority of the code that can be shared. When we need more native functionality we communicate with postMessage and we have access to ReactNative. Once in ReactNative if we need to go down to iOS specific or Android specific code we have the ability to do that too. We found this to be much more powerful than Cordova and the user experience is honestly amazing. This is still a work in progress but we are excited about what we've seen so far.
In Ask HN: Companies who adopted React Native over a year ago, do you regret it?
nathan_f77·Aug 20, 2017
The patent stuff doesn't seem very important to me. You might not like it in principle, but I don't think it's going to affect you. The author mentions Flow as a typing solution to solve some of the problems with Javascript development, but didn't like it because you can still write code that crashes if you ignore the warnings. They also complained about the lack of immutability, and mentioned Immutable.js, but weren't happy with that. They went on to say that most of these problems they mentioned are already solved with libraries, but ... libraries are bad? I didn't really pay attention to the huge Javascript rant in the middle, but I've heard it all before, and I totally disagree. I've started to realize that I prefer ES7 Javascript with Flow or Typescript, jest, babel, webpack, etc. I think I actually enjoy writing it more than Ruby or
Read the rest
Swift. I really like react-native-web [1]. I've used it to build an app that runs on all mobile devices (iOS, Android, Windows Phone), as well as on the web. There's a lot of quirks and workarounds, but it was actually a lot easier that I expected. Even if you just use plain react on the web, it's easy to write re-usable components and code. They also mentioned hot reloading. If I wrote an article titled "Why I'm a React Native developer", the content would just be the words "Hot reloading." I spent a year developing a native iOS app with Swift, and I never want to go back to waiting for my code to compile. [1] https://github.com/necolas/react-native-web
In Why I'm not a React Native developer
nathan_f77·May 28, 2017
It's difficult to convert a React web app into a React Native app, but you can use many React Native components on the web (via react-native-web. [1]) In other words, you can't run a web app on mobile, but you can run a mobile app on the web. I just launched a little game that I built with React Native [2], where I have a single codebase that supports iOS, Android, Windows, and web. [1] https://github.com/necolas/react-native-web [2] https://sudoblock.com
In Switching From React To Vue.js
migueloller·Apr 11, 2017
There's some early work for Ubuntu here [1]. You can also currently use React to share code across iOS [2], Android [3], UWP [4], macOS [5], web [6], VR [7] and a bunch of other stuff that is there mostly for fun (like React Hardware [8] and React Sketch.app [9]). There's also experimental work on defining a set of primitives that works across all of these platforms [10]. [1] https://github.com/CanonicalLtd/react-native/blob/ubuntu/REA... [2] https://github.com/facebook/react-native [3] https://github.com/facebook/react-native [4] https://github.com/Microsoft/react-native-windows [5] https://github.com/ptmt/react-native-macos [6] https://github.com/necolas/react-native-web [7] https://github.com/facebook/react-vr [8] https://github.com/iamdustan/react-hardware [9] https://www.npmjs.com/package/react-sketchapp [10] https://github.com/lelan
Read the rest
drichardson/react-primitives
In Electron is flash for the desktop (2016)
migueloller·Apr 8, 2017
I'm a bit skeptical this is needed at all. I would've much preferred if Microsoft contributed to the already popular React Native for Web [1]. React Native already supports iOS, Android, and UWP. To add browser support all you need is something like React Native for Web. I made a small presentation a few months ago that shows this. Here's the source code: [2]. Take a look at the web folder. Libraries like React Navigation [3] have also been built to support any platform that runs React code. It looks like Microsoft built yet another navigation library [4]. Also, check out React Primitives [5]. It aims to define a set of primitives that work on any platform that can be used to build more complex components. This is highly experimental, but I'm liking the direction where it's going, a unified React interface for any platform. In addition, R
Read the rest
eactVR is a great example of how React Native primitives can be extended to new emerging platforms [6]. Finally, React Native for macOS [7] answers the question that many have here about building native apps for macOS without relying on Electron. [1] https://github.com/necolas/react-native-web [2] https://github.com/migueloller/HelloWorldApp [3] https://github.com/react-community/react-navigation [4] https://microsoft.github.io/reactxp/docs/components/navigato... [5] https://github.com/lelandrichardson/react-primitives [6] https://github.com/facebook/react-vr [7] https://github.com/ptmt/react-native-macos
In ReactXP – A library for building cross-platform apps
nostrademons·Mar 13, 2017
Ironically, there's now a backport of React Native back to the web, which renders the stock React Native components using vanilla <divs> and <spans>. https://github.com/necolas/react-native-web If you're doing cross-platform prototyping, it can actually be easier than writing the app in React (or vanilla JS) and then porting to React Native, because the React Native elements are at a slightly higher semantic level of abstraction than stock DOM elements. The markup it generates is pretty atrocious, but if you just want to get something up on the screen, you can work out your design compromises first and then optimize it.
In Better List Views in React Native

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.