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

180 строки
6.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",
Split React Native repo into product/infra packages Summary: Changelog: [Internal] Reviewed By: TheSavior Differential Revision: D23165627 fbshipit-source-id: f371c070f8b297c218d2989ff3b553a8b83c18ea
2020-08-18 22:07:57 +03:00
"private": true,
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",
chore: deduplicate lock, update packages repository fields (#30044) Summary: This small PR includes the following changes: * deduplicate yarn lock file using [`yarn-deduplicate`](https://github.com/atlassian/yarn-deduplicate) package * deduplicate script has been added as `update-lock`, let me know if you would like also to see this in [`postinstall`](https://docs.npmjs.com/misc/scripts) (to automatically optimize lock on every dependency change) * according to the [npm docs](https://docs.npmjs.com/files/package.json#repository): * main `package.json` repository field has been replaced with shorthand * monorepo packages repository field has been extended by `directory` The main goal of introducing deduplication script was to optimize the dependencies footprint while developing and speed up the initial installation process. Running `yarn-deduplicate` also increase the security in some way, because it enforces usage only of the latest version of the package. You can read more about the benefits in the deduplicate script [repository](https://github.com/atlassian/yarn-deduplicate#duplicated-packages). ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://github.com/facebook/react-native/wiki/Changelog --> [Internal] [Added] - add yarn lock deduplication script Pull Request resolved: https://github.com/facebook/react-native/pull/30044 Test Plan: `yarn install` was successful, this also should not affect yarn workspaces in any way. Reviewed By: GijsWeterings Differential Revision: D23959812 Pulled By: cpojer fbshipit-source-id: e2455e3718378e1ce6206e79463d4083f8fe5d47
2020-09-29 08:39:27 +03:00
"repository": "github:facebook/react-native",
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": {
Breaking - Bump minimum Node version from 14 to 16 (#36217) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/36217 ## Bump minimum Node JS version to 16 via `react-native/package.json#engines` In https://github.com/facebook/react-native/pull/35443 we stopped running CI in Node 14 - this follows up by formally making Node 16 the minimum supported version ahead of the 0.72 cut. Node 14 [ends maintenance releases in April](https://github.com/nodejs/release#release-schedule), and bumping this minimum will allow other associated Node JS tools (CLI, Metro, Jest) to reduce their support burden. ## Insert `engines` into `template/package.json` The constraint at `react-native/package.json#engines` ensures the minimum at install/init time, with package managers providing an actionable error or warning if the constraint is not met. However, it doesn't help guide users to a supported version if on an existing project they run (e.g.) `yarn start`. Adding a constraint to the template helps prevent accidental use of an older version, as well as providing a clear reference for the current minimum. Insertion of `engines` below existing `package.json` fields is consistent with [`sort-package-json`](https://github.com/keithamus/sort-package-json/blob/main/defaultRules.md) and [`prettier-package-json`](https://github.com/cameronhunter/prettier-package-json/blob/main/src/defaultOptions.ts) - and keeps it out of the way of fields RN developers are likely to be more concerned about. ## Docs PR https://github.com/facebook/react-native-website/pull/3580 ## Changelog: [General][Breaking] Bump minimum Node JS version to 16 Reviewed By: jacdebug Differential Revision: D43436883 fbshipit-source-id: 0b369487fe44fe777e6fedc2299973a5fddd06b2
2023-02-20 20:47:24 +03:00
"node": ">=16"
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
},
Move TypeScript declarations into react-native (#34614) Summary: ## Changelog [General] [Added] - Add `types` folder to house TypeScript types. Release TypesScript types with react-native and eventually deprecate [types/react-native](https://www.npmjs.com/package/types/react-native). The current plan is to release types/react-native for 0.70 and 0.71 while also maintaining types here. This will result in some double maintenance until 0.72 but will give community time to move off of types/react-native. After this lands, there have been changes on `main` of types that we need to update. Then, when we release 0.71 from DefinitelyTyped, we can simply copy over the `types` folder from this repo. Pull Request resolved: https://github.com/facebook/react-native/pull/34614 Test Plan: `yarn run test-typescript` for linting types * Created a new project using the TS template and my local clone of `react-native` on this branch. `npx react-native init MyTSApp --version <path-to-my-local-rn-repo> --template react-native-template-typescript` * Updated the `package.json` to remove `types/react-native` * Deleted my node_modules and re-ran yarn * Opened MyTSApp in VSCode and verified the type suggestions appeared and cmd+click to defnitions took me to the node_module dependency `react-native/types` ## Danger is failing on this PR and it's expected as it runs off the changes on `main`. [This is expected](https://docs.github.com/en/github-ae@latest/actions/using-workflows/events-that-trigger-workflows?fbclid=IwAR2_AE0Jwndt8Gu-iTQnxGxLJq7nakbi7sz8jwZ6U62JWLSdcZuvjcQ6WvE#pull_request_target). However testing it locally passes. Once merged, and these changes are on `main`, danger will pass again. ``` $ react-native/packages/react-native-bots ❯ yarn danger pr https://github.com/facebook/react-native/pull/34614 yarn run v1.22.19 $ ..react-native/node_modules/.bin/danger pr https://github.com/facebook/react-native/pull/34614 Starting Danger PR on facebook/react-native#34614 Danger: ✓ found only warnings, not failing the build ## Warnings :lock: package.json - <i>Changes were made to package.json. This will require a manual import by a Facebook employee.</i> ✨ Done in 13.24s. ``` Reviewed By: mdvacca Differential Revision: D39479137 Pulled By: lunaleaps fbshipit-source-id: 1d506f812d566b783b6e79104cd6339b077a42a7
2022-09-19 22:26:00 +03:00
"types": "types",
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": [
include android in npm package (#30451) Summary: RN app expects **android** folder with maven artifacts in NPM package, and *test-manual-e2e.sh* fails on **0.64-stable** because it couldn't find **android** folder, therefore looks into remote repos and finds 0.20.1 version on bintray. See https://github.com/facebook/react-native/blob/e99b8bbb404f8cd1f11b6c7998083be530d7b8a4/template/android/build.gradle#L27 This PR will change npm pack to include **android** folder with maven artifacts in NPM package, thus RN android apps can find RN in node_modules. ## Changelog [Internal] [Changed] - include *android* in npm package Pull Request resolved: https://github.com/facebook/react-native/pull/30451 Test Plan: With this change *test-manual-e2e.sh* will run successfully, previous it was failing due to duplicate classes error. Reviewed By: MichaReiser Differential Revision: D25157286 Pulled By: cpojer fbshipit-source-id: 42fcd09d417560ebd9d3fc8fc52e1e291fca152e
2020-11-24 15:24:05 +03:00
"android",
Make it easier for users to build from source if needed (#36165) Summary: This page is not up to date anymore: https://reactnative.dev/contributing/how-to-build-from-source I'm pushing those changes to make it easier to consume our build when building from source. I'll update the page those change lands. ## Changelog [Internal] [Changed] - Make it easier for users to build from source if needed Pull Request resolved: https://github.com/facebook/react-native/pull/36165 Test Plan: If the CI is green, we should be good to merge this Reviewed By: cipolleschi Differential Revision: D43303867 Pulled By: cortinico fbshipit-source-id: c0080b06cbcbf872ee92fcfa82a9f823d5b247f4
2023-02-15 17:05:56 +03:00
"build.gradle.kts",
[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",
Publish Custom Flow Library Definitions (#30102) Summary: react-native has moved more code to be flow-strict. Part of this move involved adding custom flow-typed definitions for some third-party dependencies where not previously present. These definitions are not currently published, which prevents type-checking some parts of react-native externally. This change publishes these type definitions as part of the react-native NPM package. Impact to package size is pretty negligible. ## Changelog [Internal] [Fixed] - Publish Custom Flow Library Definitions Pull Request resolved: https://github.com/facebook/react-native/pull/30102 Reviewed By: TheSavior Differential Revision: D24099502 Pulled By: cpojer fbshipit-source-id: bf3942aa973df4cfc2843ec3e7dbec82623f0447
2020-10-06 11:00:42 +03:00
"flow-typed",
Make it easier for users to build from source if needed (#36165) Summary: This page is not up to date anymore: https://reactnative.dev/contributing/how-to-build-from-source I'm pushing those changes to make it easier to consume our build when building from source. I'll update the page those change lands. ## Changelog [Internal] [Changed] - Make it easier for users to build from source if needed Pull Request resolved: https://github.com/facebook/react-native/pull/36165 Test Plan: If the CI is green, we should be good to merge this Reviewed By: cipolleschi Differential Revision: D43303867 Pulled By: cortinico fbshipit-source-id: c0080b06cbcbf872ee92fcfa82a9f823d5b247f4
2023-02-15 17:05:56 +03:00
"gradle.properties",
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",
"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",
Stop publishing jest/preprocessor.js to npm Summary: Changelog: [Breaking][General] Remove jest/preprocessor from the react-native package Using `react-native/jest/preprocessor` outside of the React Native repo has been deprecated since D34820086 (https://github.com/facebook/react-native/commit/c1e9aa9a272aed3cba60c4aeff783eeb8bffce68). Here, we make this file private and stop publishing it to npm. The supported method of using Jest in React Native projects is using the [Jest preset](https://jestjs.io/docs/tutorial-react-native) shipped as part of the `react-native` package. NOTE: We could probably make some of the other files under `jest/` private as well, but we should go through a separate deprecation cycle with those, in case they are also being used externally by some projects. I'm leaving that for future followup at the moment. Reviewed By: GijsWeterings Differential Revision: D36132939 fbshipit-source-id: 300ffa6cf16232573cd3a79a34c14daaafd7aa43
2022-05-06 14:43:09 +03:00
"!jest/private",
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
"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",
"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.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",
"scripts/compose-source-maps.js",
Reintroduce `find-node.sh` as mitigation measure (#33538) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/33538 This Diff is a revert of this other diff: D34352049 (https://github.com/facebook/react-native/commit/802b3f778b4d2ecd22882b371a84293421558b8a). Following a discussion with the Open Source Community, the removal of `find-node.sh` script will break some configurations that leverages different node managers. The landed diff will block the release of version 0.69, that's the reason why we are reverting it. However, we still want to abstract RN from knowing which node manager the user is going to use. After discussing with the community, we will deprecate the usage of this script and we will move toward a configurable `.xcode.env` file that developers can configure on their own. The task for this is tracked here: T115868521. ## Changelog [Internal][Removed] - Reintroduce the old `find-node.sh` script to prevent broken builds for some users Reviewed By: cortinico Differential Revision: D35280778 fbshipit-source-id: 7a0b269af207e13998fd85c0c4839e75028cda65
2022-04-04 12:43:07 +03:00
"scripts/find-node-for-xcode.sh",
infra(e2e): rework local E2E script (#34513) Summary: This is a long time coming effort to improve the situation around the local e2e script that in the release crew: the current bash-based script is quirky at best, and what you end up generating as a sample project is not really a true sample project. This is where this PR comes in: it migrates the flow from `./scripts/test-manual-e2e.sh` to `yarn test-e2e-local <options>`. Here's the current shape of the options: ```sh Options: --help Show help [boolean] --version Show version number [boolean] -t, --target [choices: "RNTester", "RNTestProject"] [default: "RNTester"] -p, --platform [choices: "iOS", "Android"] [default: "iOS"] -h, --hermes [boolean] [default: true] ``` The idea is to change it so that you can just run the script, and it will do that one specific thing "well", without the tester needing to do anything aside from actually testing the app once it's open. Some of the key changes: * tries to stick to the patterns of the other established *.js based scripts, in terms of tooling and approach (and even refactor parts that can be shared with other scripts) - like the android artifacts generation * no need to start the android emulator on the side * no need to start Metro on the side * RNTester iOS will open up on the simulator (no Xcode open that then you need to press) Things that still need work: * see the #fixme and #todo in comments * because we rely on exec, the output sent back is not formatted/shaped correctly so it's a bit more noisy/chaotic - but can't handle it right now because the package we use doesn't allow it - see https://github.com/shelljs/shelljs/issues/86 ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [Internal] [Changed] - Migrate bash E2E local testing script to new JS based command Pull Request resolved: https://github.com/facebook/react-native/pull/34513 Test Plan: To test the script, you can run it passing the options showed above; this is the current situation: * RNTester iOS Hermes ✅ * RNTester Android Hermes ✅ * RNTester iOS JSC ✅ * RNTester Android JSC ✅ * RNTestProject Android Hermes ✅ * RNTestProject iOS Hermes ✅ * RNTestProject Android JSC ✅ * RNTestProject iOS JSC ✅ Reviewed By: cortinico Differential Revision: D39814692 Pulled By: cortinico fbshipit-source-id: d4791798aaad764c6a3757269b7636f847ccf2ca
2022-10-04 14:56:44 +03:00
"scripts/generate-codegen-artifacts.js",
Add newly added scripts to package.json Summary: Changelog: [internal] We added generate-artifacts.js and generate-provider.js for codegen, and this diff adds that to the package.json so that it gets included. Reviewed By: cortinico Differential Revision: D32910033 fbshipit-source-id: 4982704fd3dac12b9cb64c4b3facb496abef4343
2021-12-07 21:21:38 +03:00
"scripts/generate-provider-cli.js",
Update iOS Fabric-related files to compile on OSS (#29810) Summary: Original PR contents: This pull request updates the Podspecs and associated build scripts, and some source files so they build on OSS. RNTester now compiles with `fabric_enabled` again. The following changes have been made: * Various spots that were pointing to the old `ReactCommon/fabric` location have now been updated to `ReactCommon/react/renderer` * Files that were attempting to use internal FB header `FBRCTFabricComponentsPlugins.h` were changed to use `RCTFabricComponentsPlugins.h` * `RCTFabricComponentsPlugins` in OSS was updated to include the `Image` fabric component (thanks tsapeta) * Replaced old `generate-rncore.sh` build script with new `generate-rncore.js` script which does not require `flow-node` and uses the `react-native-codegen` API directly, so there is no longer any need for an interim `schema-rncore.json` file. * Updated Yoga podspec which wasn't fully synced with changes from the main Yoga repo * Updated Fabric podspec with additional needed subspecs Additions to PR by hramos: * Replaced use of generate-rncore scripts with the original generate-native-modules-specs.sh script, which is now generate-specs.sh and supports both codegen for Native Modules and Components now (TurboModules/Fabric). * Codegen now runs at build time as part of the Xcode build pipeline instead of as part of `pod install`. The build script is injected by the FBReactNativeSpec pod, as the pod is part of both Fabric and non-Fabric builds. ## Changelog [General] [Fixed] - RNTester compiles with `fabric_enabled` again Pull Request resolved: https://github.com/facebook/react-native/pull/29810 Test Plan: RNTester now compiles and runs in the simulator again when `fabric_enabled` is set to `true`. ``` cd xplat/js/react-native-github/packages/rn-tester USE_FABRIC=1 pod install open RNTesterPods.xcworkspace # Build and run ``` Reviewed By: fkgozali Differential Revision: D24058507 Pulled By: hramos fbshipit-source-id: 8b2ea3694e6cb9aa23f83f087e2995fd4320e2bb
2020-12-22 19:33:56 +03:00
"scripts/generate-specs-cli.js",
Attach a script to React-RCTAppDelegate to register Legacy Components in the interop layer (#36335) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/36335 This change depends on [this PR](https://github.com/react-native-community/cli/pull/1849) of the CLI that introduces the `unstable_reactLegacyComponent` field in the `react-native.config.js` file. This change introduce a JS script that reads that fields and generated a method in an object to return a list of components to be registered. The `RCTAppDelegate` has been updated to read those components and to automatically register them into the interop layer. Notice that a user can just update the `react-native.config.js` and rebuild the app to integrate these changes, there is no need to reinstall the pods. The idea behind this logic is to let the user know which components they are using with the interop layer, rather than rely on some black magic that could leave them blind to the need of actually migrate their apps. ## Changelog: [iOS][Changed] - Implement mechanism to register legacy components in the iOS Fabric interop layer Reviewed By: cortinico, dmytrorykun Differential Revision: D43665973 fbshipit-source-id: b4e8d71fa1bbed7a6130ee4f83a6221394d5306e
2023-03-04 01:44:57 +03:00
"scripts/codegen",
"!scripts/codegen/__tests__",
"!scripts/codegen/__test_fixtures__",
Hermes: Add scripts to package, remove shelljs Summary: The new Hermes scripts need to be included in the `react-native` npm. The `shelljs` dependency that was used by the Hermes scripts is a dev dependency, so instead of adding to the `react-native` npm size, we refactored its use out of hermes-utils.js. Changelog: [General][Added] - Add Hermes scripts to package Reviewed By: cortinico Differential Revision: D36387135 fbshipit-source-id: 12d0bc29d365c4cb18d33a0d390e6e7d34864b7a
2022-05-25 00:08:48 +03:00
"scripts/hermes/hermes-utils.js",
"scripts/hermes/prepare-hermes-for-build.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
"scripts/ios-configure-glog.sh",
Introduce .xcode.env configuration file to source `node` (#33546) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/33546 This Diff does 2 things: 1. Removes all the remnant of the `find-node.sh` script. This allows React Native to stay agnostic from any other node manager 2. Introduces a way for the developers to specify which `node` executable they want to use, through a simple `.env` file. ## Changelog [iOS][Changed] - This PR removes the `find-node.sh` scripts and replaces it with an `.xcode.env` file that is sourced by the script phases that needs it. The `.xcode.env` file is versioned: to customize a local environment, an unversioned `.xcode.local.env` can be used. Reviewed By: cortinico Differential Revision: D35317070 fbshipit-source-id: 4b400ba56aa2d574db563fa67b2008e1ddde1c59
2022-04-11 12:50:57 +03:00
"scripts/xcode/with-environment.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
"scripts/launchPackager.bat",
"scripts/launchPackager.command",
Move cocoapods cli native_modules require from template to rn scripts (#34215) Summary: This resolves issues where the node_modules structure is not hoisted (like with pnpm). Since the template does not directly depend on the cli, it doesn't exist in the pnpm node_modules root. Moving it to the rn scripts makes sure that the relative require starts in the correct directory for both hoisted and pnpm structures. ## Changelog [iOS] [Fixed] - Fix cocoapods cli native_modules require for pnpm node_modules Pull Request resolved: https://github.com/facebook/react-native/pull/34215 Test Plan: 1. react-native init 2. rm -rf node_modules 3. pnpm i 4. bundle install 5. bundle exec pod install --project-directory=ios This should succeed. Without the patch, it will fail with ``` [!] Invalid `Podfile` file: cannot load such file -- /.../node_modules/react-native-community/cli-platform-ios/native_modules. # from /.../ios/Podfile:2 # ------------------------------------------- # require_relative '../node_modules/react-native/scripts/react_native_pods' > require_relative '../node_modules/react-native-community/cli-platform-ios/native_modules' # # ------------------------------------------- ``` Reviewed By: cortinico Differential Revision: D37959152 Pulled By: cipolleschi fbshipit-source-id: 7fa9af4a8c153cfd38360f57eca415a8c252dbd5
2022-07-19 19:11:08 +03:00
"scripts/native_modules.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/node-binary.sh",
"scripts/packager.sh",
Add missing scripts/packager-reporter.js file in npm published files (#32763) Summary: When using the nightly builds, metro fails with an error because of missing scripts/packager-reporter.js. The file is not included in the published files so this is why. ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://github.com/facebook/react-native/wiki/Changelog --> [Internal] [Fixed] - Add missing scripts/packager-reporter.js file in npm published files Pull Request resolved: https://github.com/facebook/react-native/pull/32763 Test Plan: Test that nightly builds work when adding the missing file. Reviewed By: motiz88 Differential Revision: D33128315 Pulled By: ShikaSD fbshipit-source-id: 617d124205edf63dbca8da50336ca895f5ce866a
2021-12-15 22:41:37 +03:00
"scripts/packager-reporter.js",
Refactor script_phases script out of react_native_pods.rb (#32764) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/32764 Changelog: [Internal] This diff refactors react_native_pods.rb so that it's a bit more readable/maintainable. With the intorduction of the codegen discovery script, we have two script phases that shares some code. I've factored it out of the main file and wrote a snapshot test so that it's easier to see the output script file. Reviewed By: cortinico Differential Revision: D33045541 fbshipit-source-id: 9c80b5d7e11862cc44275e36882487a7d63e8125
2021-12-16 03:10:03 +03:00
"scripts/react_native_pods_utils/script_phases.rb",
"scripts/react_native_pods_utils/script_phases.sh",
Remove outdated references in `react-native/package.json` Summary: These files or directories no longer exist, so they don't need to be listed as files to be published to npm. The only file that was removed that does exist is the `.flowconfig` file, which should not actually be shipped to npm as projects using Flow would have their own `.flowconfig` file. Changelog: [Internal] Reviewed By: GijsWeterings Differential Revision: D23132479 fbshipit-source-id: dc656d8215c9dac11025902b403c3f6560e62e37
2020-08-17 19:45:55 +03:00
"scripts/react_native_pods.rb",
Move cocoapods utilities to utils.rb - Part 1 (#33978) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/33978 This Diff moves part of the utilities from the `react_native_pods` file to a specific `utils.rb` file. It adds tests for these utils and improve our test mocks. The goal is to simplify the `react_native_pods.rb` so it's easier to work with it. I decided to split this diff in 2 because it was becoming quite big. ## Changelog [iOS][Changed] - Refactoring part of the react_native_pods.rb script Reviewed By: cortinico Differential Revision: D37004347 fbshipit-source-id: a5156f7c199d082d5d895a58af80948556c51c2a
2022-06-10 17:25:52 +03:00
"scripts/cocoapods",
Attach a script to React-RCTAppDelegate to register Legacy Components in the interop layer (#36335) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/36335 This change depends on [this PR](https://github.com/react-native-community/cli/pull/1849) of the CLI that introduces the `unstable_reactLegacyComponent` field in the `react-native.config.js` file. This change introduce a JS script that reads that fields and generated a method in an object to return a list of components to be registered. The `RCTAppDelegate` has been updated to read those components and to automatically register them into the interop layer. Notice that a user can just update the `react-native.config.js` and rebuild the app to integrate these changes, there is no need to reinstall the pods. The idea behind this logic is to let the user know which components they are using with the interop layer, rather than rely on some black magic that could leave them blind to the need of actually migrate their apps. ## Changelog: [iOS][Changed] - Implement mechanism to register legacy components in the iOS Fabric interop layer Reviewed By: cortinico, dmytrorykun Differential Revision: D43665973 fbshipit-source-id: b4e8d71fa1bbed7a6130ee4f83a6221394d5306e
2023-03-04 01:44:57 +03:00
"!scripts/cocoapods/__tests__",
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/react-native-xcode.sh",
Make sure sdks/.hermesversion is included inside the NPM package. Summary: The sdks/.hermesversion file should be included inside the React Native NPM package. While this file is available on the release branch, so it's effectively used during artifact preparation, the file should also be included inside the react-native NPM package. This commit addresses it. Changelog: [Internal] - Make sure sdks/.hermesversion is included inside the NPM package Reviewed By: dmitryrykun Differential Revision: D36785480 fbshipit-source-id: 1152de77818e92814b402a57ca5a05c235747eac
2022-06-01 12:56:42 +03:00
"sdks/.hermesversion",
Hermes: Copy build scripts to RN Summary: Copy Hermes build scripts to React Native repository for greater control over the build pipeline when used in RN. Changelog: [Internal] Reviewed By: neildhar Differential Revision: D36295406 fbshipit-source-id: 54bf4173b6c75db35de828378e6f5782a248ed2e
2022-05-12 01:49:48 +03:00
"sdks/hermes-engine",
Build hermesc on all commits and include binaries in all releases (#33398) Summary: Extend the hermesc build jobs to cover nightlies, commitlies, and stable releases. The Hermes Compiler will be packaged alongside react-native releases in order to save on build time. # Changelog: [Internal] Pull Request resolved: https://github.com/facebook/react-native/pull/33398 Reviewed By: cortinico Differential Revision: D34727676 fbshipit-source-id: cc147b4d015abc8b5c798e8e3b5497a5de653b69
2022-03-23 23:18:52 +03:00
"sdks/hermesc",
Make it easier for users to build from source if needed (#36165) Summary: This page is not up to date anymore: https://reactnative.dev/contributing/how-to-build-from-source I'm pushing those changes to make it easier to consume our build when building from source. I'll update the page those change lands. ## Changelog [Internal] [Changed] - Make it easier for users to build from source if needed Pull Request resolved: https://github.com/facebook/react-native/pull/36165 Test Plan: If the CI is green, we should be good to merge this Reviewed By: cipolleschi Differential Revision: D43303867 Pulled By: cortinico fbshipit-source-id: c0080b06cbcbf872ee92fcfa82a9f823d5b247f4
2023-02-15 17:05:56 +03:00
"settings.gradle.kts",
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",
Stop publishing jest/preprocessor.js to npm Summary: Changelog: [Breaking][General] Remove jest/preprocessor from the react-native package Using `react-native/jest/preprocessor` outside of the React Native repo has been deprecated since D34820086 (https://github.com/facebook/react-native/commit/c1e9aa9a272aed3cba60c4aeff783eeb8bffce68). Here, we make this file private and stop publishing it to npm. The supported method of using Jest in React Native projects is using the [Jest preset](https://jestjs.io/docs/tutorial-react-native) shipped as part of the `react-native` package. NOTE: We could probably make some of the other files under `jest/` private as well, but we should go through a separate deprecation cycle with those, in case they are also being used externally by some projects. I'm leaving that for future followup at the moment. Reviewed By: GijsWeterings Differential Revision: D36132939 fbshipit-source-id: 300ffa6cf16232573cd3a79a34c14daaafd7aa43
2022-05-06 14:43:09 +03:00
"!template/node_modules",
"!template/package-lock.json",
"!template/yarn.lock",
Fix: Publish types folder (#34727) Summary: From changes in https://github.com/facebook/react-native/pull/34614, I forgot to actually export the types directory. ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [Internal] - Add types directory as part of the npm package Pull Request resolved: https://github.com/facebook/react-native/pull/34727 Test Plan: Verified on [`build_npm_package_1`](https://app.circleci.com/pipelines/github/facebook/react-native/15799/workflows/4fd57bfc-0142-49d9-a1a6-83fa43f0e371/jobs/295438) job where we create the commitly, that `types` folder is included and `__typetests__` are ignored Reviewed By: cipolleschi Differential Revision: D39646310 Pulled By: lunaleaps fbshipit-source-id: 361f7925fa1cdc30d0865d291933c7fce9e0fa49
2022-09-20 22:39:58 +03:00
"third-party-podspecs",
"types"
[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",
Add Java linting using google-java-format (#30444) Summary: Adds `google-java-format` linting for all `.java` files in the `ReactAndroid/` folder - Linting requires java and is now performed on the android container - https://github.com/google/google-java-format ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://github.com/facebook/react-native/wiki/Changelog --> [Internal] [Added] - Linting for *.java files (google-java-format) Pull Request resolved: https://github.com/facebook/react-native/pull/30444 Test Plan: See this example PR for lint comments: https://github.com/facebook/react-native/pull/30512 Reviewed By: hramos Differential Revision: D25253627 Pulled By: nganbread fbshipit-source-id: e39e4411bf09a96c054afaf6c12b3d05a80f40fa
2020-12-07 14:10:46 +03:00
"lint-java": "node ./scripts/lint-java.js",
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
"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",
Move TypeScript declarations into react-native (#34614) Summary: ## Changelog [General] [Added] - Add `types` folder to house TypeScript types. Release TypesScript types with react-native and eventually deprecate [types/react-native](https://www.npmjs.com/package/types/react-native). The current plan is to release types/react-native for 0.70 and 0.71 while also maintaining types here. This will result in some double maintenance until 0.72 but will give community time to move off of types/react-native. After this lands, there have been changes on `main` of types that we need to update. Then, when we release 0.71 from DefinitelyTyped, we can simply copy over the `types` folder from this repo. Pull Request resolved: https://github.com/facebook/react-native/pull/34614 Test Plan: `yarn run test-typescript` for linting types * Created a new project using the TS template and my local clone of `react-native` on this branch. `npx react-native init MyTSApp --version <path-to-my-local-rn-repo> --template react-native-template-typescript` * Updated the `package.json` to remove `types/react-native` * Deleted my node_modules and re-ran yarn * Opened MyTSApp in VSCode and verified the type suggestions appeared and cmd+click to defnitions took me to the node_module dependency `react-native/types` ## Danger is failing on this PR and it's expected as it runs off the changes on `main`. [This is expected](https://docs.github.com/en/github-ae@latest/actions/using-workflows/events-that-trigger-workflows?fbclid=IwAR2_AE0Jwndt8Gu-iTQnxGxLJq7nakbi7sz8jwZ6U62JWLSdcZuvjcQ6WvE#pull_request_target). However testing it locally passes. Once merged, and these changes are on `main`, danger will pass again. ``` $ react-native/packages/react-native-bots ❯ yarn danger pr https://github.com/facebook/react-native/pull/34614 yarn run v1.22.19 $ ..react-native/node_modules/.bin/danger pr https://github.com/facebook/react-native/pull/34614 Starting Danger PR on facebook/react-native#34614 Danger: ✓ found only warnings, not failing the build ## Warnings :lock: package.json - <i>Changes were made to package.json. This will require a manual import by a Facebook employee.</i> ✨ Done in 13.24s. ``` Reviewed By: mdvacca Differential Revision: D39479137 Pulled By: lunaleaps fbshipit-source-id: 1d506f812d566b783b6e79104cd6339b077a42a7
2022-09-19 22:26:00 +03:00
"prettier": "prettier --write \"./**/*.{js,md,yml,ts,tsx}\"",
"format-check": "prettier --list-different \"./**/*.{js,md,yml,ts,tsx}\"",
chore: deduplicate lock, update packages repository fields (#30044) Summary: This small PR includes the following changes: * deduplicate yarn lock file using [`yarn-deduplicate`](https://github.com/atlassian/yarn-deduplicate) package * deduplicate script has been added as `update-lock`, let me know if you would like also to see this in [`postinstall`](https://docs.npmjs.com/misc/scripts) (to automatically optimize lock on every dependency change) * according to the [npm docs](https://docs.npmjs.com/files/package.json#repository): * main `package.json` repository field has been replaced with shorthand * monorepo packages repository field has been extended by `directory` The main goal of introducing deduplication script was to optimize the dependencies footprint while developing and speed up the initial installation process. Running `yarn-deduplicate` also increase the security in some way, because it enforces usage only of the latest version of the package. You can read more about the benefits in the deduplicate script [repository](https://github.com/atlassian/yarn-deduplicate#duplicated-packages). ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://github.com/facebook/react-native/wiki/Changelog --> [Internal] [Added] - add yarn lock deduplication script Pull Request resolved: https://github.com/facebook/react-native/pull/30044 Test Plan: `yarn install` was successful, this also should not affect yarn workspaces in any way. Reviewed By: GijsWeterings Differential Revision: D23959812 Pulled By: cpojer fbshipit-source-id: e2455e3718378e1ce6206e79463d4083f8fe5d47
2020-09-29 08:39:27 +03:00
"update-lock": "npx yarn-deduplicate",
Reduce flakyness by not downloading extra packages (#36077) Summary: Yesterday CircleCI was extremely flaky due to us trying to `apt install` extra packages. This mitigates one scenario where we try to redownload `jq` and `shellcheck`. I've moved to use a container which contains those packages already ## Changelog [INTERNAL] - Reduce flakyness by not downloading extra packages Pull Request resolved: https://github.com/facebook/react-native/pull/36077 Test Plan: Will wait for a green CI Reviewed By: cipolleschi Differential Revision: D43080349 Pulled By: cortinico fbshipit-source-id: 6527c5ad129f47d8b5f02bf207e1af67a095afa1
2023-02-07 18:22:30 +03:00
"docker-setup-android": "docker pull reactnativecommunity/react-native-android:7.0",
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",
infra(e2e): rework local E2E script (#34513) Summary: This is a long time coming effort to improve the situation around the local e2e script that in the release crew: the current bash-based script is quirky at best, and what you end up generating as a sample project is not really a true sample project. This is where this PR comes in: it migrates the flow from `./scripts/test-manual-e2e.sh` to `yarn test-e2e-local <options>`. Here's the current shape of the options: ```sh Options: --help Show help [boolean] --version Show version number [boolean] -t, --target [choices: "RNTester", "RNTestProject"] [default: "RNTester"] -p, --platform [choices: "iOS", "Android"] [default: "iOS"] -h, --hermes [boolean] [default: true] ``` The idea is to change it so that you can just run the script, and it will do that one specific thing "well", without the tester needing to do anything aside from actually testing the app once it's open. Some of the key changes: * tries to stick to the patterns of the other established *.js based scripts, in terms of tooling and approach (and even refactor parts that can be shared with other scripts) - like the android artifacts generation * no need to start the android emulator on the side * no need to start Metro on the side * RNTester iOS will open up on the simulator (no Xcode open that then you need to press) Things that still need work: * see the #fixme and #todo in comments * because we rely on exec, the output sent back is not formatted/shaped correctly so it's a bit more noisy/chaotic - but can't handle it right now because the package we use doesn't allow it - see https://github.com/shelljs/shelljs/issues/86 ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [Internal] [Changed] - Migrate bash E2E local testing script to new JS based command Pull Request resolved: https://github.com/facebook/react-native/pull/34513 Test Plan: To test the script, you can run it passing the options showed above; this is the current situation: * RNTester iOS Hermes ✅ * RNTester Android Hermes ✅ * RNTester iOS JSC ✅ * RNTester Android JSC ✅ * RNTestProject Android Hermes ✅ * RNTestProject iOS Hermes ✅ * RNTestProject Android JSC ✅ * RNTestProject iOS JSC ✅ Reviewed By: cortinico Differential Revision: D39814692 Pulled By: cortinico fbshipit-source-id: d4791798aaad764c6a3757269b7636f847ccf2ca
2022-10-04 14:56:44 +03:00
"test-e2e-local": "node ./scripts/test-e2e-local.js",
"test-e2e-local-clean": "node ./scripts/test-e2e-local-clean.js",
Move TypeScript declarations into react-native (#34614) Summary: ## Changelog [General] [Added] - Add `types` folder to house TypeScript types. Release TypesScript types with react-native and eventually deprecate [types/react-native](https://www.npmjs.com/package/types/react-native). The current plan is to release types/react-native for 0.70 and 0.71 while also maintaining types here. This will result in some double maintenance until 0.72 but will give community time to move off of types/react-native. After this lands, there have been changes on `main` of types that we need to update. Then, when we release 0.71 from DefinitelyTyped, we can simply copy over the `types` folder from this repo. Pull Request resolved: https://github.com/facebook/react-native/pull/34614 Test Plan: `yarn run test-typescript` for linting types * Created a new project using the TS template and my local clone of `react-native` on this branch. `npx react-native init MyTSApp --version <path-to-my-local-rn-repo> --template react-native-template-typescript` * Updated the `package.json` to remove `types/react-native` * Deleted my node_modules and re-ran yarn * Opened MyTSApp in VSCode and verified the type suggestions appeared and cmd+click to defnitions took me to the node_module dependency `react-native/types` ## Danger is failing on this PR and it's expected as it runs off the changes on `main`. [This is expected](https://docs.github.com/en/github-ae@latest/actions/using-workflows/events-that-trigger-workflows?fbclid=IwAR2_AE0Jwndt8Gu-iTQnxGxLJq7nakbi7sz8jwZ6U62JWLSdcZuvjcQ6WvE#pull_request_target). However testing it locally passes. Once merged, and these changes are on `main`, danger will pass again. ``` $ react-native/packages/react-native-bots ❯ yarn danger pr https://github.com/facebook/react-native/pull/34614 yarn run v1.22.19 $ ..react-native/node_modules/.bin/danger pr https://github.com/facebook/react-native/pull/34614 Starting Danger PR on facebook/react-native#34614 Danger: ✓ found only warnings, not failing the build ## Warnings :lock: package.json - <i>Changes were made to package.json. This will require a manual import by a Facebook employee.</i> ✨ Done in 13.24s. ``` Reviewed By: mdvacca Differential Revision: D39479137 Pulled By: lunaleaps fbshipit-source-id: 1d506f812d566b783b6e79104cd6339b077a42a7
2022-09-19 22:26:00 +03:00
"test-ios": "./scripts/objc-test.sh test",
Fix Errors with TypeScript Tests Summary: This fixes some style errors found by dtslint, along with some test cases for StyleSheet.compose() where the recent change made it slightly too permissive when explicit return types are given. I also added runs of the TS tests to a script which runs in sandcastle so we can catch this at diff-submission time in the future. Changelog: [General][Fixed] - Fix Errors with TypeScript Tests Reviewed By: lunaleaps Differential Revision: D42085257 fbshipit-source-id: 7e6ca49d3c3aef822c61c97ecc07b55b0a949d51
2022-12-16 06:17:58 +03:00
"test-typescript": "dtslint types",
feat(react-native-github): a script to automate patch version bumping of packages (#35767) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/35767 Changelog: [Internal] Introducing a script, which can be used to identify all packages inside `/packages`, which contain any changes after the last time its version was changed How it works step by step: ``` check that no git changes are present for each package: if package is private -> skip grep id of the last commit that changed package grep id of the last commit that changed version of the package if these ids are different: bump package patch version commit changes if required ``` Can be executed only in git environment and by running: `node ./scripts/bump-all-updated-packages` --- Also adding a separate script `align-package-versions.js`, which can be used to update versions of packages inside consumer packages ``` check that no git changes are present for each package x: for each package y: if y has x as dependency: validate that y uses the latest version of x if some changes were made: run yarn ``` --- Q: Why `run_yarn` step was removed from CircleCI flow? A: For *-stable branches, there are no yarn workspaces and all packages are specified as direct dependencies, so if we update `react-native/assets-registry` to the next version, we won't be able to run `yarn` for react-native root package, because updated version is not yet published to npm To avoid this, we first need publish new versions and then update them in consumer packages --- The final flow: 1. Developer uses `node ./scripts/bump-all-updated-packages` to bump versions of all updated packages. 2. Commit created from step 1 being merged or directly pushed to `main` or `*-stable` branches 3. A workflow from CircleCI publishes all updated versions to npm 4. Developer can use `align-package-versions.js` script to create required changes to align all packages versions Reviewed By: cortinico Differential Revision: D42295344 fbshipit-source-id: 54b667adb3ee5f28d19ee9c7991570451549aac2
2023-01-11 00:23:06 +03:00
"test-typescript-offline": "dtslint --localTs node_modules/typescript/lib types",
"bump-all-updated-packages": "node ./scripts/monorepo/bump-all-updated-packages",
"align-package-versions": "node ./scripts/monorepo/align-package-versions.js"
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 07:10:52 +03:00
},
Split React Native repo into product/infra packages Summary: Changelog: [Internal] Reviewed By: TheSavior Differential Revision: D23165627 fbshipit-source-id: f371c070f8b297c218d2989ff3b553a8b83c18ea
2020-08-18 22:07:57 +03:00
"workspaces": [
Configure `@react-native-community/eslint-config` as a yarn workspace (#34423) Summary: Changes the React Native base ESLint configuration to consume `react-native-community/eslint-config` as a [yarn workspace](https://classic.yarnpkg.com/lang/en/docs/workspaces/), so that any dependencies of `react-native-community/eslint-config` can also be resolved from the root directory of `react-native`. Previously, `~/.eslintrc.js` extended `react-native-community/eslint-config` using a relative file path. This is problematic because if any dependencies (notably, optional peer dependencies such as some of the TypeScript dependencies) are not already installed at the root directory of `react-native`, running ESLint could fail to resolve any required dependencies. In other words, there was an implicit dependency that `react-native/yarn.lock` would also contain any dependencies required by `react-native/packages/eslint-config-react-native-community/yarn.lock`. With this change, running `yarn` from the root directory of `react-native` will also install any dependencies of `react-native-community/eslint-config`, and it will also symlink `react-native/node_modules/react-native-community/eslint-config` to `../../packages/eslint-config-react-native-community` (meaning any local changes to the config will still be reflected during active development). ## Changelog [Internal] Pull Request resolved: https://github.com/facebook/react-native/pull/34423 Test Plan: Successfully install dependencies and run ESLint. ``` $ cd react-native $ yarn $ yarn lint ``` Successfully run Danger on https://github.com/facebook/react-native/pull/34401 (which would previously fail because `typescript-eslint/eslint-plugin` could not be resolved from the root directory of `react-native`): ``` $ cd react-native/bots $ yarn $ node ./node_modules/.bin/danger pr https://github.com/facebook/react-native/pull/34401 ``` Reviewed By: NickGerleman Differential Revision: D38710285 Pulled By: yungsters fbshipit-source-id: a06ceea0884a90be60f6f5db9a5d42be52a951d5
2022-08-16 04:48:01 +03:00
"packages/*",
Split React Native repo into product/infra packages Summary: Changelog: [Internal] Reviewed By: TheSavior Differential Revision: D23165627 fbshipit-source-id: f371c070f8b297c218d2989ff3b553a8b83c18ea
2020-08-18 22:07:57 +03:00
"repo-config"
],
Fixed package.json peerDependencies Reviewed By: sophiebits Differential Revision: D5860751 fbshipit-source-id: 634ccf22d40bf80eabed467cb1c874f5b02c4f8d
2017-09-20 01:39:18 +03:00
"peerDependencies": {
React Native sync for revisions d300ceb...9e3b772 Summary: Sync goes to v18.2 release. I had to manually trigger CircleCI builds because TTL for build artefacts is 30 days. This sync includes the following changes: - **[060505e9d](https://github.com/facebook/react/commit/060505e9d )**: Fix misapplying prod error opt-out ([#24688](https://github.com/facebook/react/pull/24688)) //<Josh Story>// - **[47944142f](https://github.com/facebook/react/commit/47944142f )**: `now` isn't part of the react-reconciler config anymore ([#24689](https://github.com/facebook/react/pull/24689)) //<Mathieu Dutour>// - **[b34552352](https://github.com/facebook/react/commit/b34552352 )**: [Fizz] Support abort reasons ([#24680](https://github.com/facebook/react/pull/24680)) //<Josh Story>// - **[79f54c16d](https://github.com/facebook/react/commit/79f54c16d )**: Bugfix: Revealing a hidden update ([#24685](https://github.com/facebook/react/pull/24685)) //<Andrew Clark>// - **[7e8a020a4](https://github.com/facebook/react/commit/7e8a020a4 )**: Remove extra Server Context argument ([#24683](https://github.com/facebook/react/pull/24683)) //<Sebastian Markbåge>// - **[4f29ba1cc](https://github.com/facebook/react/commit/4f29ba1cc )**: support errorInfo in onRecoverableError ([#24591](https://github.com/facebook/react/pull/24591)) //<Josh Story>// - **[1cd90d2cc](https://github.com/facebook/react/commit/1cd90d2cc )**: Refactor of interleaved ("concurrent") update queue ([#24663](https://github.com/facebook/react/pull/24663)) //<Andrew Clark>// Changelog: [General][Changed] - React Native sync for revisions d300ceb...9e3b772 jest_e2e[run_all_tests] Reviewed By: JoshuaGross Differential Revision: D38496392 fbshipit-source-id: 3ecffc2b3354104562eb23a2643fe0a37a01a7e6
2022-08-09 02:44:55 +03:00
"react": "18.2.0"
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": {
Update Jest to ^29.2.1 (#35014) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/35014 X-link: https://github.com/facebook/metro/pull/881 Following on from https://github.com/facebook/react-native/pull/34724 and https://github.com/facebook/react-native/pull/34972, this updates Jest to the latest version 29.2.1 across projects and in the OSS React Native new app template. Importantly this version includes the [new `jest.now()` API](https://github.com/facebook/jest/pull/13245), which will be useful for exposing internally consistent fake timer mocks of `requestAnimationFrame`, etc., in the new React Native Jest environment. Changelog: [General] [Changed] - Upgrade Jest in React Native template to ^29.2.1 Reviewed By: jacdebug Differential Revision: D40386349 fbshipit-source-id: 43f5a69cf546df09e2f02542ebf50130d65f0436
2022-10-19 22:17:39 +03:00
"@jest/create-cache-key-function": "^29.2.1",
chore(dependencies): bump CLI to 11 alpha2 and metro to 0.75.1 (#36271) Summary: Ahead of cut of RN 0.72, I'm upgrading CLI and Metro according to https://github.com/react-native-community/cli/releases/tag/v11.0.0-alpha.2 ~While working on it, I noticed that run-ios has some changes that make the e2e test script not work super well, so I'll be checking in with the CLI team to figure out what's wrong. Let's not merge it until that's address it. (also, there's already a bump for Metro that we need https://github.com/react-native-community/cli/commit/8d18baef554423904c036cbeaa5a1ea92603ff5d so I'll probably change the version to latest CLI and Metro once more)~ (all addressed) ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [GENERAL] [CHANGED] - bump CLI to 11 alphav2 and metro to 0.75.1 Pull Request resolved: https://github.com/facebook/react-native/pull/36271 Test Plan: Test CI, and locally I've used the e2e test script to ensure everything still works. Reviewed By: NickGerleman Differential Revision: D43625952 Pulled By: cipolleschi fbshipit-source-id: dad940b65c56a586ae82acc2e7c16a918b872ee5
2023-02-28 14:18:06 +03:00
"@react-native-community/cli": "11.0.0-alpha.2",
"@react-native-community/cli-platform-android": "11.0.0-alpha.2",
"@react-native-community/cli-platform-ios": "11.0.0-alpha.2",
Rename `assets` to `assets-registry` (#34572) Summary: Part of the [monorepo RFC](https://github.com/react-native-community/discussions-and-proposals/blob/04671deebe4ef2af782e281bbd912a8597c5af96/proposals/0006-react-native-monorepo.md) ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [General] [Changed] - Rename assets to assets-registry Pull Request resolved: https://github.com/facebook/react-native/pull/34572 Reviewed By: cortinico Differential Revision: D39235817 Pulled By: hoxyq fbshipit-source-id: ff4d4a7ff980d3fc6e28b83ad3b36250eba79fc3
2022-11-30 23:25:02 +03:00
"@react-native/assets-registry": "^0.72.0",
Bump all the usages of published packages in the monorepo (#36356) Summary: This bumps all the usages of the packages in the monorepo to the latest published. ## Changelog [INTERNAL] - Bump all the usages of published packages Pull Request resolved: https://github.com/facebook/react-native/pull/36356 Test Plan: n/a Reviewed By: jacdebug Differential Revision: D43735714 Pulled By: cortinico fbshipit-source-id: 746af2a2f34e65e1093d0670cd79dae5484f21c2
2023-03-03 01:25:58 +03:00
"@react-native/gradle-plugin": "^0.72.5",
Update all package usage on main after a bump (#36200) Summary: This updates all the package usages after the recent bump on main. ## Changelog [INTERNAL] - Update all package usage on main after a bump Pull Request resolved: https://github.com/facebook/react-native/pull/36200 Test Plan: Relying on CI Reviewed By: hoxyq Differential Revision: D43397084 Pulled By: cortinico fbshipit-source-id: 06a13772a627f812d7d39931f32071fa3eaa59f9
2023-02-18 01:10:15 +03:00
"@react-native/js-polyfills": "^0.72.1",
chore: rename normalize-color to normalize-colors (umbrella 480) (#34571) Summary: ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [General] [Changed] - Rename normalize-color to normalize-colors as part of https://github.com/react-native-community/discussions-and-proposals/pull/480 Pull Request resolved: https://github.com/facebook/react-native/pull/34571 Reviewed By: cortinico Differential Revision: D39235696 Pulled By: hoxyq fbshipit-source-id: b6d5fcae9fb5c953c2f7b48f73a95cd883ff8f63
2022-12-01 19:46:57 +03:00
"@react-native/normalize-colors": "^0.72.0",
Bump all the usages of published packages in the monorepo (#36356) Summary: This bumps all the usages of the packages in the monorepo to the latest published. ## Changelog [INTERNAL] - Bump all the usages of published packages Pull Request resolved: https://github.com/facebook/react-native/pull/36356 Test Plan: n/a Reviewed By: jacdebug Differential Revision: D43735714 Pulled By: cortinico fbshipit-source-id: 746af2a2f34e65e1093d0670cd79dae5484f21c2
2023-03-03 01:25:58 +03:00
"@react-native/virtualized-lists": "^0.72.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
"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",
RN: Upgrade to deprecated-react-native-prop-types@4.0.0 Summary: Upgrades `react-native` to `deprecated-react-native-prop-types@4.0.0`, which depends on `react-native/normalize-colors` instead of `react-native/normalize-color` and improves compatibility with React Native 0.72. Changelog: [General][Changed] Upgraded to `deprecated-react-native-prop-types@4.0.0` - https://github.com/facebook/react-native-deprecated-modules/blob/main/deprecated-react-native-prop-types/CHANGELOG.md Reviewed By: cortinico Differential Revision: D42088315 fbshipit-source-id: d1197e9a7d70654f601b421231b66bd760098ddf
2022-12-16 13:36:02 +03:00
"deprecated-react-native-prop-types": "^4.0.0",
Deploy 0.163.0 to xplat Summary: Changelog: [Internal] Reviewed By: evanyeung Differential Revision: D32025457 fbshipit-source-id: f2c08e4baa9a39731ab970b917d2c67c852e9603
2021-10-30 05:04:26 +03:00
"event-target-shim": "^5.0.1",
react-native code-gen > C++ TurboModules enum example (#36083) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/36083 Changelog: [Internal] Reviewed By: javache Differential Revision: D43036612 fbshipit-source-id: fc70650bc4ba48d11f489556d1290ae9e7e58016
2023-02-09 07:24:28 +03:00
"flow-enums-runtime": "^0.0.5",
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",
Update Jest to ^29.2.1 (#35014) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/35014 X-link: https://github.com/facebook/metro/pull/881 Following on from https://github.com/facebook/react-native/pull/34724 and https://github.com/facebook/react-native/pull/34972, this updates Jest to the latest version 29.2.1 across projects and in the OSS React Native new app template. Importantly this version includes the [new `jest.now()` API](https://github.com/facebook/jest/pull/13245), which will be useful for exposing internally consistent fake timer mocks of `requestAnimationFrame`, etc., in the new React Native Jest environment. Changelog: [General] [Changed] - Upgrade Jest in React Native template to ^29.2.1 Reviewed By: jacdebug Differential Revision: D40386349 fbshipit-source-id: 43f5a69cf546df09e2f02542ebf50130d65f0436
2022-10-19 22:17:39 +03:00
"jest-environment-node": "^29.2.1",
update jsc-android to ndk r23 based (#36062) Summary: the current jsc-android is still built based on ndk r21, and react-native is now built based on ndk r23. the unwinder between r21 and r23 is incompatible (libgcc vs libunwind). if there's exceptions throwing from jsc, other react native libraries cannot catch these exceptions and cause runtime crash. this pr updates jsc-android to 235231.0.0 which is the same webkitgtk version as 235230.2.1 but only built by ndk r23. the jsc-android pr is from https://github.com/react-native-community/jsc-android-buildscripts/pull/179. note that the jsc is based on ndk r23c and react-native is based on ndk r23b. the reason is that i cannot get jsc building successfully on r23b. hopefully r23b and r23c are abi safe. there is another crash from libjscexecutor when testing the new jsc-android. to fix the issue, i have to explicitly link libunwind.a from libjscexecutor.so. supposedly ndk r23 should help to link libunwind under the hood, i still not figure out why it doesn't. but after linking libunwind.a, i can get new jsc-android work successfully. ``` E/art ( 2669): dlopen("/data/app/com.test-1/lib/x86_64/libjscexecutor.so", RTLD_LAZY) failed: dlopen failed: cannot locate symbol "_Unwind_Resume" referenced by "/data/app/com.test-1/lib/x86_64/libjscexecutor.so"... W/System.err( 2669): java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_Unwind_Resume" referenced by "/data/app/com.test-1/lib/x86_64/libjscexecutor.so"... W/System.err( 2669): at java.lang.Runtime.load(Runtime.java:331) W/System.err( 2669): at java.lang.System.load(System.java:982) W/System.err( 2669): at com.facebook.soloader.SoLoader$1.load(SoLoader.java:558) W/System.err( 2669): at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:110) W/System.err( 2669): at com.facebook.soloader.DirectorySoSource.loadLibrary(DirectorySoSource.java:63) W/System.err( 2669): at com.facebook.soloader.ApplicationSoSource.loadLibrary(ApplicationSoSource.java:91) W/System.err( 2669): at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1067) W/System.err( 2669): at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:943) W/System.err( 2669): at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:855) W/System.err( 2669): at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:802) W/System.err( 2669): at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:772) W/System.err( 2669): at com.facebook.react.jscexecutor.JSCExecutor.loadLibrary(JSCExecutor.java:24) W/System.err( 2669): at com.facebook.react.jscexecutor.JSCExecutor.<clinit>(JSCExecutor.java:20) W/System.err( 2669): at com.facebook.react.ReactInstanceManagerBuilder.getDefaultJSExecutorFactory(ReactInstanceManagerBuilder.java:363) W/System.err( 2669): at com.facebook.react.ReactInstanceManagerBuilder.build(ReactInstanceManagerBuilder.java:316) W/System.err( 2669): at com.facebook.react.ReactNativeHost.createReactInstanceManager(ReactNativeHost.java:94) W/System.err( 2669): at com.facebook.react.ReactNativeHost.getReactInstanceManager(ReactNativeHost.java:41) W/System.err( 2669): at com.test.MainApplication.onCreate(MainApplication.java:60) W/System.err( 2669): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1011) W/System.err( 2669): at androidx.test.runner.MonitoringInstrumentation.callApplicationOnCreate(MonitoringInstrumentation.java:483) W/System.err( 2669): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4518) W/System.err( 2669): at android.app.ActivityThread.access$1500(ActivityThread.java:144) W/System.err( 2669): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1339) W/System.err( 2669): at android.os.Handler.dispatchMessage(Handler.java:102) W/System.err( 2669): at android.os.Looper.loop(Looper.java:135) W/System.err( 2669): at android.app.ActivityThread.main(ActivityThread.java:5221) W/System.err( 2669): at java.lang.reflect.Method.invoke(Native Method) W/System.err( 2669): at java.lang.reflect.Method.invoke(Method.java:372) W/System.err( 2669): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:899) W/System.err( 2669): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:694) ``` fixes https://github.com/facebook/react-native/issues/36052 ## Changelog [ANDROID][FIXED] - Fixed jscexecutor crash on Android which is caused from NDK incompatibility Pull Request resolved: https://github.com/facebook/react-native/pull/36062 Test Plan: tested on [jsc-android instrumented test](https://github.com/react-native-community/jsc-android-buildscripts/tree/2.26.1/test) (based on react-native 0.71.2) Reviewed By: cipolleschi Differential Revision: D43040295 Pulled By: cortinico fbshipit-source-id: e0e5b8fb7faa8ee5654d4cde5f274bef4b517376
2023-02-07 20:33:44 +03:00
"jsc-android": "^250231.0.0",
VirtualizedList optimization - memoize FlatList._renderer Summary: Problem: All CellRenderers rerender every time the containing VirtualizedList is rerendered. This is due to the following: - Lambda is created for each CellRenderer's onLayout prop on every VirtualizedList render (fixed in D35061321 (https://github.com/facebook/react-native/commit/19cf70266eb8ca151aa0cc46ac4c09cb987b2ceb)) - CellRenderer's parentProps prop changes on every VirtualizedList render (fixed in D35062323 (https://github.com/facebook/react-native/commit/adb2962fee968d7ae20ec32a55dc69e4ebb3ce12)) - FlatList recreates renderItem/ListItemComponent in FlatList._renderer (addressed in this diff) Changelog: [Internal] - VirtualizedList optimization - memoize FlatList._renderer Reviewed By: ryancat Differential Revision: D35067472 fbshipit-source-id: 124629d94821f35b8943730839fbe72f547e80fd
2022-03-24 23:14:37 +03:00
"memoize-one": "^5.0.0",
chore(dependencies): bump CLI to 11 alpha2 and metro to 0.75.1 (#36271) Summary: Ahead of cut of RN 0.72, I'm upgrading CLI and Metro according to https://github.com/react-native-community/cli/releases/tag/v11.0.0-alpha.2 ~While working on it, I noticed that run-ios has some changes that make the e2e test script not work super well, so I'll be checking in with the CLI team to figure out what's wrong. Let's not merge it until that's address it. (also, there's already a bump for Metro that we need https://github.com/react-native-community/cli/commit/8d18baef554423904c036cbeaa5a1ea92603ff5d so I'll probably change the version to latest CLI and Metro once more)~ (all addressed) ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [GENERAL] [CHANGED] - bump CLI to 11 alphav2 and metro to 0.75.1 Pull Request resolved: https://github.com/facebook/react-native/pull/36271 Test Plan: Test CI, and locally I've used the e2e test script to ensure everything still works. Reviewed By: NickGerleman Differential Revision: D43625952 Pulled By: cipolleschi fbshipit-source-id: dad940b65c56a586ae82acc2e7c16a918b872ee5
2023-02-28 14:18:06 +03:00
"metro-react-native-babel-transformer": "0.75.1",
"metro-runtime": "0.75.1",
"metro-source-map": "0.75.1",
Fix Circle CI test_ios_template (#33761) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/33761 Changelog: [General][Fixed] - Add 'mkdirp' as a direct dependency to 'react-native' instead of assuming it being a transitive dependency of some other module. Reviewed By: cortinico, cipolleschi Differential Revision: D36138320 fbshipit-source-id: b2421aa6b22fca0b813bbb5bb0c7213540ca578d
2022-05-08 19:10:25 +03:00
"mkdirp": "^0.5.1",
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 26.5.2. Summary: Changelog: [Internal] Reviewed By: kacieb Differential Revision: D24154865 fbshipit-source-id: 04d637a3944b6f030fee342c4e8a181eb4b14458
2020-10-07 12:12:30 +03:00
"pretty-format": "^26.5.2",
Add support `Promise.any` out of box (#35080) Summary: `promise` module diff: [`8.2.0...8.3.0`](https://npmfs.com/compare/promise/8.2.0/8.3.0/) - Hermes issue: https://github.com/facebook/hermes/issues/766 ## Changelog [General] [Added] - Added support `Promise.any` Pull Request resolved: https://github.com/facebook/react-native/pull/35080 Test Plan: Release notes [`promise@8.3.0`](https://github.com/then/promise/releases/tag/8.3.0) ```tsx typeof Promise.any // function ``` Reviewed By: cortinico Differential Revision: D40681373 Pulled By: jacdebug fbshipit-source-id: ecd589186483f3aa0f48da28a1f6dfcb1e26c8bc
2022-10-27 15:39:36 +03:00
"promise": "^8.3.0",
Upgrade react-devtools-core to 4.27.2 Summary: This diff upgrade dependencies to `react-devtools-core` to 4.27.2, which includes changes I need to unblock trace update highlights. - Update package.json file for dependencies in all existing deps with latest version (4.26.1): https://fburl.com/code/litgze0m - Run `yarn` under `xplat/js` and `xplat/js/public` Changelog: [General][Internal] - Upgrade react-devtools-core to 4.27.2 Reviewed By: javache Differential Revision: D43176345 fbshipit-source-id: 8bd5a9eca286bbfbb1630cb92c15f9653fa3534a
2023-02-13 21:49:13 +03:00
"react-devtools-core": "^4.27.2",
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",
React Native sync for revisions bd4784c...d300ceb Summary: This sync includes the following changes: - **[dd4950c90](https://github.com/facebook/react/commit/dd4950c90 )**: [Flight] Implement useId hook ([#24172](https://github.com/facebook/react/pull/24172)) //<Josh Story>// - **[26a5b3c7f](https://github.com/facebook/react/commit/26a5b3c7f )**: Explicitly set `highWaterMark` to 0 for `ReadableStream` ([#24641](https://github.com/facebook/react/pull/24641)) //<Josh Larson>// - **[aec575914](https://github.com/facebook/react/commit/aec575914 )**: [Fizz] Send errors down to client ([#24551](https://github.com/facebook/react/pull/24551)) //<Josh Story>// - **[a2766387e](https://github.com/facebook/react/commit/a2766387e )**: [Fizz] Improve text separator byte efficiency ([#24630](https://github.com/facebook/react/pull/24630)) //<Josh Story>// - **[f7860538a](https://github.com/facebook/react/commit/f7860538a )**: Fix typo in useSyncExternalStore main entry point error ([#24631](https://github.com/facebook/react/pull/24631)) //<François Chalifour>// - **[1bed20731](https://github.com/facebook/react/commit/1bed20731 )**: Add a module map option to the Webpack Flight Client ([#24629](https://github.com/facebook/react/pull/24629)) //<Sebastian Markbåge>// - **[b2763d3ea](https://github.com/facebook/react/commit/b2763d3ea )**: Move hydration code out of normal Suspense path ([#24532](https://github.com/facebook/react/pull/24532)) //<Andrew Clark>// - **[357a61324](https://github.com/facebook/react/commit/357a61324 )**: [DevTools][Transition Tracing] Added support for Suspense Boundaries ([#23365](https://github.com/facebook/react/pull/23365)) //<Luna Ruan>// - **[2c8a1452b](https://github.com/facebook/react/commit/2c8a1452b )**: Fix ignored setState in Safari when iframe is touched ([#24459](https://github.com/facebook/react/pull/24459)) //<dan>// - **[62662633d](https://github.com/facebook/react/commit/62662633d )**: Remove enableFlipOffscreenUnhideOrder ([#24545](https://github.com/facebook/react/pull/24545)) //<Ricky>// - **[34da5aa69](https://github.com/facebook/react/commit/34da5aa69 )**: Only treat updates to lazy as a new mount in legacy mode ([#24530](https://github.com/facebook/react/pull/24530)) //<Ricky>// - **[46a6d77e3](https://github.com/facebook/react/commit/46a6d77e3 )**: Unify JSResourceReference Interfaces ([#24507](https://github.com/facebook/react/pull/24507)) //<Timothy Yung>// - **[6cbf0f7fa](https://github.com/facebook/react/commit/6cbf0f7fa )**: Fork ReactSymbols ([#24484](https://github.com/facebook/react/pull/24484)) //<Ricky>// - **[a10a9a6b5](https://github.com/facebook/react/commit/a10a9a6b5 )**: Add test for hiding children after layout destroy ([#24483](https://github.com/facebook/react/pull/24483)) //<Ricky>// - **[b4eb0ad71](https://github.com/facebook/react/commit/b4eb0ad71 )**: Do not replay erroring beginWork with invokeGuardedCallback when suspended or previously errored ([#24480](https://github.com/facebook/react/pull/24480)) //<Josh Story>// - **[99eef9e2d](https://github.com/facebook/react/commit/99eef9e2d )**: Hide children of Offscreen after destroy effects ([#24446](https://github.com/facebook/react/pull/24446)) //<Ricky>// - **[ce1386028](https://github.com/facebook/react/commit/ce1386028 )**: Remove enablePersistentOffscreenHostContainer flag ([#24460](https://github.com/facebook/react/pull/24460)) //<Andrew Clark>// - **[72b7462fe](https://github.com/facebook/react/commit/72b7462fe )**: Bump local package.json versions for 18.1 release ([#24447](https://github.com/facebook/react/pull/24447)) //<Andrew Clark>// - **[22edb9f77](https://github.com/facebook/react/commit/22edb9f77 )**: React `version` field should match package.json ([#24445](https://github.com/facebook/react/pull/24445)) //<Andrew Clark>// - **[6bf3deef5](https://github.com/facebook/react/commit/6bf3deef5 )**: Upgrade react-shallow-renderer to support react 18 ([#24442](https://github.com/facebook/react/pull/24442)) //<Michael サイトー 中村 Bashurov>// Changelog: [General][Changed] - React Native sync for revisions bd4784c...d300ceb jest_e2e[run_all_tests] Reviewed By: cortinico, kacieb Differential Revision: D36874368 fbshipit-source-id: c0ee015f4ef2fa56e57f7a1f6bc37dd05c949877
2022-06-06 20:58:29 +03:00
"react-shallow-renderer": "^16.15.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",
React Native sync for revisions d300ceb...9e3b772 Summary: Sync goes to v18.2 release. I had to manually trigger CircleCI builds because TTL for build artefacts is 30 days. This sync includes the following changes: - **[060505e9d](https://github.com/facebook/react/commit/060505e9d )**: Fix misapplying prod error opt-out ([#24688](https://github.com/facebook/react/pull/24688)) //<Josh Story>// - **[47944142f](https://github.com/facebook/react/commit/47944142f )**: `now` isn't part of the react-reconciler config anymore ([#24689](https://github.com/facebook/react/pull/24689)) //<Mathieu Dutour>// - **[b34552352](https://github.com/facebook/react/commit/b34552352 )**: [Fizz] Support abort reasons ([#24680](https://github.com/facebook/react/pull/24680)) //<Josh Story>// - **[79f54c16d](https://github.com/facebook/react/commit/79f54c16d )**: Bugfix: Revealing a hidden update ([#24685](https://github.com/facebook/react/pull/24685)) //<Andrew Clark>// - **[7e8a020a4](https://github.com/facebook/react/commit/7e8a020a4 )**: Remove extra Server Context argument ([#24683](https://github.com/facebook/react/pull/24683)) //<Sebastian Markbåge>// - **[4f29ba1cc](https://github.com/facebook/react/commit/4f29ba1cc )**: support errorInfo in onRecoverableError ([#24591](https://github.com/facebook/react/pull/24591)) //<Josh Story>// - **[1cd90d2cc](https://github.com/facebook/react/commit/1cd90d2cc )**: Refactor of interleaved ("concurrent") update queue ([#24663](https://github.com/facebook/react/pull/24663)) //<Andrew Clark>// Changelog: [General][Changed] - React Native sync for revisions d300ceb...9e3b772 jest_e2e[run_all_tests] Reviewed By: JoshuaGross Differential Revision: D38496392 fbshipit-source-id: 3ecffc2b3354104562eb23a2643fe0a37a01a7e6
2022-08-09 02:44:55 +03:00
"scheduler": "^0.23.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
"stacktrace-parser": "^0.1.3",
Replace use-subscripton with use-sync-external-store (#33770) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/33770 React has replaced use-subscription with the React 18 compatible use-sync-external-store. Changelog: [General][Changed] - Replace use-subscripton with use-sync-external-store Reviewed By: ryancat Differential Revision: D35592432 fbshipit-source-id: cc2016f66940e53f3614e110bafb02240bae1ae4
2022-05-06 05:58:19 +03:00
"use-sync-external-store": "^1.0.0",
Split React Native repo into product/infra packages Summary: Changelog: [Internal] Reviewed By: TheSavior Differential Revision: D23165627 fbshipit-source-id: f371c070f8b297c218d2989ff3b553a8b83c18ea
2020-08-18 22:07:57 +03:00
"whatwg-fetch": "^3.0.0",
Move yargs to a dependency to avoid script failures (#35912) Summary: yargs depdendency is unavailable on npm ci breaking certain CI builds. Fixes https://github.com/facebook/react-native/issues/35893#issuecomment-1397494372 Changelog: [Internal] Prevent script failures on certain npm CI setups Pull Request resolved: https://github.com/facebook/react-native/pull/35912 Test Plan: waitforsandcastle Reviewed By: hoxyq Differential Revision: D43730837 Pulled By: cortinico fbshipit-source-id: 926182ee8482cd0c7fd183ea3e993a9322680567
2023-03-02 16:48:23 +03:00
"ws": "^6.2.2",
"yargs": "^17.6.2"
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
},
Add react back to dev dependencies for RNTester Summary: This is a partial revert of D23165627 (https://github.com/facebook/react-native/commit/f3930a93d5cf5f19058b0bfe453c7b9324eb8552) which broke RNTester testing internally. Changelog: [Internal] Reviewed By: mdvacca, cpojer Differential Revision: D23267175 fbshipit-source-id: d0d7010d00cf65497731dd973094fe334215044b
2020-08-22 00:56:29 +03:00
"devDependencies": {
Deploy v0.200.0 to xplat Reviewed By: mroch Differential Revision: D43377809 fbshipit-source-id: fb95e86a1d5155f45104dca2a9a5989f0acea827
2023-02-18 03:47:34 +03:00
"flow-bin": "^0.200.0",
switch from babel-eslint to hermes-eslint for flow code Summary: `hermes-eslint` is built by Meta to work with the latest Flow code. It follows the latest ESLint standards and AST, and has a true scope analyser to ensure best compatibility with core ESLint rules. Reviewed By: motiz88 Differential Revision: D37181192 fbshipit-source-id: 1f59e01f306792e67a4977435c5c77e0000d960a
2022-06-16 20:12:58 +03:00
"hermes-eslint": "0.8.0",
fix(dependencies): move mockfs to the right package.json (#35476) Summary: While working on 0.71 we noticed that we were hitting a "mock-fs not found" issue on CI, caused by the fact that the dependency was set in the wrong spot. This PR backports to main the fix: https://github.com/facebook/react-native/commit/05646f8f38b65abb9487a348d0ba7e02a35751d9 & https://github.com/facebook/react-native/commit/ceaebc69759e59bfc465722924fee98f2deac825 This is related to the black magics of repo-config, and the fact that devDeps from repo-config don't get propagated back to the root package.json when on stable branch. Because of that, this commit doesn't NOT have a yarn.lock entry (the dep is there in main). I'm confused as to how that dep ended in the devDeps of repo config, it seems something went wrong in migrating some commits from GH to monorepo and back? check out: * https://github.com/facebook/react-native/pull/34580 * https://github.com/facebook/react-native/commit/f0ffd2291c850682e293d9a9ca3dbe7f46bf2e25 ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [Internal] [Changed] - move mockfs to the right package.json Pull Request resolved: https://github.com/facebook/react-native/pull/35476 Test Plan: N/A, change is transparent Reviewed By: cortinico, cipolleschi, dmytrorykun Differential Revision: D41530265 Pulled By: jacdebug fbshipit-source-id: ec7a6426d9a2a766a98a3cccc339ca7ca090c3a0
2022-11-25 19:10:19 +03:00
"mock-fs": "^5.1.4",
React Native sync for revisions d300ceb...9e3b772 Summary: Sync goes to v18.2 release. I had to manually trigger CircleCI builds because TTL for build artefacts is 30 days. This sync includes the following changes: - **[060505e9d](https://github.com/facebook/react/commit/060505e9d )**: Fix misapplying prod error opt-out ([#24688](https://github.com/facebook/react/pull/24688)) //<Josh Story>// - **[47944142f](https://github.com/facebook/react/commit/47944142f )**: `now` isn't part of the react-reconciler config anymore ([#24689](https://github.com/facebook/react/pull/24689)) //<Mathieu Dutour>// - **[b34552352](https://github.com/facebook/react/commit/b34552352 )**: [Fizz] Support abort reasons ([#24680](https://github.com/facebook/react/pull/24680)) //<Josh Story>// - **[79f54c16d](https://github.com/facebook/react/commit/79f54c16d )**: Bugfix: Revealing a hidden update ([#24685](https://github.com/facebook/react/pull/24685)) //<Andrew Clark>// - **[7e8a020a4](https://github.com/facebook/react/commit/7e8a020a4 )**: Remove extra Server Context argument ([#24683](https://github.com/facebook/react/pull/24683)) //<Sebastian Markbåge>// - **[4f29ba1cc](https://github.com/facebook/react/commit/4f29ba1cc )**: support errorInfo in onRecoverableError ([#24591](https://github.com/facebook/react/pull/24591)) //<Josh Story>// - **[1cd90d2cc](https://github.com/facebook/react/commit/1cd90d2cc )**: Refactor of interleaved ("concurrent") update queue ([#24663](https://github.com/facebook/react/pull/24663)) //<Andrew Clark>// Changelog: [General][Changed] - React Native sync for revisions d300ceb...9e3b772 jest_e2e[run_all_tests] Reviewed By: JoshuaGross Differential Revision: D38496392 fbshipit-source-id: 3ecffc2b3354104562eb23a2643fe0a37a01a7e6
2022-08-09 02:44:55 +03:00
"react": "18.2.0",
"react-test-renderer": "^18.2.0"
Add react back to dev dependencies for RNTester Summary: This is a partial revert of D23165627 (https://github.com/facebook/react-native/commit/f3930a93d5cf5f19058b0bfe453c7b9324eb8552) which broke RNTester testing internally. Changelog: [Internal] Reviewed By: mdvacca, cpojer Differential Revision: D23267175 fbshipit-source-id: d0d7010d00cf65497731dd973094fe334215044b
2020-08-22 00:56:29 +03:00
},
Utility script to discover codegen-enabled libraries Summary: Adds utility script which crawls through a React Native app's Node dependencies and, for each compatible library, generates the relevant native code artifacts. This script is for development purposes, and is not hooked into the existing codegen integration by design. Changelog: [Internal] Reviewed By: sota000 Differential Revision: D28915433 fbshipit-source-id: de36d3e1dc0e11aad3ca55cea5e6731db09c5377
2021-10-22 01:22:50 +03:00
"codegenConfig": {
"libraries": [
{
"name": "FBReactNativeSpec",
Add libraryType support to Codegen Shared Configs Summary: Update codegen library discovery script to use libraryType param and new output location. Changelog: [Internal] Reviewed By: sota000 Differential Revision: D31842556 fbshipit-source-id: b811e6d18fcdd59e7d77c6d59dc6017d418531eb
2021-11-05 21:28:13 +03:00
"type": "modules",
"ios": {},
Utility script to discover codegen-enabled libraries Summary: Adds utility script which crawls through a React Native app's Node dependencies and, for each compatible library, generates the relevant native code artifacts. This script is for development purposes, and is not hooked into the existing codegen integration by design. Changelog: [Internal] Reviewed By: sota000 Differential Revision: D28915433 fbshipit-source-id: de36d3e1dc0e11aad3ca55cea5e6731db09c5377
2021-10-22 01:22:50 +03:00
"android": {},
"jsSrcsDir": "Libraries"
},
{
"name": "rncore",
Add libraryType support to Codegen Shared Configs Summary: Update codegen library discovery script to use libraryType param and new output location. Changelog: [Internal] Reviewed By: sota000 Differential Revision: D31842556 fbshipit-source-id: b811e6d18fcdd59e7d77c6d59dc6017d418531eb
2021-11-05 21:28:13 +03:00
"type": "components",
"ios": {},
Utility script to discover codegen-enabled libraries Summary: Adds utility script which crawls through a React Native app's Node dependencies and, for each compatible library, generates the relevant native code artifacts. This script is for development purposes, and is not hooked into the existing codegen integration by design. Changelog: [Internal] Reviewed By: sota000 Differential Revision: D28915433 fbshipit-source-id: de36d3e1dc0e11aad3ca55cea5e6731db09c5377
2021-10-22 01:22:50 +03:00
"android": {},
"jsSrcsDir": "Libraries"
}
]
[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
}