microsoft
/
react-native-macos
зеркало из https://github.com/microsoft/react-native-macos.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
react-native-macos/package.json

193 строки
7.3 KiB
JSON
Исходник Обычный вид История

[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 07:10:52 +03:00
{
[ReactNative] Remove react-native/package.json
2015-03-23 06:32:49 +03:00
"name": "react-native",
Update version number in repo for ecosystem compatibility Summary:In https://github.com/facebook/react-native/pull/5241 ide updated the version number to be a fake one so that people wouldn't send in PRs just bumping the version. Unfortunately, this leads to compatibility issues when developing against `master` with 3rd-party components that declare React Native as a `peerDependency`. For example, I'm using [react-native-orientation](https://github.com/yamill/react-native-orientation) which has a peerDependency of `"react-native": ">=0.5"`. I see a few ways to deal with this: 1. Only develop against the releases on npm, not git snapshots. 2. Ask ecosystem projects to not include a minimum version of `react-native` in their peerDependencies. 3. Track the RN release numbers in the git repository (eg it would be 0.19 right now). 4. Make the release number on master huge (1000 in this PR) so it's obviously a fake number but will still comply with >= checks. I don't think option 2 is good because it's reasonable for a package author to want to specify a minimum R Closes https://github.com/facebook/react-native/pull/5556 Differential Revision: D3110274 fb-gh-sync-id: 8638157d44ee99945337fbf585936b50699f0341 fbshipit-source-id: 8638157d44ee99945337fbf585936b50699f0341
2016-03-29 22:32:57 +03:00
"version": "1000.0.0",
Add bin to package.json (#24187) Summary: Add `bin` field to `package.json`. It will be required for initializing `react-native` with `npx`: ```sh npx react-native init ProjectName ``` [General] [Added] - Added bin to package.json cc thymikee cpojer Pull Request resolved: https://github.com/facebook/react-native/pull/24187 Differential Revision: D14672211 Pulled By: hramos fbshipit-source-id: 9e8633213bba4b3f02d20b54391a04d0a1a19376
2019-03-29 00:14:15 +03:00
"bin": "./cli.js",
[React Native] Sync from github
2015-03-28 08:18:47 +03:00
"description": "A framework for building native apps using React",
Update to MIT license Summary: Manual changes. Reviewed By: TheSavior, yungsters Differential Revision: D7012152 fbshipit-source-id: de7459be3db13c687868b45059856f125c4f2eb1
2018-02-17 05:25:02 +03:00
"license": "MIT",
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 07:10:52 +03:00
"repository": {
"type": "git",
"url": "git@github.com:facebook/react-native.git"
},
Add Node >= 4 requirement to package.json and packager/package.json Summary: When you try to install these with old Node you'll now get a message from npm telling you that your version of Node is old. This makes it more obvious what's going on and hopefully reduces the number of issues we get due to people using an old version of Node. Closes https://github.com/facebook/react-native/pull/3296 Reviewed By: @​svcscm Differential Revision: D2526500 Pulled By: @vjeux fb-gh-sync-id: 036e10a8d1819ea082e419cd328a458202f0e071
2015-10-10 00:42:33 +03:00
"engines": {
Update engines to node >=10 (#28174) Summary: v8 dropped out of LTS support, updating the package.json engines to node v10. ## Changelog [General] [Changed] - Bump supported Node engines to >= 10 Pull Request resolved: https://github.com/facebook/react-native/pull/28174 Reviewed By: cpojer Differential Revision: D20107977 Pulled By: hramos fbshipit-source-id: 795cce79eb32f34e19d20bb8684b898b26e07228
2020-02-27 18:03:07 +03:00
"node": ">=10"
Add Node >= 4 requirement to package.json and packager/package.json Summary: When you try to install these with old Node you'll now get a message from npm telling you that your version of Node is old. This makes it more obvious what's going on and hopefully reduces the number of issues we get due to people using an old version of Node. Closes https://github.com/facebook/react-native/pull/3296 Reviewed By: @​svcscm Differential Revision: D2526500 Pulled By: @vjeux fb-gh-sync-id: 036e10a8d1819ea082e419cd328a458202f0e071
2015-10-10 00:42:33 +03:00
},
Fix test ci reporter (#22749) Summary: Hi Team! This PR fixes #22741 Thanks for labeling as Good First Issue! Changelog: ---------- [General] [Fixed] - fix deprecation warning of testResultsProcessor flag in test-ci Pull Request resolved: https://github.com/facebook/react-native/pull/22749 Differential Revision: D13542419 Pulled By: hramos fbshipit-source-id: 84f33329a6b9431ed1db843a99e7db7dbeda5361
2018-12-22 04:34:07 +03:00
"jest-junit": {
"outputDirectory": "reports/junit",
"outputName": "js-test-results.xml"
},
[ReactNative] Update package.json to be npm-ready
2015-03-26 04:18:41 +03:00
"files": [
Move `react-native-implementation.js` to `index.js` Summary: I am unsure whether there was a reason not to use an `index.js` file from the beginning. It always struck me as confusing and odd to have the main API hidden in a folder somewhere. This changes RN to use the standard `index.js` file that is common in almost all JavaScript packages. Reviewed By: yungsters, rubennorte Differential Revision: D17314423 fbshipit-source-id: 10eaf4fddd41e91163de7d10c0879b623dab00d7
2019-09-12 13:26:46 +03:00
"!template/node_modules",
"!template/package-lock.json",
"!template/yarn.lock",
Adding Jest preset so that people can configure Jest using react-native as preset Reviewed By: cpojer Differential Revision: D4081817 fbshipit-source-id: 43cf2ec467ea69651705162b6a58e0b3f1ad1dbf
2016-10-31 22:52:30 +03:00
".flowconfig",
Consume Android artifacts from npm Summary: This lets us say goodbye to Maven Central. This will greatly simplify and speed up the release process as releasing Android artifacts to Maven Central adds a lot of [complexity](https://github.com/facebook/react-native/blob/master/Releases-publish.md) and delays the whole release by several hours when we have to wait for the artifacts to propagate. This diff assumes there's a local Maven repo at `node_modules/react-native/android`. The second part once this lands is to change our `release.sh` script to output the artifacts under `react-native/android` before publishing to npm. This adds 3.7MB to the size of `node_modules` of any app. However, we just download eagerly what we'd normally download later via Gradle. **Test plan** Released RN including a local Maven repo into Sinopia: $ cd react-native # Updated version in gradle.properties to 0.21.0 $ ./gradlew ReactAndroid:installArchives # Moved everything in .m2/repository/com/facebook/react to react-native/android $ ls react-native/android com/facebook/react/react-native/0.21.0/react-native-0.21.0.aar com/facebook/react/react-native/0.21.0/react-native-0.21.0.pom com/facebook/react/react-native/maven-metadata.xml ... # Set version in package.json to 0.21.0 $ npm set registry http://localhost:4873/ $ npm publish Created and ran an app: $ cd /tmp $ react-native init AndroidNpm $ cd AndroidNpm $ react-native run-android It worked. Checked that we're using the artifacts from node_modules/react-native/android: $ cd android $ ./gradlew app:dependencies compile - Classpath for compiling the main sources. +--- com.android.support:appcompat-v7:23.0.1 | \--- com.android.support:support-v4:23.0.1 | \--- com.android.support:support-annotations:23.0.1 \--- com.facebook.react:react-native:+ -> 0.21.0 +--- com.google.code.findbugs:jsr305:3.0.0 +--- com.facebook.stetho:stetho-okhttp:1.2.0 ... Checked that Android Studio can find the source jars (you can navigate to RN sources in Android Studio). Opened the new project as described in the [docs](https://facebook.github.io/react-native/docs/android-setup.html#editing-your-app-s-java-code-in-android-studio). public Reviewed By: bestander Differential Revision: D2912557 fb-gh-sync-id: 251c180518a3fb9bb8e80963b236e982d65533be shipit-source-id: 251c180518a3fb9bb8e80963b236e982d65533be
2016-02-09 17:36:30 +03:00
"android",
[ReactNative] Update package.json to be npm-ready
2015-03-26 04:18:41 +03:00
"cli.js",
Adding Jest preset so that people can configure Jest using react-native as preset Reviewed By: cpojer Differential Revision: D4081817 fbshipit-source-id: 43cf2ec467ea69651705162b6a58e0b3f1ad1dbf
2016-10-31 22:52:30 +03:00
"flow",
Move `react-native-implementation.js` to `index.js` Summary: I am unsure whether there was a reason not to use an `index.js` file from the beginning. It always struck me as confusing and odd to have the main API hidden in a folder somewhere. This changes RN to use the standard `index.js` file that is common in almost all JavaScript packages. Reviewed By: yungsters, rubennorte Differential Revision: D17314423 fbshipit-source-id: 10eaf4fddd41e91163de7d10c0879b623dab00d7
2019-09-12 13:26:46 +03:00
"index.js",
[ReactNative] Update package.json to be npm-ready
2015-03-26 04:18:41 +03:00
"init.sh",
Move `react-native-implementation.js` to `index.js` Summary: I am unsure whether there was a reason not to use an `index.js` file from the beginning. It always struck me as confusing and odd to have the main API hidden in a folder somewhere. This changes RN to use the standard `index.js` file that is common in almost all JavaScript packages. Reviewed By: yungsters, rubennorte Differential Revision: D17314423 fbshipit-source-id: 10eaf4fddd41e91163de7d10c0879b623dab00d7
2019-09-12 13:26:46 +03:00
"interface.js",
fix: use `require.resolve` in `jest-preset` (#22972) Summary: The current way the Jest preset work requires the different files to be in `<rootDir>/node_modules/react-native`. This is not necessarily true - especially in monorepoes. If we instead do `require.resolve`, we do not need to do `rootDir` replacement in Jest. Having a JS file as preset has been supported since Jest 23.0.0: https://github.com/facebook/jest/pull/6185 Changelog: ---------- [General] [Fixed] - use `require.resolve` in `jest-preset` Pull Request resolved: https://github.com/facebook/react-native/pull/22972 Differential Revision: D13662758 Pulled By: hramos fbshipit-source-id: ca79b5b89d9d05c6fe639b0d88619858e8d05da7
2019-01-15 03:28:55 +03:00
"jest-preset.js",
Adding Jest preset so that people can configure Jest using react-native as preset Reviewed By: cpojer Differential Revision: D4081817 fbshipit-source-id: 43cf2ec467ea69651705162b6a58e0b3f1ad1dbf
2016-10-31 22:52:30 +03:00
"jest",
"lib",
"Libraries",
[ReactNative] Update package.json to be npm-ready
2015-03-26 04:18:41 +03:00
"LICENSE",
Move `react-native-implementation.js` to `index.js` Summary: I am unsure whether there was a reason not to use an `index.js` file from the beginning. It always struck me as confusing and odd to have the main API hidden in a folder somewhere. This changes RN to use the standard `index.js` file that is common in almost all JavaScript packages. Reviewed By: yungsters, rubennorte Differential Revision: D17314423 fbshipit-source-id: 10eaf4fddd41e91163de7d10c0879b623dab00d7
2019-09-12 13:26:46 +03:00
"local-cli",
Adding Jest preset so that people can configure Jest using react-native as preset Reviewed By: cpojer Differential Revision: D4081817 fbshipit-source-id: 43cf2ec467ea69651705162b6a58e0b3f1ad1dbf
2016-10-31 22:52:30 +03:00
"packager",
Move `react-native-implementation.js` to `index.js` Summary: I am unsure whether there was a reason not to use an `index.js` file from the beginning. It always struck me as confusing and odd to have the main API hidden in a folder somewhere. This changes RN to use the standard `index.js` file that is common in almost all JavaScript packages. Reviewed By: yungsters, rubennorte Differential Revision: D17314423 fbshipit-source-id: 10eaf4fddd41e91163de7d10c0879b623dab00d7
2019-09-12 13:26:46 +03:00
"React-Core.podspec",
- Publish `react-native.config.js` (#25436) Summary: Looks we forgot to add this file to publish list. By adding it, we can remove some code in CLI that special-cases `react-native` package, since it now announces itself as a proper platform. cc kelset, we'd like to have this cherry-picked for 0.60. ## Changelog [Internal] [Fixed] - Publish `react-native.config.js` Pull Request resolved: https://github.com/facebook/react-native/pull/25436 Test Plan: `npm pack` shows `react-native.config.js` Differential Revision: D16071113 Pulled By: cpojer fbshipit-source-id: df18affbb9a0ad7f2cfdd1a4cc93191aa5ffadeb
2019-07-01 12:35:42 +03:00
"react-native.config.js",
Adding Jest preset so that people can configure Jest using react-native as preset Reviewed By: cpojer Differential Revision: D4081817 fbshipit-source-id: 43cf2ec467ea69651705162b6a58e0b3f1ad1dbf
2016-10-31 22:52:30 +03:00
"react.gradle",
"React.podspec",
"React",
"ReactAndroid",
"ReactCommon",
Ship third-party-podspecs in the npm package Summary: Hi, Today I upgraded from RN 0.44 to 0.45.0-rc.0 and noticed I add to include either `CxxBridge` or `BatchedBridge` in the React subspecs in my Podfile to get my project to compile again (https://github.com/facebook/react-native/issues/13010). Adding `BatchedBridge` works fine. However I wanted to try `CxxBridge` as described in https://github.com/facebook/react-native/commit/5aca739cc25949eebc04a0309c2944f92b5b5391 but couldn't do it since the required `third-party-podspecs` folder with `Folly.podspec`, `GLog.podspec` and `DoubleConversion.podspec` hadn't been included in the npm release. So here is the fix for that. It should be included in the next 0.45.0-rc release. Let me know what you think. Closes https://github.com/facebook/react-native/pull/13922 Differential Revision: D5051477 Pulled By: javache fbshipit-source-id: e5c527f1ee9c84734d3e3a3d85ec3f1e5d648bef
2017-05-12 12:50:12 +03:00
"README.md",
Move `react-native-implementation.js` to `index.js` Summary: I am unsure whether there was a reason not to use an `index.js` file from the beginning. It always struck me as confusing and odd to have the main API hidden in a folder somewhere. This changes RN to use the standard `index.js` file that is common in almost all JavaScript packages. Reviewed By: yungsters, rubennorte Differential Revision: D17314423 fbshipit-source-id: 10eaf4fddd41e91163de7d10c0879b623dab00d7
2019-09-12 13:26:46 +03:00
"rn-get-polyfills.js",
Rename autolinking-ios.rb script and bring RNTester and template in line. (#28077) Summary: Make the script ready for picking in 0.62.0-rc.3. * Rename the script to remove ambiguity. “autolinking” is a CLI feature where 3rd-party pods are automatically discovered: https://github.com/react-native-community/cli/blob/master/docs/autolinking.md * Make the Flipper version of the pods configurable, as requested [here](https://github.com/facebook/react-native/pull/28044#discussion_r378662636). * Make RNTester’s Podfile use the same form as the template–including enabling Flipper by moving the CPP define into the right place in the Xcode project and out of the Podfile. * Get rid of Podfile.lock thrashing by making the default CDN spec source explicit. ## Changelog [iOS] [Changed] - Disambiguate autolinking-ios.rb script from CLI’s “autolinking” feature and bring RNTester & template in line. Pull Request resolved: https://github.com/facebook/react-native/pull/28077 Test Plan: RNTester builds, as does a new application. Reviewed By: PeteTheHeat Differential Revision: D19956392 Pulled By: TheSavior fbshipit-source-id: 6c800ddb646b49fc45c088978e2794cd7b60ea48
2020-02-20 02:15:19 +03:00
"scripts/react_native_pods.rb",
Move `react-native-implementation.js` to `index.js` Summary: I am unsure whether there was a reason not to use an `index.js` file from the beginning. It always struck me as confusing and odd to have the main API hidden in a folder somewhere. This changes RN to use the standard `index.js` file that is common in almost all JavaScript packages. Reviewed By: yungsters, rubennorte Differential Revision: D17314423 fbshipit-source-id: 10eaf4fddd41e91163de7d10c0879b623dab00d7
2019-09-12 13:26:46 +03:00
"scripts/compose-source-maps.js",
"scripts/ios-configure-glog.sh",
"scripts/launchPackager.bat",
"scripts/launchPackager.command",
"scripts/node-binary.sh",
"scripts/packager.sh",
"scripts/react-native-xcode.sh",
Rename ios project name with new template (#24292) Summary: With new `init` implementation we replace all occurrences of the project name (`HelloWorld`) inside `ios` and `android` directories. For some reason, a product name field in `ios` was named wrongly. This shouldn't impact initialization using `global-cli` [iOS] [Fixed] - Change productName in iOS in new init. Pull Request resolved: https://github.com/facebook/react-native/pull/24292 Differential Revision: D14749249 Pulled By: cpojer fbshipit-source-id: aaf4294ab23180770aac3075789d3ffb4d5a4f3f
2019-04-03 19:49:38 +03:00
"template.config.js",
Move `react-native-implementation.js` to `index.js` Summary: I am unsure whether there was a reason not to use an `index.js` file from the beginning. It always struck me as confusing and odd to have the main API hidden in a folder somewhere. This changes RN to use the standard `index.js` file that is common in almost all JavaScript packages. Reviewed By: yungsters, rubennorte Differential Revision: D17314423 fbshipit-source-id: 10eaf4fddd41e91163de7d10c0879b623dab00d7
2019-09-12 13:26:46 +03:00
"template",
"third-party-podspecs"
[ReactNative] Update package.json to be npm-ready
2015-03-26 04:18:41 +03:00
],
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 07:10:52 +03:00
"scripts": {
Use latest React Native CLI (#24517) Summary: Updates React Native to use latest CLI. Changes: - No more `--reactNativePath`, define it once in the configuration file. This reverts the previous PR that added this flag - Add `platforms` and `commands` - React Native now defines platform like any other package. There's no longer concept of "out-of-tree" platform. All are treated equally. If React Native works, any other platform will work too. - Updates `jest/hasteImpl.js` to use public CLI interface (`loadConfig`) instead of `findPlugins` and removes a weird conditional that checks for CI presence. [INTERNAL] - Update React Native CLI Pull Request resolved: https://github.com/facebook/react-native/pull/24517 Differential Revision: D15044762 Pulled By: cpojer fbshipit-source-id: 379b61e842e619312c542173219a7d326663cf24
2019-04-24 14:44:27 +03:00
"start": "react-native start",
Update to 14.0 Reviewed By: kassens Differential Revision: D3627753 fbshipit-source-id: 35b8246c8cb61e60908d8c233a6e72063bf67096
2016-07-28 08:02:42 +03:00
"test": "jest",
Fix test ci reporter (#22749) Summary: Hi Team! This PR fixes #22741 Thanks for labeling as Good First Issue! Changelog: ---------- [General] [Fixed] - fix deprecation warning of testResultsProcessor flag in test-ci Pull Request resolved: https://github.com/facebook/react-native/pull/22749 Differential Revision: D13542419 Pulled By: hramos fbshipit-source-id: 84f33329a6b9431ed1db843a99e7db7dbeda5361
2018-12-22 04:34:07 +03:00
"test-ci": "jest --maxWorkers=2 --ci --reporters=\"default\" --reporters=\"jest-junit\"",
Use flow-bin to typecheck locally, update ESLint to 2.0 Summary:Using local version of the Flow make it easy to have project specific version instead of relying on the user to have the correct version installed globally. For example, React Native uses an older version of Flow, while I have the latest version installed. Now I cannot typecheck the code because my version doesn't match the `.flowconfig`. **Test plan (required)** Run `npm run lint` and `npm run flow` to run `eslint` and `flow`. cc bestander mkonicek Closes https://github.com/facebook/react-native/pull/6145 Reviewed By: dmmiller Differential Revision: D2976616 Pulled By: bestander fb-gh-sync-id: bb08f6f8ceb09f644ec1d45c40b4cb7a9d3cfef5 shipit-source-id: bb08f6f8ceb09f644ec1d45c40b4cb7a9d3cfef5
2016-03-03 15:15:15 +03:00
"flow": "flow",
package.json: Add flow check commands for iOS and Android (#21326) Summary: This PR adds these two scripts to `package.json`: * `flow-check-ios` - for running `flow check` on `.ios.js` files * `flow-check-android` - for running `flow check` on `.android.js` files The Android command makes use of the new `--flowconfig-name` option added to Flow in `0.80.0` Pull Request resolved: https://github.com/facebook/react-native/pull/21326 Differential Revision: D10055702 Pulled By: hramos fbshipit-source-id: e647f8d2995da0a9bd6af242218819fd5745df63
2018-09-27 02:49:07 +03:00
"flow-check-ios": "flow check",
"flow-check-android": "flow check --flowconfig-name .flowconfig.android",
Run eslint on all js files Reviewed By: zertosh Differential Revision: D5405047 fbshipit-source-id: 5ade9d8beb3688d8bb08a208709c0dbf1ec671b2
2017-07-12 23:48:49 +03:00
"lint": "eslint .",
Bots cleanup, avoid leaving inline reviews when N>5 (#24923) Summary: This PR cleans up some of our GitHub bots. The overall goal is to make the contribution process just a tad nicer. ### analysis-bot * The bot will continue leaving GitHub Reviews when it finds lint issues, but will abstain from leaving inline comments if they would exceed 5 in number. * The review comment left by the bot has instructions on how to reproduce the lint issues locally. This will educate PR authors on how to run lint and fix the issues without unnecessarily spamming the PR with 50+ comments, while still providing useful reviews to authors when only a handful of lint issues slip by. * Code moved to `bots/` directory for ease of discovery and co-location with pull-bot. * Added `yarn lint-ci` command. This seems like the right choice: it's running `yarn lint` and other linters, and it is only intended to run on CI. * It's still possible to run `yarn lint-ci` locally, though the script will stop short of posting a review to GitHub unless the necessary envvars are provided. * Added `yarn shellcheck` command. This can be run locally, though it requires `shellcheck` to be installed. * Outside of this PR, I added instructions on using shellcheck to https://github.com/facebook/react-native/wiki/Development-Dependencies * Updated Circle CI config to use these new commands, and streamlined the `analyze_pr` step. * Documented analysis-bot in `bots/README.md`. ### pull-bot * Bumped `danger-js` dependency. No breaking changes found in this minor bump from what I can tell. * Documented pull-bot in `bots/README.md`. ### misc * PR template: don't use jargon. ## Changelog [Internal] [Changed] - GitHub Bots cleanup Pull Request resolved: https://github.com/facebook/react-native/pull/24923 Differential Revision: D15399744 Pulled By: hramos fbshipit-source-id: 32632e775f8554424072270e3f98542de84bfb8c
2019-05-22 05:35:40 +03:00
"lint-ci": "./scripts/circleci/analyze_code.sh && yarn shellcheck",
"shellcheck": "./scripts/circleci/analyze_scripts.sh",
add clang-format to current toolchain (#23434) Summary: add `clang-format` toolchain. we have 2558 files need to process in current task. cc cpojer empyrical shergin matthargett Pull Request resolved: https://github.com/facebook/react-native/pull/23434 Differential Revision: D14067789 Pulled By: cpojer fbshipit-source-id: ddf812fc9579068ebb850bacedde6675376f18b7
2019-02-18 03:00:18 +03:00
"clang-format": "clang-format -i --glob=*/**/*.{h,cpp,m,mm}",
"format": "npm run prettier && npm run clang-format",
add yml to prettier list.Fixes #23426 (#23953) Summary: add yml to prettier list. Related issue: https://github.com/facebook/react-native/issues/23426. [GENERAL] [Changed] - add yml to prettier list Pull Request resolved: https://github.com/facebook/react-native/pull/23953 Differential Revision: D14479402 Pulled By: cpojer fbshipit-source-id: 2cf2e78b6b418908bc909f7401e2fef0e285d9f8
2019-03-15 18:02:30 +03:00
"prettier": "prettier --write \"./**/*.{js,md,yml}\"",
"format-check": "prettier --list-different \"./**/*.{js,md,yml}\"",
migrate ci to official docker (#21477) Summary: Simplify current build and offer it to community as official docker. I have also created an [rfc](https://github.com/react-native-community/discussions-and-proposals/pull/36). pass all current ci. none [GENERAL] [INTERNAL] [CI] - migrate ci to official docker Pull Request resolved: https://github.com/facebook/react-native/pull/21477 Differential Revision: D13801696 Pulled By: cpojer fbshipit-source-id: fa235cf21ab5af2c87eb3c1a14788fab01c71ccf
2019-01-24 17:22:28 +03:00
"docker-setup-android": "docker pull reactnativecommunity/react-native-android",
Move Dockerfiles into Circle CI directory (#23677) Summary: This is an effort to clean up the root of the repository. Everything related to Docker is being moved to the `.circleci` directory, as these images are used as part of the Circle CI 2.0 tests on Android. [GENERAL] [Changed] - Moved Dockerfiles into .circleci directory Pull Request resolved: https://github.com/facebook/react-native/pull/23677 Differential Revision: D14253735 Pulled By: cpojer fbshipit-source-id: 4d482d531a71b8259b09c001b310d82ce5349b87
2019-02-28 06:27:36 +03:00
"docker-build-android": "docker build -t reactnativeci/android -f .circleci/Dockerfiles/Dockerfile.android .",
"test-android-run-instrumentation": "docker run --cap-add=SYS_ADMIN -it reactnativeci/android bash .circleci/Dockerfiles/scripts/run-android-docker-instrumentation-tests.sh",
"test-android-run-unit": "docker run --cap-add=SYS_ADMIN -it reactnativeci/android bash .circleci/Dockerfiles/scripts/run-android-docker-unit-tests.sh",
"test-android-run-e2e": "docker run --privileged -it reactnativeci/android bash .circleci/Dockerfiles/scripts/run-ci-e2e-tests.sh --android --js",
Update Android Docker images Summary: yarn docker-build-android-base yarn docker-build-android [INTERNAL] [MINOR] [ContainerShip] - Bump versions in Dockerfiles Closes https://github.com/facebook/react-native/pull/18597 Differential Revision: D7433542 Pulled By: hramos fbshipit-source-id: 5ec7496c84203a0ed20ef3875ac3d367914a0e80
2018-03-29 21:29:09 +03:00
"test-android-all": "yarn run docker-build-android && yarn run test-android-run-unit && yarn run test-android-run-instrumentation && yarn run test-android-run-e2e",
"test-android-instrumentation": "yarn run docker-build-android && yarn run test-android-run-instrumentation",
"test-android-unit": "yarn run docker-build-android && yarn run test-android-run-unit",
Initial Detox E2E iOS configuration to be run on RNTester (#20235) Summary: This PR adds initial setup for Detox E2E iOS and some tests for ButtonExample. Pull Request resolved: https://github.com/facebook/react-native/pull/20235 Reviewed By: hramos Differential Revision: D8924525 Pulled By: TheSavior fbshipit-source-id: 8117fc1559c2e9cb831f7b081aa8f4ddc8ba7401
2018-07-31 00:25:49 +03:00
"test-android-e2e": "yarn run docker-build-android && yarn run test-android-run-e2e",
"build-ios-e2e": "detox build -c ios.sim.release",
Add test-ios command to package.json (#24985) Summary: There is currently no entry point for running the RNTester tests in package.json. This adds a test-ios command which leverages the existing objc-test-ios.sh script. With this change in place, our documentation for running tests locally can be simplified and made consistent with how JavaScript tests are run (yarn test). ## Changelog [General] [Added] - Add a test-ios command to run iOS RNTester tests locally Pull Request resolved: https://github.com/facebook/react-native/pull/24985 Differential Revision: D15449399 Pulled By: cpojer fbshipit-source-id: 63f7ad653d23c5601a11fc9d27a39b4987fccaad
2019-05-22 16:53:20 +03:00
"test-ios-e2e": "detox test -c ios.sim.release RNTester/e2e",
Use CocoaPods-based RNTesterPods for iOS tests (#25416) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/25416 Use CocoaPods-based RNTesterPods workspace to run iOS unit tests and integration tests. This is necessary as new iOS projects now use CocoaPods by default. CocoaPods also powers the new package auto-linking feature. In order to provide test coverage for this new default configuration, our iOS tests are being migrated to use a CocoaPods-managed RNTester workspace. This applies to both Circle CI, and Sandcastle. Changelog: [iOS] [Changed] - Use RNTesterPods for iOS Tests Reviewed By: fkgozali Differential Revision: D16052466 fbshipit-source-id: 724b0c51008882d3c06a9074693fe23e74abe86b
2019-06-29 05:12:42 +03:00
"test-ios": "./scripts/objc-test.sh test"
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 07:10:52 +03:00
},
Fixed package.json peerDependencies Reviewed By: sophiebits Differential Revision: D5860751 fbshipit-source-id: 634ccf22d40bf80eabed467cb1c874f5b02c4f8d
2017-09-20 01:39:18 +03:00
"peerDependencies": {
Update React package Summary: This just updates the `react` package to the latest stable version. We updated it to experimental internally earlier so this brings the open source version to the latest before the branch cut. This doesn't include any breaking changes. Changelog: [General][Changed] - Update to React 16.13.1 Reviewed By: cpojer Differential Revision: D20642909 fbshipit-source-id: 68a4c74bfe72f1abdb33b0b9071a4f4e8e568318
2020-03-25 14:14:22 +03:00
"react": "16.13.1"
Fixed package.json peerDependencies Reviewed By: sophiebits Differential Revision: D5860751 fbshipit-source-id: 634ccf22d40bf80eabed467cb1c874f5b02c4f8d
2017-09-20 01:39:18 +03:00
},
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 07:10:52 +03:00
"dependencies": {
Remove global babelHelpers and regenerator (#21283) Summary: Follow up to https://github.com/facebook/metro/commit/8932a9caa8f9ffe82160f2da25342a0bde3bbb26 Babel helpers and regenerator runtime will be imported automatically from `babel/runtime`. We still need to add the global regeneratorRuntime for jest tests since we disable babel-runtime currently. Pull Request resolved: https://github.com/facebook/react-native/pull/21283 Reviewed By: mjesun Differential Revision: D10010963 Pulled By: rafeca fbshipit-source-id: da5e23dd901f8f8940d46816b4fc9290d0e28c76
2018-09-26 19:48:35 +03:00
"@babel/runtime": "^7.0.0",
chore: update CLI to the latest version (#28623) Summary: Bumps CLI to the latest version, needed by https://github.com/facebook/react-native/pull/28572 to work. ## Changelog [INTERNAL] - Bump CLI to latest Pull Request resolved: https://github.com/facebook/react-native/pull/28623 Reviewed By: hramos Differential Revision: D21017766 Pulled By: cpojer fbshipit-source-id: 62a873923c58f8752edb0394db7e6dfceed92485
2020-04-16 12:54:06 +03:00
"@react-native-community/cli": "^4.7.0",
"@react-native-community/cli-platform-android": "^4.7.0",
"@react-native-community/cli-platform-ios": "^4.7.0",
Add support for cancelling fetch requests with AbortController (#24419) Summary: This adds https://github.com/mysticatea/abort-controller to polyfill [AbortController](https://developer.mozilla.org/en-US/docs/Web/API/AbortController). This is used to cancel requests when using `fetch`. This also updates `event-target-shim` to 5.0 to make sure we only have one version of this dependency. This updates required adding a polyfill for `console.assert` which is used by the new version. I made one based on https://github.com/gskinner/console-polyfill/blob/master/console.js#L74. The polyfill is very small, especially since we already use `event-target-shim` so I think it makes sense to include in core. Depends on #24418 so that the fetch polyfill supports the `signal` parameter. Fixes #18115 [General] [Added] - Add support for cancelling fetch requests with AbortController Pull Request resolved: https://github.com/facebook/react-native/pull/24419 Differential Revision: D14912858 Pulled By: cpojer fbshipit-source-id: 8a6402910398db51e2f3e3262f07aabdf68fcf72
2019-04-15 21:59:14 +03:00
"abort-controller": "^3.0.0",
Syntax highlighting for LogBox Code Frames Summary: This diff adds syntax highlighting to LogBox CodeFrames. It works by turning Ansi codes into "JSON" (it's actually just a JS object but the third-party API uses JSON as terminology) and then turning that into `<Text>` elements. The syntax theme is called Afterglow and I took it from https://iterm2colorschemes.com/. Happy for anyone who wants to further tweak it! I installed this into iTerm and extracted the colors from there as it has a color picker and the labels directly map to the color classes exposed by the `anser` package. Changelog: [Internal] (Note: this ignores all push blocking failures!) Reviewed By: rickhanlonii Differential Revision: D18618897 fbshipit-source-id: 64815619fc482e08b5671f492dabda8c8c0ceca5
2019-11-22 20:06:38 +03:00
"anser": "^1.4.9",
update base64-js version. follow up #6961 Summary: **Motivation** This is originally a follow up of PR #6327 by dewe and jeremyong And mkonicek indicated this should split into a separate PR. Now philikon takes over #6327 as #6961 **Test Plan:** According to #6961 and #6889 Load WebSocketExample in UIExplorer app and start websocket test server script and test sending binary data on both iOS and Android Closes https://github.com/facebook/react-native/pull/6937 Reviewed By: javache Differential Revision: D3669596 Pulled By: mkonicek fbshipit-source-id: 342e29eb34de882bcbd9f297aab71dd6bb236748
2016-09-20 15:41:29 +03:00
"base64-js": "^1.1.2",
Add support for cancelling fetch requests with AbortController (#24419) Summary: This adds https://github.com/mysticatea/abort-controller to polyfill [AbortController](https://developer.mozilla.org/en-US/docs/Web/API/AbortController). This is used to cancel requests when using `fetch`. This also updates `event-target-shim` to 5.0 to make sure we only have one version of this dependency. This updates required adding a polyfill for `console.assert` which is used by the new version. I made one based on https://github.com/gskinner/console-polyfill/blob/master/console.js#L74. The polyfill is very small, especially since we already use `event-target-shim` so I think it makes sense to include in core. Depends on #24418 so that the fetch polyfill supports the `signal` parameter. Fixes #18115 [General] [Added] - Add support for cancelling fetch requests with AbortController Pull Request resolved: https://github.com/facebook/react-native/pull/24419 Differential Revision: D14912858 Pulled By: cpojer fbshipit-source-id: 8a6402910398db51e2f3e3262f07aabdf68fcf72
2019-04-15 21:59:14 +03:00
"event-target-shim": "^5.0.1",
Remove ListView and SwipeableListView from React Native Summary: This diff removes ListView and SwipeableListView from React Native: * Removes the code and all examples * Removes the exports on `react-native-implementation` but leaves an error message in dev mode only * Uses `deprecated-react-native-listview` for `ListView` and `deprecated-react-native-swipeable-listview` for `SwipeableListView` Both ListView and SwipeableListView are now fully removed from React Native in open source and we will continue to use the deprecated packages internally. Reviewed By: TheSavior Differential Revision: D14181708 fbshipit-source-id: 5030c33791f998567de058fee934449c16fa1d54
2019-02-26 09:37:18 +03:00
"fbjs": "^1.0.0",
Upgrade fbjs-scripts to 1.1.0 Summary: This new version uses paths relative to the `rootDir` option to compute cache keys, so it is compatible with remote caching. Reviewed By: rickhanlonii Differential Revision: D14241858 fbshipit-source-id: fbf244bbf389bf873fb8a42f35c9b023fb06182f
2019-02-28 20:42:56 +03:00
"fbjs-scripts": "^1.1.0",
Upgrade Hermes dependency to 0.5.0 Summary: Use the latest published release of hermes-engine. Update RN to invoke `hermesc` instead of `hermes`. Changelog: [Android] [Changed] - Upgraded to Hermes 0.5.0 allow-large-files Reviewed By: mhorowitz Differential Revision: D20998564 fbshipit-source-id: 4824e273bcb044029a5a7e9379f168d3da47da50
2020-04-14 05:45:08 +03:00
"hermes-engine": "~0.5.0",
Use `invariant` instead of `fbjs/lib/invariant` Summary: This is one more step to remove `fbjs` from `react-native-github`. This changes both the internal and external code to use `invariant` from zertosh instead of the copy in fbjs. Reviewed By: yungsters Differential Revision: D13195941 fbshipit-source-id: 73564ca1715110e7da9c7ef56dc57374d61377e0
2018-12-03 10:49:12 +03:00
"invariant": "^2.2.4",
Upgrade jsc-android to r245459 and fix crash on Samsung S7 Edge (#25426) Summary: Upgrade bundled jsc-android that should fix the native JSC crash addressed for https://github.com/facebook/react-native/issues/24261. Major changes after r241213 are: 1. Disable DFG JIT. 2. Upgrade WebKitGTK to 2.24.2, this version includes the [new bytecode format enhancement](https://webkit.org/blog/9329/a-new-bytecode-format-for-javascriptcore/). 3. Workaround LLVM __clear_cache issue which may have some problems on ARM Cortex A-53. For details, please refer to the PRs in https://github.com/react-native-community/jsc-android-buildscripts. In https://github.com/facebook/react-native/issues/24261, there were many experimented JSC deliveries and thank to people in RN community helping me verify the final version which solve the crash issues. ## Changelog [Android] [Fixed] - Upgrade jsc-android to r245459 and fix crash on Samsung S7 Edge Pull Request resolved: https://github.com/facebook/react-native/pull/25426 Test Plan: 1. Run [measure scripts](https://github.com/react-native-community/jsc-android-buildscripts/tree/master/measure) on my Samsung Note 5. 2. Provide an [experimented version](https://www.npmjs.com/package/kudo-ci/jsc-android/v/245459.9000.0) for community who previously reported JSC crash and seems no more crashes happened, see that thread in https://github.com/facebook/react-native/issues/24261 Differential Revision: D16071388 Pulled By: cpojer fbshipit-source-id: 52eb7af61ccd73db21dea1e2e9c58f191a311868
2019-07-01 14:23:07 +03:00
"jsc-android": "^245459.0.0",
Upgrade to Metro 0.59 Summary: Upgrades RN to Metro 0.59. Changelog: [Internal] Metro Upgrade Reviewed By: motiz88 Differential Revision: D20533864 fbshipit-source-id: 3c5fb8e37d2363edf0b9a1a8cfbdefba00763415
2020-03-19 17:18:10 +03:00
"metro-babel-register": "0.59.0",
"metro-react-native-babel-transformer": "0.59.0",
"metro-source-map": "0.59.0",
Upgrade nullthrows to ^1.1.1 Reviewed By: TheSavior Differential Revision: D17552725 fbshipit-source-id: 535faeb8d9ca2b901c5342a48ccba7fc26aebd4f
2019-09-25 20:11:54 +03:00
"nullthrows": "^1.1.1",
Upgrade to Jest 25 Summary: This diff upgrades Jest to the latest version which fixes a bunch of issues with snapshots (therefore allowing me to enable the Pressable-test again). Note that this also affects Metro and various other tooling as they all depend on packages like `jest-worker`, `jest-haste-map` etc. Breaking changes: https://github.com/facebook/jest/blob/master/CHANGELOG.md This diff increases node_modules by 3 MiB, primarily because it causes more duplicates of `source-map` (0.8 MiB for each copy) and packages like `chalk` 3.x (vs 2.x). The base install was 15 MiB bigger and I reduced it to this size by playing around with various manual yarn.lock optimizations. However, D21085929 reduces node_modules by 11 MiB and the Babel upgrade reduced node_modules by 13 MiB. I will subsequently work on reducing the size through other packages as well and I'm working with the Jest folks to get rid of superfluous TypeScript stuff for Jest 26. Other changes in this diff: * Fixed Pressable-test * Blackhole node-notifier: It's large and we don't need it, and also the license may be problematic, see: https://github.com/facebook/jest/pull/8918 * Updated jest-junit (not a Jest package) but blackholed it internally because it is only used for open source CI. * Updated some API calls we use from Jest to account for breaking changes * Made two absolutely egrigious changes to existing product code tests to make them still pass as our match of async/await, fake timers and then/promise using `setImmediate` is tripping up `regenerator` with `Generator is already run` errors in Jest 25. These tests should probably be rewritten. * Locked everything to the same `resolve` version that we were already using, otherwise it was somehow pulling in 1.16 even though nothing internally uses it. Changelog: [General] Update Jest Reviewed By: rickhanlonii Differential Revision: D21064825 fbshipit-source-id: d0011a51355089456718edd84ea0af21fd923a58
2020-04-20 11:23:59 +03:00
"pretty-format": "^25.4.0",
Upgrade Promise polyfill to promise@8.0.3 Summary: Bumps `promise` from 7.1.1 to 8.0.3. The package [hasn't changed significantly between these two versions](https://github.com/then/promise/compare/7.1.1...8.0.3). This is part housekeeping, part making it easier to make PRs to `promise` and then upgrade after they're merged. Changelog: [Internal] Reviewed By: cpojer Differential Revision: D20094814 fbshipit-source-id: d8933bd39aa3e9f9b19e4d5a09b0828ecc032085
2020-03-02 15:53:46 +03:00
"promise": "^8.0.3",
Bundle size reduction (#23968) Summary: With recent activity to extract out non-core things into separate repos, I did an audit of the package.json to see what can be removed, and what packages remain that have newer versions that result in less/smaller javascript code. The goal is to: 1. make developer experience better by removing unneeded dependencies, and 2. eliminate things the app bundler needs to process to make the production app bundle smaller. [internal] [chore] - Remove unneeded packages, bump package versions who now have smaller size Pull Request resolved: https://github.com/facebook/react-native/pull/23968 Differential Revision: D14519070 Pulled By: cpojer fbshipit-source-id: 579f035f925668a34d07293810e3d35a7d0ae076
2019-03-21 21:02:46 +03:00
"prop-types": "^15.7.2",
Upgrade React DevTools 4.0.6 -> 4.6.0 Summary: Upgrading the embedded version of React DevTools, primarily to pull in [this PR](https://github.com/facebook/react/pull/18397) which will reduce the impact of this package on `node_modules` size. # Update process Following a similar process as D15973709, I began by searching for [all of the references](https://our.intern.facebook.com/intern/biggrep/?corpus=xplat&filename=.json&case=false&view=default&extre=&s=%22react-devtools&engine=apr_strmatch&context=false&filter[uninteresting]=false&filter[intern]=false&filter[test]=false&grep_regex=) to the `react-devtools-core` package and updated all v4 usage to to point to the new 4.6.0 release: 1: Manually update "react-devtools-core" versions: ``` js/package.json js/react-native-github/package.json nuclide/package.json sonar/desktop/app/package.json sonar/desktop/plugins/reactdevtools/package.json vscode/modules/vscode-webview/package.json ``` 2: Setup Yarn proxy: ``` yarn config set proxy http://fwdproxy:8080/ yarn config set https-proxy http://fwdproxy:8080 ``` 3: Run "yarn" in each of the above directories. 4: Run the lockfile shell script: ``` ~/xplat/js/scripts/update-oss-yarn-lockfile.sh ``` 5: Update the generated `MOBILE_JS_NODE_MODULE_DEPS.bzl` by running ``` js1 build buckfiles ``` ## Changelog: [General] [Changed] - Upgrade embedded React DevTools backend from v4.0.6 to v4.6.0. Reviewed By: cpojer, gaearon Differential Revision: D20676091 fbshipit-source-id: 99865bdba9bce45e2a7d582d5fb550cfdbeeca3a
2020-03-27 02:41:53 +03:00
"react-devtools-core": "^4.6.0",
Fix Fast Refresh on Fabric Summary: Brings in https://github.com/facebook/react/pull/16302. We were passing roots to a wrong renderer, hence a confusing Fabric-only crash. Reviewed By: JoshuaGross Differential Revision: D16672454 fbshipit-source-id: 115894eb375b50da09d145c57f15c7d5668b926d
2019-08-08 14:38:12 +03:00
"react-refresh": "^0.4.0",
Bundle size reduction (#23968) Summary: With recent activity to extract out non-core things into separate repos, I did an audit of the package.json to see what can be removed, and what packages remain that have newer versions that result in less/smaller javascript code. The goal is to: 1. make developer experience better by removing unneeded dependencies, and 2. eliminate things the app bundler needs to process to make the production app bundle smaller. [internal] [chore] - Remove unneeded packages, bump package versions who now have smaller size Pull Request resolved: https://github.com/facebook/react-native/pull/23968 Differential Revision: D14519070 Pulled By: cpojer fbshipit-source-id: 579f035f925668a34d07293810e3d35a7d0ae076
2019-03-21 21:02:46 +03:00
"regenerator-runtime": "^0.13.2",
Update React package Summary: This just updates the `react` package to the latest stable version. We updated it to experimental internally earlier so this brings the open source version to the latest before the branch cut. This doesn't include any breaking changes. Changelog: [General][Changed] - Update to React 16.13.1 Reviewed By: cpojer Differential Revision: D20642909 fbshipit-source-id: 68a4c74bfe72f1abdb33b0b9071a4f4e8e568318
2020-03-25 14:14:22 +03:00
"scheduler": "0.19.1",
Remove vendored fetch polyfill, update to whatwg-fetch@3.0 (#24418) Summary: The original reason for vendoring the fetch polyfill was to remove the default blob response type but this was reverted. Here's a little history around the fetch polyfill and the blob issue: - Original commit introducing the vendored polyfill: #19333, the goal was to fix a memory leak because our blob implementation doesn't release resources automatically. Not an ideal fix but since the issue was pretty severe and the infra for a proper fix was not in place. - This introduced an issue when downloading images using `fetch` which was fixed by #22063 which re-added the default blob content type. However that re-introduced the original fetch memory leak. - We have better infra now with jsi and I was able to get blob deallocation working, see #24405 Currently the vendored fetch polyfill is useless since it was changed back to the original version. We can just use the npm version again. I also updated to 3.0 which brings better spec compliance and support for cancellation via `AbortController`, https://github.com/github/fetch/releases/tag/v3.0.0. ## Changelog [General] [Changed] - Remove vendored fetch polyfill, update to whatwg-fetch@3.0 Pull Request resolved: https://github.com/facebook/react-native/pull/24418 Differential Revision: D14932683 Pulled By: cpojer fbshipit-source-id: 915e3d25978e8b9d7507ed807e7fba45aa88385a
2019-05-31 11:32:13 +03:00
"stacktrace-parser": "^0.1.3",
useColorScheme hook (#26143) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/26143 A new useColorScheme hook is provided as the preferred way of accessing the user's preferred color scheme (aka Dark Mode). Changelog: [General] [Added] - useColorScheme hook Reviewed By: yungsters Differential Revision: D16860954 fbshipit-source-id: 8a2b6c2624ed7cf431ab331158bc5456cde1f185
2019-08-31 21:21:03 +03:00
"use-subscription": "^1.0.0",
Remove vendored fetch polyfill, update to whatwg-fetch@3.0 (#24418) Summary: The original reason for vendoring the fetch polyfill was to remove the default blob response type but this was reverted. Here's a little history around the fetch polyfill and the blob issue: - Original commit introducing the vendored polyfill: #19333, the goal was to fix a memory leak because our blob implementation doesn't release resources automatically. Not an ideal fix but since the issue was pretty severe and the infra for a proper fix was not in place. - This introduced an issue when downloading images using `fetch` which was fixed by #22063 which re-added the default blob content type. However that re-introduced the original fetch memory leak. - We have better infra now with jsi and I was able to get blob deallocation working, see #24405 Currently the vendored fetch polyfill is useless since it was changed back to the original version. We can just use the npm version again. I also updated to 3.0 which brings better spec compliance and support for cancellation via `AbortController`, https://github.com/github/fetch/releases/tag/v3.0.0. ## Changelog [General] [Changed] - Remove vendored fetch polyfill, update to whatwg-fetch@3.0 Pull Request resolved: https://github.com/facebook/react-native/pull/24418 Differential Revision: D14932683 Pulled By: cpojer fbshipit-source-id: 915e3d25978e8b9d7507ed807e7fba45aa88385a
2019-05-31 11:32:13 +03:00
"whatwg-fetch": "^3.0.0"
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 07:10:52 +03:00
},
"devDependencies": {
Upgrade to babel@7.0.0 Summary: Now that babel7 is stable, we can upgrade Metro and fbsource to use it, yay!!!!! Reviewed By: mjesun Differential Revision: D9518571 fbshipit-source-id: c85569cb3058235f4f9310949897f7955ecf7324
2018-08-29 20:47:33 +03:00
"@babel/core": "^7.0.0",
upgrade to @babel/generator@7.5.0 Summary: This version is needed to correctly generate inexact flow object type annotations. Keeping the upgrade minimal to reduce exposure to runtime code generation and avoiding a full babel upgrade. Changelog: [Internal] Reviewed By: jbrown215 Differential Revision: D18429751 fbshipit-source-id: d83621ed773566005a4dcdd4f99ded5101dc74b4
2019-11-12 00:48:11 +03:00
"@babel/generator": "^7.5.0",
Move error-subclass-name lint rule to GitHub Summary: Ports an internal ESLint rule used at Facebook, `error-subclass-name`, to cover the React Native codebase. This rule enforces that error classes ( = those with PascalCase names ending with `Error`) only extend other error classes, and that regular functions don't have names that could be mistaken for those of error classes. Reviewed By: rubennorte Differential Revision: D17829298 fbshipit-source-id: 834e457343034a0897ab394b6a2d941789953d2e
2019-10-09 21:46:08 +03:00
"@react-native-community/eslint-plugin": "file:packages/eslint-plugin-react-native-community",
New TextInput-test that would have prevented S168585 Summary: Adds a basic test that would have prevented S168585. We should expand coverage of this and other components as well. Reviewed By: TheSavior Differential Revision: D13038064 fbshipit-source-id: 14cf4742efd53d7bca2a3f8d1c5c34ebc6227674
2018-11-16 07:42:47 +03:00
"@reactions/component": "^2.0.2",
Adds async & babel-generator to the devDependencies Reviewed By: mjesun Differential Revision: D7707199 fbshipit-source-id: 30635f44b24c156ef1947652ef78850b4d9d68b6
2018-04-23 20:26:28 +03:00
"async": "^2.4.0",
Upgrade babel-eslint in xplat/js Summary: `babel-eslint` is the parser you can supply to ESLint based off of Babel. `babel-eslint` 10.1.0 is the newest production version of `babel-eslint`. There are very few changes between 10.0.1 (the lowest previous version) and 10.1.0. There are only 3 non-version-bump commits: 2 bug fixes and enabling parsing of Flow enums. The only project that was on a lower version than 10.0.1 was `/xplat/js/RKJSModules/Libraries/Relay/oss/__github__` - test below Changelog: [Internal] Reviewed By: cpojer Differential Revision: D21055850 fbshipit-source-id: bae0d8af5c6d833a4dbb0ad775c8e5e78ead1051
2020-04-22 05:02:52 +03:00
"babel-eslint": "^10.1.0",
add clang-format to current toolchain (#23434) Summary: add `clang-format` toolchain. we have 2558 files need to process in current task. cc cpojer empyrical shergin matthargett Pull Request resolved: https://github.com/facebook/react-native/pull/23434 Differential Revision: D14067789 Pulled By: cpojer fbshipit-source-id: ddf812fc9579068ebb850bacedde6675376f18b7
2019-02-18 03:00:18 +03:00
"clang-format": "^1.2.4",
- Remove connect, escape-string-regexp, eslint-plugin-relay deps (#28171) Summary: Some dependencies don't need to be downloaded by consumers: - `connect` is only used in RNTester, moved to dev dependencies - `escape-string-regexp` is not used directly, removed - `eslint-plugin-relay` was in both deps and dev deps, removed from deps Overall, this results in node_modules being 3.3MB smaller on clean install. cc cpojer as you may already be aware. Feel free to treat these as a reference when optimizing internal deps. ## Changelog [Internal] [Changed] - Remove connect, escape-string-regexp, eslint-plugin-relay deps Pull Request resolved: https://github.com/facebook/react-native/pull/28171 Test Plan: CI passes Reviewed By: hramos Differential Revision: D20097591 Pulled By: cpojer fbshipit-source-id: 0800751996accf39fd777bc6458be19f66f436a3
2020-02-26 12:56:24 +03:00
"connect": "^3.6.5",
Add Coveralls to package.json [1/2] (#21017) Summary: Adds a new step to the test suite. Test coverage is now collected and sent to Coveralls. Initial configuration is limited to the Libraries/ and local-cli/ directories. Please let me know if additional directories should be considered. I have enabled this repo on the coveralls service. The coveralls token has been added to React Native's Circle CI environment variables. - Track coverage on PRs, and fail PRs that lower the coverage % - Increase coverage :) [INTERNAL] [ENHANCEMENT] [.circleci/config.yml] - Start tracking code coverage (JS) Pull Request resolved: https://github.com/facebook/react-native/pull/21017 Differential Revision: D9724396 Pulled By: hramos fbshipit-source-id: 61da4478877805f9a9a3c9670b54ddc4e40e958b
2018-12-01 06:45:56 +03:00
"coveralls": "^3.0.2",
upgrade detox to 15.4.4 Summary: Upgrade detox version to avoid a crash, per https://github.com/wix/Detox/issues/1947#issuecomment-596547229. Changelog: [Internal] Upgrade Detox to 15.4.4. Reviewed By: TheSavior Differential Revision: D20344541 fbshipit-source-id: a7a3d97b858dbbb13a796dbc3c5c0c47f3ffe556
2020-03-10 00:09:19 +03:00
"detox": "15.4.4",
Upgrade ESLint to 5.1.0 Summary: This release fixes several issues. Most importantly for us: - https://github.com/eslint/eslint/issues/10560 - https://github.com/eslint/eslint/issues/10512 Differential Revision: D8767118 fbshipit-source-id: 2048829d780b5f0f2f607114f803c8d0c3e02ca7
2018-07-09 22:31:17 +03:00
"eslint": "5.1.0",
Upgrade Jest to 24.9.0 Summary: Upgrades Jest to the latest 24.x release, [24.9.0](https://github.com/facebook/jest/blob/master/CHANGELOG.md#2490). This is a minor update as we are already on 24.x across the board. Changelog: [Internal] Reviewed By: cpojer Differential Revision: D19683451 fbshipit-source-id: 12eaeb8b6341d81daf6bdc8f35728967729f291e
2020-02-03 14:16:42 +03:00
"eslint-config-fb-strict": "^24.9.0",
Eliminate eslint npm version mismatch warnings and bump some to latest (#23969) Summary: I was annoyed by warnings from yarn/npm about eslint peer dependencies not being met, so I dived in to try and get rid of some of them. Sometimes it meant bumping a plugin, but then that plugin needed a newer babel-eslint, so it was a dance. Some we can't easily update to latest (eslint-plugin-prettier) because the rule format has changed a bit. Happy to do that in this PR if folks think its a good idea. eslint-config-fbjs itself needs to be updated and republished to eliminate the last few warnings. There are a few new warnings (the repo wasn't linting cleanly for me from the start). I can fix those in this PR, or a separate one, based on people's preferences. [internal] [chore] - Eliminate some peer dependency warnings and bump some eslint packages to latest. Pull Request resolved: https://github.com/facebook/react-native/pull/23969 Differential Revision: D14519076 Pulled By: cpojer fbshipit-source-id: aa44cfd05814d7b79069414aa78d089e448c2235
2019-03-19 20:59:41 +03:00
"eslint-config-fbjs": "2.1.0",
Use eslint-plugin-prettier recommended config (#25674) Summary: I created a new test project today using RN 0.60.3 and saw that prettier is now used with eslint. After looking at the `react-native-community` eslint config, I notice that it wasn't using the [recommended configuration](https://github.com/prettier/eslint-plugin-prettier#recommended-configuration) of `eslint-plugin-prettier` This PR adds the `eslint-config-prettier` to avoid conflicts between eslint and prettier, it also adds the `prettier/react` config to avoid problems with the `eslint-plugin-react`. ## Changelog [General] [Changed] - Use eslint-plugin-prettier recommended config Pull Request resolved: https://github.com/facebook/react-native/pull/25674 Test Plan: - ✅ Ensure there is no difference on this repo (no ESLint errors, same number of warnings, and no changes when running prettier). Differential Revision: D16666178 Pulled By: cpojer fbshipit-source-id: 70f81db793866acc88388b7b00a496aab5e0b156
2019-08-09 16:37:45 +03:00
"eslint-config-prettier": "^6.0.0",
Eliminate eslint npm version mismatch warnings and bump some to latest (#23969) Summary: I was annoyed by warnings from yarn/npm about eslint peer dependencies not being met, so I dived in to try and get rid of some of them. Sometimes it meant bumping a plugin, but then that plugin needed a newer babel-eslint, so it was a dance. Some we can't easily update to latest (eslint-plugin-prettier) because the rule format has changed a bit. Happy to do that in this PR if folks think its a good idea. eslint-config-fbjs itself needs to be updated and republished to eliminate the last few warnings. There are a few new warnings (the repo wasn't linting cleanly for me from the start). I can fix those in this PR, or a separate one, based on people's preferences. [internal] [chore] - Eliminate some peer dependency warnings and bump some eslint packages to latest. Pull Request resolved: https://github.com/facebook/react-native/pull/23969 Differential Revision: D14519076 Pulled By: cpojer fbshipit-source-id: aa44cfd05814d7b79069414aa78d089e448c2235
2019-03-19 20:59:41 +03:00
"eslint-plugin-babel": "^5.3.0",
"eslint-plugin-eslint-comments": "^3.1.1",
"eslint-plugin-flowtype": "2.50.3",
"eslint-plugin-jest": "22.4.1",
"eslint-plugin-jsx-a11y": "6.2.1",
"eslint-plugin-prettier": "2.6.2",
"eslint-plugin-react": "7.12.4",
Update React Hooks Plugin Summary: Updates `eslint-plugin-react-hooks` to 3.0.0. This introduces a new lint error when you use a Hook inside a class. Changelog: [General][Changed] - Updated the React Hooks ESLint Plugin Reviewed By: cpojer Differential Revision: D20675528 fbshipit-source-id: d0cbe9748fd15df7a4c6de00bd1462610e0a43d6
2020-03-26 23:59:39 +03:00
"eslint-plugin-react-hooks": "^3.0.0",
Update eslint-plugin-react-native to 3.8.1 (#27114) Summary: This updates [`eslint-plugin-react-native`](https://github.com/intellicode/eslint-plugin-react-native) to `3.8.1`. Includes some minor updates and fixes, and avoids errors related to incorrect peer dependencies when using ESLint 6+ ``` error "react-native#eslint-plugin-react-native#eslint@^3.17.0 || ^4 || ^5" doesn't satisfy found match of "eslint@6.6.0" ``` ## Changelog [Internal] [Changed] - Update eslint-plugin-react-native to 3.8.1 Pull Request resolved: https://github.com/facebook/react-native/pull/27114 Test Plan: Check that ESlint and CI passes. Differential Revision: D18323510 Pulled By: cpojer fbshipit-source-id: 0257eaebe295fec4b0e52b2f08cf62336fc147a3
2019-11-05 16:26:29 +03:00
"eslint-plugin-react-native": "3.8.1",
Update relay ESLint plugin Summary: We've updated the version of plugin to 1.7.0 that includes similar fix to D19910353 ## Changelog: Changelog: [Internal] Reviewed By: kassens Differential Revision: D19912264 fbshipit-source-id: 973d4211bf56e33da427e01c9c561e15f7406ffb
2020-02-15 02:58:54 +03:00
"eslint-plugin-relay": "1.7.0",
Flow 0.123.0 in xplat/js Summary: Changelog: [Internal] ## Sync of generated files Ran ``` js1 upgrade www-shared -p core_windowless ``` but had to manually revert ``` RKJSModules/Libraries/www-shared/core_windowless/logging/FBLoggerType.flow.js RKJSModules/Libraries/www-shared/core_windowless/logging/FBLogger.js ``` because they introduced more errors ## Flow version bump ``` ~/fbsource/fbcode/flow/facebook/deploy_xplat.sh 0.123.0 ``` Reviewed By: gkz Differential Revision: D21159821 fbshipit-source-id: e106fcb43e4fc525b9185f8fc8a246e6c3a6b14f
2020-04-22 08:40:47 +03:00
"flow-bin": "^0.123.0",
Fabric: working podspecs & works in RNTester (#23803) Summary: This is the couple of hacks I used after I finished #23802 in order to get fabric working on RNTester. This is inspired from prior work by kmagiera. The goal of this PR is to show others what I’m struggling with, and to eventually merge it sans hacks. - Yarn Install - Uncomment the commented out pods in RNTester's pod file - Open RNTesterPods workspace - Run App - this is only for pods, the non-pod RNTester will no longer work until updated with fabric too. - `SurfaceHostingView` & `SurfaceHostingProxyRootView` both try to start the surface immediately, this leads to a race condition due to the javascript not having loaded yet, the hack here is: 1. Swizzle the `start` method on `RCTFabricSurface` to no-op when called. 2. Add observer for `RCTJavaScriptDidLoadNotification` 3. Call private method `_startAllSurfaces` on `_surfacePresenter` in AppDelegate when we receive `RCTJavaScriptDidLoadNotification`. [General] [Added] - Use Fabric in RNTester Pull Request resolved: https://github.com/facebook/react-native/pull/23803 Reviewed By: shergin, mdvacca Differential Revision: D14450726 Pulled By: fkgozali fbshipit-source-id: 8ae2d48634fecb60db539aaf0a2c89ba1f572c27
2019-03-16 09:56:17 +03:00
"flow-remove-types": "1.2.3",
Upgrade to Jest 25 Summary: This diff upgrades Jest to the latest version which fixes a bunch of issues with snapshots (therefore allowing me to enable the Pressable-test again). Note that this also affects Metro and various other tooling as they all depend on packages like `jest-worker`, `jest-haste-map` etc. Breaking changes: https://github.com/facebook/jest/blob/master/CHANGELOG.md This diff increases node_modules by 3 MiB, primarily because it causes more duplicates of `source-map` (0.8 MiB for each copy) and packages like `chalk` 3.x (vs 2.x). The base install was 15 MiB bigger and I reduced it to this size by playing around with various manual yarn.lock optimizations. However, D21085929 reduces node_modules by 11 MiB and the Babel upgrade reduced node_modules by 13 MiB. I will subsequently work on reducing the size through other packages as well and I'm working with the Jest folks to get rid of superfluous TypeScript stuff for Jest 26. Other changes in this diff: * Fixed Pressable-test * Blackhole node-notifier: It's large and we don't need it, and also the license may be problematic, see: https://github.com/facebook/jest/pull/8918 * Updated jest-junit (not a Jest package) but blackholed it internally because it is only used for open source CI. * Updated some API calls we use from Jest to account for breaking changes * Made two absolutely egrigious changes to existing product code tests to make them still pass as our match of async/await, fake timers and then/promise using `setImmediate` is tripping up `regenerator` with `Generator is already run` errors in Jest 25. These tests should probably be rewritten. * Locked everything to the same `resolve` version that we were already using, otherwise it was somehow pulling in 1.16 even though nothing internally uses it. Changelog: [General] Update Jest Reviewed By: rickhanlonii Differential Revision: D21064825 fbshipit-source-id: d0011a51355089456718edd84ea0af21fd923a58
2020-04-20 11:23:59 +03:00
"jest": "^25.4.0",
"jest-junit": "^10.0.0",
Remove `@babel/preset-env` Summary: `babel/preset-env` pulls in a number of unused deps, like `caniuse-lite` (3 MiB) that knows about which browsers support certain features. We do not ship to browsers and always know which version of node we are using, so we don't need to pull this in. I changed `jscodeshift` to optionally depend on `babel/preset-env` instead of always pulling it in. This reduces node_modules by 7 MiB. Changelog: [Internal] Reviewed By: yungsters Differential Revision: D21374475 fbshipit-source-id: 6f55e96e990ec0ca12f17bb3657bfa5429796b93
2020-05-04 11:09:47 +03:00
"jscodeshift": "^0.9.0",
Bundle size reduction (#23968) Summary: With recent activity to extract out non-core things into separate repos, I did an audit of the package.json to see what can be removed, and what packages remain that have newer versions that result in less/smaller javascript code. The goal is to: 1. make developer experience better by removing unneeded dependencies, and 2. eliminate things the app bundler needs to process to make the production app bundle smaller. [internal] [chore] - Remove unneeded packages, bump package versions who now have smaller size Pull Request resolved: https://github.com/facebook/react-native/pull/23968 Differential Revision: D14519070 Pulled By: cpojer fbshipit-source-id: 579f035f925668a34d07293810e3d35a7d0ae076
2019-03-21 21:02:46 +03:00
"mkdirp": "^0.5.1",
Upgrade Prettier in Xplat to version 1.19.1 Summary: Upgrades Prettier in Xplat to 1.19.1 Ignores upgrading packages on already on versions greater than 1.19.1 Changelog: [Internal] allow-large-files bypass-lint (Note: this ignores all push blocking failures!) Reviewed By: gkz, cpojer Differential Revision: D20879147 fbshipit-source-id: 0deee7ac941e91e1c3c3a1e7d3d3ed20de1d657d
2020-04-09 20:55:48 +03:00
"prettier": "1.19.1",
Update React package Summary: This just updates the `react` package to the latest stable version. We updated it to experimental internally earlier so this brings the open source version to the latest before the branch cut. This doesn't include any breaking changes. Changelog: [General][Changed] - Update to React 16.13.1 Reviewed By: cpojer Differential Revision: D20642909 fbshipit-source-id: 68a4c74bfe72f1abdb33b0b9071a4f4e8e568318
2020-03-25 14:14:22 +03:00
"react": "16.13.1",
"react-test-renderer": "16.13.1",
Update ws dependency (#23520) Summary: Our `ws` dependency is super outdated, and is [insecure](https://www.npmjs.com/advisories/550). It is used for the websocket example code in RNTester. This PR updates the dependency, and removes undefined console.logs. [General] [Security] - Updates ws dependency to 6.4.1 Pull Request resolved: https://github.com/facebook/react-native/pull/23520 Differential Revision: D14147596 Pulled By: cpojer fbshipit-source-id: a03041f613a84bf019d8d0a8c5028d6657b5d89a
2019-02-22 00:49:14 +03:00
"shelljs": "^0.7.8",
Generate doc info for RN components Summary: We used to generate the documentation for the website but moved the docs to another repo. There is some work on the docs to be able to ingest info from this repo in order to go back to generating API information. The current thinking is we will generate this JSON file and the website repo will pull it in to generate the docs. I plan to make the script run on CI and fail if the generated file isn't updated, in a follow up PR. Reviewed By: zackargyle Differential Revision: D17183936 fbshipit-source-id: 99ce3fa5d7becc0ef20df5d439b175eedbe546f3
2019-09-20 04:34:26 +03:00
"signedsource": "^1.0.0",
Fix `test_javascript` e2e tests (#24658) Summary: Fix regression in JavaScript e2e tests. [General] [Fixed] - Fixed JavaScript e2e tests. Pull Request resolved: https://github.com/facebook/react-native/pull/24658 Differential Revision: D15146466 Pulled By: cpojer fbshipit-source-id: 05baa99e3b1cdd3ef02bc3f97cf2987dd8ba80f4
2019-04-30 13:05:06 +03:00
"ws": "^6.1.4",
Upgrade yargs to 14.2.0 (#2934) Summary: `mem` package vulnerability found. > In nodejs-mem before version 4.0.0 there is a memory leak due to old results not being removed from the cache despite reaching maxAge. Exploitation of this can lead to exhaustion of memory and subsequent denial of service. ref: https://github.com/sindresorhus/mem/commit/da4e4398cb27b602de3bd55f746efa9b4a31702b `relay-compiler` depends on that. ``` relay-compiler@6.0.0 └─┬ yargs@9.0.1 └─┬ os-locale@2.1.0 └── mem@1.1.0 ``` Pull Request resolved: https://github.com/facebook/relay/pull/2934 Test Plan: - Tested the Relay compiler briefly on the open source examples project, seems like yargs doesn't error - `js1 build relay --project facebook` - `js1 jest` Reviewed By: alunyov Differential Revision: D18397131 Pulled By: kassens fbshipit-source-id: 8b7fc5e237c7b4ce14ff3809cdd59d243e7c4523
2019-11-09 03:04:44 +03:00
"yargs": "^14.2.0"
Initial Detox E2E iOS configuration to be run on RNTester (#20235) Summary: This PR adds initial setup for Detox E2E iOS and some tests for ButtonExample. Pull Request resolved: https://github.com/facebook/react-native/pull/20235 Reviewed By: hramos Differential Revision: D8924525 Pulled By: TheSavior fbshipit-source-id: 8117fc1559c2e9cb831f7b081aa8f4ddc8ba7401
2018-07-31 00:25:49 +03:00
},
"detox": {
"test-runner": "jest",
"runner-config": "RNTester/e2e/config.json",
Update detox to 12.2.0 (#24425) Summary: This updates `detox` from `12.1.1` to `12.2.0`. It includes (amongst other things) the following fixes, as described on the [12.1.4 release page](https://github.com/wix/Detox/releases/tag/12.1.4): - hotfix: redundant logs in the folder - fix: stabilize simulator log recording It also updates the detox test script and config in `packages.json` (which was previously missed when detox was updated to 12.1.x). It will remove the following deprecation warnings: ``` detox[6416] WARN: [test.js] Deprecation warning: "file" and "specs" support will be dropped in the next Detox version. detox[6416] WARN: [test.js] Please edit your package.json according to the migration guide: https://wix.to/I0DOAK0 ``` Instead of extra preprocessing the test folder by `detox`, it will now be passed straight to `jest`. More information in the [migration guide](https://github.com/wix/Detox/blob/master/docs/Guide.Migration.md). [General] [Changed] - Update detox to 12.2.0 Pull Request resolved: https://github.com/facebook/react-native/pull/24425 Differential Revision: D14973771 Pulled By: cpojer fbshipit-source-id: 367ed1f75d2cc3b02349282e7a6201684ba130a7
2019-04-17 20:14:49 +03:00
"specs": "",
Initial Detox E2E iOS configuration to be run on RNTester (#20235) Summary: This PR adds initial setup for Detox E2E iOS and some tests for ButtonExample. Pull Request resolved: https://github.com/facebook/react-native/pull/20235 Reviewed By: hramos Differential Revision: D8924525 Pulled By: TheSavior fbshipit-source-id: 8117fc1559c2e9cb831f7b081aa8f4ddc8ba7401
2018-07-31 00:25:49 +03:00
"configurations": {
add Detox integrations to Android RNTester app Summary: This diff adds required Detox integrations to the RNTester app to be able to run Detox end-to-end tests on the Android version of the app. * Instructions at https://github.com/wix/Detox/blob/master/docs/Introduction.Android.md were followed. * The `minSdkVersion` version for the app was bumped to 18, as required by Detox. * I also added build and test configurations in `package.json` * The debug app is able to run some of the existing tests, but the release app instacrashes. I do not know the reason for the instacrash at this time. * CI integrations to build and test the Android app will be added in future diffs Changelog: [Internal] add Detox integrations to the RNTester Android app Reviewed By: TheSavior Differential Revision: D19566834 fbshipit-source-id: 5dd506bbdbb426a5db18146e5dc7c450a27b1d0c
2020-02-11 21:07:03 +03:00
"android.emu.release": {
upgrade eslint-plugin-relay to 1.6.0 Summary: This updates the lint to include an update to `getModuleName` that landed in the compiler a few days ago so that lint and compiler requirements match in all cases again. js1 upgrade dependency -p eslint-plugin-relay@1.6.0 Changelog: [General] [Changed] - upgrade eslint-plugin-relay to 1.6.0 Reviewed By: alunyov Differential Revision: D19856543 fbshipit-source-id: 2fe3b49f6cd2d170132132557ec8834ca7e94181
2020-02-12 20:44:40 +03:00
"binaryPath": "RNTester/android/app/build/outputs/apk/hermes/release/app-hermes-x86-release.apk",
add Detox integrations to Android RNTester app Summary: This diff adds required Detox integrations to the RNTester app to be able to run Detox end-to-end tests on the Android version of the app. * Instructions at https://github.com/wix/Detox/blob/master/docs/Introduction.Android.md were followed. * The `minSdkVersion` version for the app was bumped to 18, as required by Detox. * I also added build and test configurations in `package.json` * The debug app is able to run some of the existing tests, but the release app instacrashes. I do not know the reason for the instacrash at this time. * CI integrations to build and test the Android app will be added in future diffs Changelog: [Internal] add Detox integrations to the RNTester Android app Reviewed By: TheSavior Differential Revision: D19566834 fbshipit-source-id: 5dd506bbdbb426a5db18146e5dc7c450a27b1d0c
2020-02-11 21:07:03 +03:00
"testBinaryPath": "RNTester/android/app/build/outputs/apk/androidTest/hermes/release/app-hermes-release-androidTest.apk",
upgrade eslint-plugin-relay to 1.6.0 Summary: This updates the lint to include an update to `getModuleName` that landed in the compiler a few days ago so that lint and compiler requirements match in all cases again. js1 upgrade dependency -p eslint-plugin-relay@1.6.0 Changelog: [General] [Changed] - upgrade eslint-plugin-relay to 1.6.0 Reviewed By: alunyov Differential Revision: D19856543 fbshipit-source-id: 2fe3b49f6cd2d170132132557ec8834ca7e94181
2020-02-12 20:44:40 +03:00
"build": "./gradlew RNTester:android:app:assembleRelease RNTester:android:app:assembleAndroidTest -DtestBuildType=release",
add Detox integrations to Android RNTester app Summary: This diff adds required Detox integrations to the RNTester app to be able to run Detox end-to-end tests on the Android version of the app. * Instructions at https://github.com/wix/Detox/blob/master/docs/Introduction.Android.md were followed. * The `minSdkVersion` version for the app was bumped to 18, as required by Detox. * I also added build and test configurations in `package.json` * The debug app is able to run some of the existing tests, but the release app instacrashes. I do not know the reason for the instacrash at this time. * CI integrations to build and test the Android app will be added in future diffs Changelog: [Internal] add Detox integrations to the RNTester Android app Reviewed By: TheSavior Differential Revision: D19566834 fbshipit-source-id: 5dd506bbdbb426a5db18146e5dc7c450a27b1d0c
2020-02-11 21:07:03 +03:00
"type": "android.emulator",
"device": {
"avdName": "Nexus_6_API_29"
}
},
"android.emu.debug": {
"binaryPath": "RNTester/android/app/build/outputs/apk/hermes/debug/app-hermes-x86-debug.apk",
"testBinaryPath": "RNTester/android/app/build/outputs/apk/androidTest/hermes/debug/app-hermes-debug-androidTest.apk",
"build": "./gradlew RNTester:android:app:assembleDebug RNTester:android:app:assembleAndroidTest -DtestBuildType=debug",
"type": "android.emulator",
"device": {
"avdName": "Nexus_6_API_29"
}
upgrade eslint-plugin-relay to 1.6.0 Summary: This updates the lint to include an update to `getModuleName` that landed in the compiler a few days ago so that lint and compiler requirements match in all cases again. js1 upgrade dependency -p eslint-plugin-relay@1.6.0 Changelog: [General] [Changed] - upgrade eslint-plugin-relay to 1.6.0 Reviewed By: alunyov Differential Revision: D19856543 fbshipit-source-id: 2fe3b49f6cd2d170132132557ec8834ca7e94181
2020-02-12 20:44:40 +03:00
},
Initial Detox E2E iOS configuration to be run on RNTester (#20235) Summary: This PR adds initial setup for Detox E2E iOS and some tests for ButtonExample. Pull Request resolved: https://github.com/facebook/react-native/pull/20235 Reviewed By: hramos Differential Revision: D8924525 Pulled By: TheSavior fbshipit-source-id: 8117fc1559c2e9cb831f7b081aa8f4ddc8ba7401
2018-07-31 00:25:49 +03:00
"ios.sim.release": {
"binaryPath": "RNTester/build/Build/Products/Release-iphonesimulator/RNTester.app/",
deprecate iOS .xcodeproj (#25583) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/25583 We now use CocoaPods for better maintainability. Reviewed By: hramos Differential Revision: D16193719 fbshipit-source-id: 26382f2da4eaba14a71771540b587fdc80b41108
2019-07-11 21:54:38 +03:00
"build": "xcodebuild -workspace RNTester/RNTesterPods.xcworkspace -scheme RNTester -configuration Release -sdk iphonesimulator -derivedDataPath RNTester/build -UseModernBuildSystem=NO -quiet",
Initial Detox E2E iOS configuration to be run on RNTester (#20235) Summary: This PR adds initial setup for Detox E2E iOS and some tests for ButtonExample. Pull Request resolved: https://github.com/facebook/react-native/pull/20235 Reviewed By: hramos Differential Revision: D8924525 Pulled By: TheSavior fbshipit-source-id: 8117fc1559c2e9cb831f7b081aa8f4ddc8ba7401
2018-07-31 00:25:49 +03:00
"type": "ios.simulator",
Bump detox simulator version to work with latest xcode (#27733) Summary: The latest xcode version removed iPhone 6s, so we need to bump to the latest simulator listed that has 3d touch. ## Changelog [General] [Fix] - Bump e2e simulator version Pull Request resolved: https://github.com/facebook/react-native/pull/27733 Test Plan: - `yarn build-ios-e2e && yarn test-ios-e2e ` Reviewed By: hramos, sammy-SC Differential Revision: D19345576 Pulled By: rickhanlonii fbshipit-source-id: 428cb83ccb899409e972551f18df580174adee91
2020-01-13 22:13:01 +03:00
"name": "iPhone 8"
Detox debug build (#22572) Summary: Adds a Detox configuration and instructions for running the app in development mode in Detox. This speeds up developing tests, because changes to production code don't require a full rebuild. Pull Request resolved: https://github.com/facebook/react-native/pull/22572 Differential Revision: D13396883 Pulled By: cpojer fbshipit-source-id: 186cc8d75eccae411b602cb0f68f0e11856e0743
2018-12-10 13:31:24 +03:00
},
"ios.sim.debug": {
"binaryPath": "RNTester/build/Build/Products/Debug-iphonesimulator/RNTester.app/",
deprecate iOS .xcodeproj (#25583) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/25583 We now use CocoaPods for better maintainability. Reviewed By: hramos Differential Revision: D16193719 fbshipit-source-id: 26382f2da4eaba14a71771540b587fdc80b41108
2019-07-11 21:54:38 +03:00
"build": "xcodebuild -workspace RNTester/RNTesterPods.xcworkspace -scheme RNTester -configuration Debug -sdk iphonesimulator -derivedDataPath RNTester/build -UseModernBuildSystem=NO -quiet",
Detox debug build (#22572) Summary: Adds a Detox configuration and instructions for running the app in development mode in Detox. This speeds up developing tests, because changes to production code don't require a full rebuild. Pull Request resolved: https://github.com/facebook/react-native/pull/22572 Differential Revision: D13396883 Pulled By: cpojer fbshipit-source-id: 186cc8d75eccae411b602cb0f68f0e11856e0743
2018-12-10 13:31:24 +03:00
"type": "ios.simulator",
Bump detox simulator version to work with latest xcode (#27733) Summary: The latest xcode version removed iPhone 6s, so we need to bump to the latest simulator listed that has 3d touch. ## Changelog [General] [Fix] - Bump e2e simulator version Pull Request resolved: https://github.com/facebook/react-native/pull/27733 Test Plan: - `yarn build-ios-e2e && yarn test-ios-e2e ` Reviewed By: hramos, sammy-SC Differential Revision: D19345576 Pulled By: rickhanlonii fbshipit-source-id: 428cb83ccb899409e972551f18df580174adee91
2020-01-13 22:13:01 +03:00
"name": "iPhone 8"
Initial Detox E2E iOS configuration to be run on RNTester (#20235) Summary: This PR adds initial setup for Detox E2E iOS and some tests for ButtonExample. Pull Request resolved: https://github.com/facebook/react-native/pull/20235 Reviewed By: hramos Differential Revision: D8924525 Pulled By: TheSavior fbshipit-source-id: 8117fc1559c2e9cb831f7b081aa8f4ddc8ba7401
2018-07-31 00:25:49 +03:00
}
}
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 07:10:52 +03:00
}
Bump metro to v0.24.4 Reviewed By: mjesun Differential Revision: D6711855 fbshipit-source-id: 88192d22a8b50f16ad329b6dfdb7c5da24b2ce9e
2018-01-12 20:09:04 +03:00
}