a9f4ec2bf7
|
||
|---|---|---|
| .ado | ||
| .appveyor | ||
| .circleci | ||
| .github | ||
| ContainerShip | ||
| Folly | ||
| IntegrationTests | ||
| Libraries | ||
| RNTester | ||
| React | ||
| ReactAndroid | ||
| ReactApple | ||
| ReactCommon | ||
| bots | ||
| danger | ||
| double-conversion | ||
| flow | ||
| flow-github | ||
| glog | ||
| gradle/wrapper | ||
| jest | ||
| jsc | ||
| keystores | ||
| lib | ||
| local-cli | ||
| metadata | ||
| processor | ||
| react-native-cli | ||
| react-native-git-upgrade | ||
| scripts | ||
| stubs/glog | ||
| template/android/app/src/debug | ||
| third-party-podspecs | ||
| tools/build_defs | ||
| v8-docker-build | ||
| website/server | ||
| .buckconfig | ||
| .buckjavaargs | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .flowconfig | ||
| .flowconfig.android | ||
| .gitattributes | ||
| .github.flowconfig.android | ||
| .gitignore | ||
| .npmignore | ||
| .nvmrc | ||
| Brewfile | ||
| CHANGELOG.json | ||
| CHANGELOG.md | ||
| CMakeLists.txt | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| DockerTests.md | ||
| Jenkinsfile | ||
| LICENSE | ||
| LICENSE-docs | ||
| README.md | ||
| React.podspec | ||
| Releases.md | ||
| build.gradle | ||
| cli.js | ||
| dirs | ||
| gradlew | ||
| gradlew.bat | ||
| jest-preset.json | ||
| package.json | ||
| react.gradle | ||
| rn-cli.config.js | ||
| rn-get-polyfills.js | ||
| runXcodeTests.sh | ||
| settings.gradle | ||
| setupBabel.js | ||
| yarn.lock | ||
README.md
Working fork for Microsoft internal usage
It is not our goal to have a long term fork of facebook/react-native/
The reasons for this fork to exist currently are 3 fold.
- Provide a staging ground for changes that Microsoft is submitting back to the main Facebook repo, such that our internal apps can share and validate these changes while the PRs go through the standard merge process with Facebook.
- A holding ground for our implementation of react-native for macOS. -- The eventual plan is to refactor a bunch of code within facebook/react-native to allow the macOS code to be implemented as an out of tree platform that works with the core react-native package. But currently the implementation shares so much logic with the iOS platform that it would involve a lot of code duplication to move it out. This process will take a while to work through but is the eventual goal.
- Hold various changes that we have made internally to support our apps, which we hope to revert as we update our internal code. But we are putting it all out here since other projects require this changes exist for now.
The eventual goal is for this fork to stop existing, or certainly have a much smaller delta between this fork and facebook/react-native.
React Native · 
Learn once, write anywhere: Build mobile apps with React.
See the official React Native website for an introduction to React Native.
Requirements
Supported target operating systems are >= Android 4.1 (API 16) and >= iOS 9.0. You may use Windows, macOS, or Linux as your development operating system, though building and running iOS apps is limited to macOS by default (tools like Expo can be used to get around this).
Building your first React Native app
Follow the Getting Started guide. The recommended way to install React Native depends on your project. Here you can find short guides for the most common scenarios:
How React Native works
React Native lets you build mobile apps using JavaScript. It uses the same design as React, letting you compose a rich mobile UI from declarative components.
With React Native, you don't build a "mobile web app", an "HTML5 app", or a "hybrid app". You build a real mobile app that's indistinguishable from an app built using Objective-C, Java, Kotlin, or Swift. React Native uses the same fundamental UI building blocks as regular iOS and Android apps. You just put those building blocks together using JavaScript and React.
React Native lets you build your app faster. Instead of recompiling, you can reload your app instantly. With hot reloading, you can even run new code while retaining your application state.
React Native combines smoothly with components written in Objective-C, Java, Kotlin, or Swift. It's simple to drop down to native code if you need to optimize a few aspects of your application. It's also easy to build part of your app in React Native, and part of your app using native code directly - that's how the Facebook app works.
The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native.
Full documentation
The full documentation for React Native can be found on our website. The source for the React Native documentation and website is hosted on a separate repo, https://github.com/facebook/react-native-website.
The React Native documentation only discusses the components, APIs, and topics specific to React Native (React on iOS and Android). For further documentation on the React API that is shared between React Native and React DOM, refer to the React documentation.
Join the React Native community
- Website: https://facebook.github.io/react-native
- Twitter: https://twitter.com/reactnative
- Discussion: https://discuss.reactjs.org/
See the CONTRIBUTING file for how to help out.
License
React Native is MIT licensed, as found in the LICENSE file.
React Native documentation is Creative Commons licensed, as found in the LICENSE-docs file.