status-im
/
react-native
mirror of https://github.com/status-im/react-native.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
react-native/package.json

191 lines
5.5 KiB
JSON
Raw Normal View History

[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
{
[ReactNative] Remove react-native/package.json
2015-03-23 03:32:49 +00:00
"name": "react-native",
Set the versions in package.json and React.podspec to 0.0.0-master Summary: The current versions in these files is 0.12.0, which is out of date. Better to claim no version than the wrong version, so this diff changes the versions to 0.0.0-master. Release branches will still have the correct versions. Closes https://github.com/facebook/react-native/pull/5241 Reviewed By: svcscm Differential Revision: D2819277 Pulled By: javache fb-gh-sync-id: 99d4682e5d1f571e241f306caf309b2944483909
2016-01-13 12:57:14 +00:00
"version": "0.0.0-master",
[React Native] Sync from github
2015-03-28 05:18:47 +00:00
"description": "A framework for building native apps using React",
Add the license field on package.json Summary: Add the license field on package.json Closes https://github.com/facebook/react-native/pull/1409 Github Author: Leonardo YongUk Kim <dalinaum@gmail.com> Test Plan: Imported from GitHub, without a `Test Plan:` line.
2015-05-28 18:48:58 +00:00
"license": "BSD-3-Clause",
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
"repository": {
"type": "git",
"url": "git@github.com:facebook/react-native.git"
},
Add Node >= 4 requirement to package.json and packager/package.json Summary: When you try to install these with old Node you'll now get a message from npm telling you that your version of Node is old. This makes it more obvious what's going on and hopefully reduces the number of issues we get due to people using an old version of Node. Closes https://github.com/facebook/react-native/pull/3296 Reviewed By: @​svcscm Differential Revision: D2526500 Pulled By: @vjeux fb-gh-sync-id: 036e10a8d1819ea082e419cd328a458202f0e071
2015-10-09 21:42:33 +00:00
"engines": {
"node": ">=4"
},
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
"jest": {
Simplify jest config + update to jest 0.5.5 in react-native-github Reviewed By: @DmitrySoshnikov Differential Revision: D2445071
2015-09-16 04:49:56 +00:00
"scriptPreprocessor": "jestSupport/preprocessor.js",
[react-packager] Fix jest tests
2015-02-25 20:57:33 +00:00
"setupEnvScriptFile": "jestSupport/env.js",
Add moduleNameMapper config Summary: This adds the moduleNameMapper config which corresponds to the same config in flow. public Reviewed By: voideanvalue Differential Revision: D2582879 fb-gh-sync-id: f116b86a7d4196c39faa366a521fe8401769b173
2015-10-27 00:01:41 +00:00
"moduleNameMapper": {
"^image![a-zA-Z0-9$_-]+$": "GlobalImageStub",
"^[./a-zA-Z0-9$_-]+\\.png$": "RelativeImageStub"
},
Update all tests to use Jasmine 2 Reviewed By: vjeux Differential Revision: D2782581 fb-gh-sync-id: 1d938a2bbdd8670c917c1793234dfdcb29fd4511
2015-12-22 19:40:16 +00:00
"testRunner": "<rootDir>/node_modules/jest-cli/src/testRunners/jasmine/jasmine2.js",
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
"testPathIgnorePatterns": [
Codemod tests to use top-level-requires Reviewed By: @DmitrySoshnikov Differential Revision: D2456250
2015-09-18 01:34:14 +00:00
"/node_modules/"
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
],
Update + use node-haste2 Summary:This updates jest to 0.9 which will result in *much* faster startup time (1s vs. 10-15s) and better runtime overall (2-3x). The route gen and cli integration tests are failing locally, but also on master. javache is this expected right now or is this related to my changes? Reviewed By: javache Differential Revision: D2943137 fb-gh-sync-id: 8b39ba5f51e30fbc5bacb84d67013ab0a4061f6e shipit-source-id: 8b39ba5f51e30fbc5bacb84d67013ab0a4061f6e
2016-02-18 08:12:42 +00:00
"haste": {
"defaultPlatform": "ios",
"providesModuleNodeModules": [
"fbjs",
"react",
"react-native",
"parse",
"react-transform-hmr"
],
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 12:15:15 +00:00
"platforms": [
"ios",
"android"
]
Update + use node-haste2 Summary:This updates jest to 0.9 which will result in *much* faster startup time (1s vs. 10-15s) and better runtime overall (2-3x). The route gen and cli integration tests are failing locally, but also on master. javache is this expected right now or is this related to my changes? Reviewed By: javache Differential Revision: D2943137 fb-gh-sync-id: 8b39ba5f51e30fbc5bacb84d67013ab0a4061f6e shipit-source-id: 8b39ba5f51e30fbc5bacb84d67013ab0a4061f6e
2016-02-18 08:12:42 +00:00
},
Updates for haste2 inside of jest Summary: I'm working on deploying haste2 with jest. This updates all the files that require changes for this to work and they are backwards compatible with the current version of jest. * package.json was just outdated. I think haste1's liberal handling with collisions made this a "non-issue" * env.js didn't properly set up ErrorUtils, also unsure why that isn't a problem in jest right now already? * some things were mocking things they shouldn't * Because of the regex that matches against providesModule and System.import, it isn't possible to list module names more than once. We have multiple tests reusing the same providesModule ids and using System.import with modules that only exist virtually within that test. Splitting up the strings makes the regexes work (we do the same kind of splitting on www sometimes if we need to) and using different providesModule names in different test files fixes the problem. I think the BundlesLayoutIntegration-test is going to be deleted, so this doesn't even matter. public Reviewed By: voideanvalue Differential Revision: D2809681 fb-gh-sync-id: 8fe6ed8b5a1be28ba141e9001de143e502693281
2016-01-08 14:51:45 +00:00
"modulePathIgnorePatterns": [
Hotfix jest startup time Summary: I talked about this a bunch before. node-haste2 will resolve this issue. Right now node-haste1 looks into eevery single node_module recursively even though we only need to look into a finite-set of them. Some node_modules are huge so it takes a long time. haste2 doesn't eagerly look into node_modules so it doesn't have this issue. This diff blacklists the modules from node-haste but since we use the `resolve` npm module as a fallback we'll still be able to require them. public Reviewed By: kassens Differential Revision: D2852384 fb-gh-sync-id: 113f1bd9c66fcd712c2549a7110a3e752b0e4a69
2016-01-22 19:34:19 +00:00
"/node_modules/(?!react|fbjs|react-native|parse|react-transform-hmr|core-js|promise)/",
Remove knowledge of fbjs from the packager Summary:Follow-up to https://github.com/facebook/react-native/pull/5084 This… - changes all requires within RN to `require('fbjs/lib/…')` - updates `.flowconfig` - updates `packager/blacklist.js` - adapts tests - removes things from `Libraries/vendor/{core,emitter}` that are also in fbjs - removes knowledge of `fbjs` from the packager Closes https://github.com/facebook/react-native/pull/5084 Reviewed By: bestander Differential Revision: D2926835 fb-gh-sync-id: 2095e22b2f38e032599d1f2601722b3560e8b6e9 shipit-source-id: 2095e22b2f38e032599d1f2601722b3560e8b6e9
2016-03-02 12:27:13 +00:00
"node_modules/react/node_modules/fbjs/",
Updates for haste2 inside of jest Summary: I'm working on deploying haste2 with jest. This updates all the files that require changes for this to work and they are backwards compatible with the current version of jest. * package.json was just outdated. I think haste1's liberal handling with collisions made this a "non-issue" * env.js didn't properly set up ErrorUtils, also unsure why that isn't a problem in jest right now already? * some things were mocking things they shouldn't * Because of the regex that matches against providesModule and System.import, it isn't possible to list module names more than once. We have multiple tests reusing the same providesModule ids and using System.import with modules that only exist virtually within that test. Splitting up the strings makes the regexes work (we do the same kind of splitting on www sometimes if we need to) and using different providesModule names in different test files fixes the problem. I think the BundlesLayoutIntegration-test is going to be deleted, so this doesn't even matter. public Reviewed By: voideanvalue Differential Revision: D2809681 fb-gh-sync-id: 8fe6ed8b5a1be28ba141e9001de143e502693281
2016-01-08 14:51:45 +00:00
"node_modules/react/lib/React.js",
"node_modules/react/lib/ReactDOM.js",
"node_modules/fbjs/lib/Map.js",
"node_modules/fbjs/lib/Promise.js",
"node_modules/fbjs/lib/fetch.js",
"node_modules/fbjs/lib/ErrorUtils.js",
"node_modules/fbjs/lib/URI.js",
"node_modules/fbjs/lib/Deferred.js",
"node_modules/fbjs/lib/PromiseMap.js",
"node_modules/fbjs/lib/UserAgent.js",
"node_modules/fbjs/lib/areEqual.js",
"node_modules/fbjs/lib/base62.js",
"node_modules/fbjs/lib/crc32.js",
"node_modules/fbjs/lib/everyObject.js",
"node_modules/fbjs/lib/fetchWithRetries.js",
"node_modules/fbjs/lib/filterObject.js",
"node_modules/fbjs/lib/flattenArray.js",
"node_modules/fbjs/lib/forEachObject.js",
"node_modules/fbjs/lib/isEmpty.js",
"node_modules/fbjs/lib/nullthrows.js",
"node_modules/fbjs/lib/removeFromArray.js",
"node_modules/fbjs/lib/resolveImmediate.js",
"node_modules/fbjs/lib/someObject.js",
"node_modules/fbjs/lib/sprintf.js",
"node_modules/fbjs/lib/xhrSimpleDataSerializer.js",
"downstream/core/CSSCore.js",
"downstream/core/TouchEventUtils.js",
"downstream/core/camelize.js",
"downstream/core/createArrayFromMixed.js",
"downstream/core/createNodesFromMarkup.js",
"downstream/core/dom/containsNode.js",
"downstream/core/dom/focusNode.js",
"downstream/core/dom/getActiveElement.js",
"downstream/core/dom/getUnboundedScrollPosition.js",
"downstream/core/dom/isNode.js",
"downstream/core/dom/isTextNode.js",
"downstream/core/emptyFunction.js",
"downstream/core/emptyObject.js",
"downstream/core/getMarkupWrap.js",
"downstream/core/hyphenate.js",
"downstream/core/hyphenateStyleName.js",
"downstream/core/invariant.js",
"downstream/core/nativeRequestAnimationFrame.js",
"downstream/core/toArray.js",
"node_modules/jest-cli",
Remove knowledge of fbjs from the packager Summary:Follow-up to https://github.com/facebook/react-native/pull/5084 This… - changes all requires within RN to `require('fbjs/lib/…')` - updates `.flowconfig` - updates `packager/blacklist.js` - adapts tests - removes things from `Libraries/vendor/{core,emitter}` that are also in fbjs - removes knowledge of `fbjs` from the packager Closes https://github.com/facebook/react-native/pull/5084 Reviewed By: bestander Differential Revision: D2926835 fb-gh-sync-id: 2095e22b2f38e032599d1f2601722b3560e8b6e9 shipit-source-id: 2095e22b2f38e032599d1f2601722b3560e8b6e9
2016-03-02 12:27:13 +00:00
"node_modules/react/dist",
"/node_modules/fbjs/.*/__mocks__/"
Updates for haste2 inside of jest Summary: I'm working on deploying haste2 with jest. This updates all the files that require changes for this to work and they are backwards compatible with the current version of jest. * package.json was just outdated. I think haste1's liberal handling with collisions made this a "non-issue" * env.js didn't properly set up ErrorUtils, also unsure why that isn't a problem in jest right now already? * some things were mocking things they shouldn't * Because of the regex that matches against providesModule and System.import, it isn't possible to list module names more than once. We have multiple tests reusing the same providesModule ids and using System.import with modules that only exist virtually within that test. Splitting up the strings makes the regexes work (we do the same kind of splitting on www sometimes if we need to) and using different providesModule names in different test files fixes the problem. I think the BundlesLayoutIntegration-test is going to be deleted, so this doesn't even matter. public Reviewed By: voideanvalue Differential Revision: D2809681 fb-gh-sync-id: 8fe6ed8b5a1be28ba141e9001de143e502693281
2016-01-08 14:51:45 +00:00
],
[react-packager][cleanup options 1/2] add npm installed joi validation library
2015-02-19 21:11:11 +00:00
"testFileExtensions": [
"js"
[react-packager] Fix jest tests
2015-02-25 20:57:33 +00:00
],
"unmockedModulePathPatterns": [
[ReactNative] Disable mocking "promise" in OSS Jest tests
2015-06-24 18:01:09 +00:00
"promise",
Improve performance of node-haste2 and react-packager Reviewed By: davidaurelio Differential Revision: D2911210 fb-gh-sync-id: 8ac2f213e8a9e089281bb065f9a7190d2e0f5b18 shipit-source-id: 8ac2f213e8a9e089281bb065f9a7190d2e0f5b18
2016-02-16 06:33:11 +00:00
"source-map",
Remove knowledge of fbjs from the packager Summary:Follow-up to https://github.com/facebook/react-native/pull/5084 This… - changes all requires within RN to `require('fbjs/lib/…')` - updates `.flowconfig` - updates `packager/blacklist.js` - adapts tests - removes things from `Libraries/vendor/{core,emitter}` that are also in fbjs - removes knowledge of `fbjs` from the packager Closes https://github.com/facebook/react-native/pull/5084 Reviewed By: bestander Differential Revision: D2926835 fb-gh-sync-id: 2095e22b2f38e032599d1f2601722b3560e8b6e9 shipit-source-id: 2095e22b2f38e032599d1f2601722b3560e8b6e9
2016-03-02 12:27:13 +00:00
"fast-path",
"fbjs"
[react-packager][cleanup options 1/2] add npm installed joi validation library
2015-02-19 21:11:11 +00:00
]
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
},
[ReactNative] Remove react-native/package.json
2015-03-23 03:32:49 +00:00
"main": "Libraries/react-native/react-native.js",
[ReactNative] Update package.json to be npm-ready
2015-03-26 01:18:41 +00:00
"files": [
[ReactNative] s/ReactKit/React/g
2015-03-26 09:58:06 +00:00
"React",
[podspec] Include podspec in npm distribution Summary: The way RCT_EXPORT_MODULE currently works, any module that is included as a pod also needs react itself to be included as a pod. npm seems to be the preferred way to get the latest copy of react (compared to github directly or the cocoapods repo) so what this diff enables is including react as a pod if it was installed via npm. Closes https://github.com/facebook/react-native/pull/1057 Github Author: James Ide <ide@jameside.com> Test Plan: Imported from GitHub, without a `Test Plan:` line.
2015-04-29 15:21:44 +00:00
"React.podspec",
Also release Android sources to npm Summary:Turns out also having sources (besides binaries in /android) in npm is useful: https://facebook.github.io/react-native/docs/android-building-from-source.html Reviewed By: mkonicek Differential Revision:D2947237 Ninja: oss-only fb-gh-sync-id: 80e3e79c9c5a5f54fd54e91ac147249a68c74847 shipit-source-id: 80e3e79c9c5a5f54fd54e91ac147249a68c74847
2016-02-18 00:53:17 +00:00
"ReactAndroid",
Consume Android artifacts from npm Summary: This lets us say goodbye to Maven Central. This will greatly simplify and speed up the release process as releasing Android artifacts to Maven Central adds a lot of [complexity](https://github.com/facebook/react-native/blob/master/Releases-publish.md) and delays the whole release by several hours when we have to wait for the artifacts to propagate. This diff assumes there's a local Maven repo at `node_modules/react-native/android`. The second part once this lands is to change our `release.sh` script to output the artifacts under `react-native/android` before publishing to npm. This adds 3.7MB to the size of `node_modules` of any app. However, we just download eagerly what we'd normally download later via Gradle. **Test plan** Released RN including a local Maven repo into Sinopia: $ cd react-native # Updated version in gradle.properties to 0.21.0 $ ./gradlew ReactAndroid:installArchives # Moved everything in .m2/repository/com/facebook/react to react-native/android $ ls react-native/android com/facebook/react/react-native/0.21.0/react-native-0.21.0.aar com/facebook/react/react-native/0.21.0/react-native-0.21.0.pom com/facebook/react/react-native/maven-metadata.xml ... # Set version in package.json to 0.21.0 $ npm set registry http://localhost:4873/ $ npm publish Created and ran an app: $ cd /tmp $ react-native init AndroidNpm $ cd AndroidNpm $ react-native run-android It worked. Checked that we're using the artifacts from node_modules/react-native/android: $ cd android $ ./gradlew app:dependencies compile - Classpath for compiling the main sources. +--- com.android.support:appcompat-v7:23.0.1 | \--- com.android.support:support-v4:23.0.1 | \--- com.android.support:support-annotations:23.0.1 \--- com.facebook.react:react-native:+ -> 0.21.0 +--- com.google.code.findbugs:jsr305:3.0.0 +--- com.facebook.stetho:stetho-okhttp:1.2.0 ... Checked that Android Studio can find the source jars (you can navigate to RN sources in Android Studio). Opened the new project as described in the [docs](https://facebook.github.io/react-native/docs/android-setup.html#editing-your-app-s-java-code-in-android-studio). public Reviewed By: bestander Differential Revision: D2912557 fb-gh-sync-id: 251c180518a3fb9bb8e80963b236e982d65533be shipit-source-id: 251c180518a3fb9bb8e80963b236e982d65533be
2016-02-09 14:36:30 +00:00
"android",
[ReactNative] Update package.json to be npm-ready
2015-03-26 01:18:41 +00:00
"Libraries",
"packager",
"cli.js",
[ReactNative] Update package.json
2015-04-08 04:36:34 +00:00
"local-cli",
[ReactNative] Update package.json to be npm-ready
2015-03-26 01:18:41 +00:00
"init.sh",
"LICENSE",
[React Native] Sync from github
2015-03-28 05:18:47 +00:00
"PATENTS",
Include jestSupport for npm package Summary: https://github.com/facebook/react-native/pull/1639 was closed for unknown reason. This will help unit test with Jest without manually copying them into node_modules/react-native. Closes https://github.com/facebook/react-native/pull/1848 Github Author: John Ku <john.cmyk@gmail.com>
2015-07-16 01:49:37 +00:00
"README.md",
merge .flowconfig files part 1 Differential Revision: D2472462 committer: Service User <svcscm@fb.com>
2015-09-23 19:59:50 +00:00
"jestSupport",
Add npm-shrinkwrap.json to npm Reviewed By: svcscm Differential Revision: D2933826 fb-gh-sync-id: 48def92bfd9eb929cc092bea90bcbe1ed53f8675 shipit-source-id: 48def92bfd9eb929cc092bea90bcbe1ed53f8675
2016-02-13 23:27:22 +00:00
".flowconfig",
"npm-shrinkwrap.json"
[ReactNative] Update package.json to be npm-ready
2015-03-26 01:18:41 +00:00
],
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
"scripts": {
Codemod tests to use top-level-requires Reviewed By: @DmitrySoshnikov Differential Revision: D2456250
2015-09-18 01:34:14 +00:00
"test": "NODE_ENV=test jest",
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 12:15:15 +00:00
"flow": "flow",
Revert package.json change
2015-12-22 18:32:20 +00:00
"lint": "eslint Examples/ Libraries/",
Don’t report failure to npm-start with arg support Summary: This supports passing args to `npm start` as referenced in [this comment][comment] while still returning 0 on failure from an npm perspective. This builds off the npm change in [this commit][commit] and discussed in this [PR]. [comment]: https://github.com/facebook/react-native/pull/2415#issuecomment-141309448 [commit]: https://github.com/facebook/react-native/commit/75df3b537ae071b0b4d1b01ae75d66ec5457bb1e [PR]: https://github.com/facebook/react-native/pull/2415 Closes https://github.com/facebook/react-native/pull/3002 Reviewed By: svcscm Differential Revision: D2647258 Pulled By: spicyj fb-gh-sync-id: 2385254d23a37a99a53f53308e4688bc1fc3124e
2015-11-12 17:24:44 +00:00
"start": "/usr/bin/env bash -c './packager/packager.sh \"$@\" || true' --"
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
},
Bring back global cli module check Summary: public This was introduced by vjeux on 0a5967d and removed on 0686b01. I guess it was removed accidentally as this this is a nice warning to have that should prevent n00bs from commiting a common mistake Reviewed By: frantic Differential Revision: D2563885 fb-gh-sync-id: 9fae145bbec587514f118d1d28d076b1d82f0630
2015-10-26 18:42:53 +00:00
"bin": {
"react-native": "local-cli/wrong-react-native.js"
},
Move `react` to peerDependencies Summary: This PR moves `react` from dependencies to peerDependencies. In general, this would have only been important for those people using packages that depend on `react` and were using npm@2...npm@3 would automatically de-dupe. However, when #5812 gets merged, dependencies will be scoped to react-native (on both npm@2 & npm@3), thus breaking projects that are using a package like `react-redux` for example, which depends on `react`. There would be two copies of React installed, and due to the use of haste modules in `react`, this would break the packager and cause naming collisions. This PR does three things - 1. Moves the dependency from dependencies to peerDependencies 2. Updates the local-cli to run `npm install react --save` when a new project is initialized. 3. Updates `react-native upgrade` to warn if `react` is not listed in the package.json's dependencies. **Note: This will require a shrinkwrap update.** Closes https://github.com/facebook/react-native/pull/5813 Reviewed By: svcscm Differential Revision: D2918380 Pulled By: androidtrunkagent fb-gh-sync-id: 6e4234a45284be2fdf6fedf29e70b2d2d0262486 shipit-source-id: 6e4234a45284be2fdf6fedf29e70b2d2d0262486
2016-02-09 23:37:28 +00:00
"peerDependencies": {
"react": "^0.14.5"
},
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
"dependencies": {
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"absolute-path": "^0.0.0",
Expose additional private modules Summary: - TextInputState as TextInput.State - Touchable - flattenStyle as StyleSheet.flatten - ReactNativeART as ART Original discussion in #1821 Closes https://github.com/facebook/react-native/pull/3308 Reviewed By: sebmarkbage Differential Revision: D2527152 Pulled By: javache fb-gh-sync-id: 19d4ef9d4c0e6587b9f0793e1ca624aebb034f3b
2015-11-05 11:31:11 +00:00
"art": "^0.10.0",
Update Babel/React Dependencies Summary:PR does as it says -- updates Babel dependencies to latest versions. In general, this changes nothing for 99.9% of users (everyone that isn't FB). If they were to `npm install react-native` right now, they would get all of these dependencies anyway. However, this does revert a previous change where we were using "~" instead of "^" in front of the Babel deps in order to attempt to lock them to minor dependencies. However, due to the fact that each Babel package uses "^", and there are so many interdependencies, this actually would cause an issue where multiple versions of babel-core, et. al. to be installed. *Edit* - In addition, we add React to `devDependencies` so that it behaves properly in testing, now that it's a peer dependency. Closes https://github.com/facebook/react-native/pull/5811 Reviewed By: davidaurelio Differential Revision: D2931184 Pulled By: martinbigio fb-gh-sync-id: 7b9fc640d37fb2d98fc1808860f9f64074aff475 shipit-source-id: 7b9fc640d37fb2d98fc1808860f9f64074aff475
2016-03-04 05:18:49 +00:00
"babel-core": "^6.6.4",
"babel-plugin-external-helpers": "^6.5.0",
"babel-polyfill": "^6.6.1",
"babel-preset-react-native": "^1.5.1",
"babel-register": "^6.6.0",
"babel-types": "^6.6.4",
"babylon": "^6.6.4",
Add support for binary type data (ArrayBuffer) Summary: Entirely based on https://github.com/facebook/react-native/pull/1829 I just updated the diff to be compatible with the current master branch. Closes https://github.com/facebook/react-native/pull/4483 Reviewed By: svcscm Differential Revision: D2783425 Pulled By: nicklockwood fb-gh-sync-id: 1cc67c0741cff3b071530877d688f6b8c1061e3f
2015-12-22 17:22:01 +00:00
"base64-js": "^0.0.8",
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"bser": "^1.0.2",
"chalk": "^1.1.1",
"connect": "^2.8.3",
"debug": "^2.2.0",
Import event-target-shim npm module Reviewed By: @foghina Differential Revision: D2498747
2015-10-01 19:25:28 +00:00
"event-target-shim": "^1.0.5",
Improve performance of node-haste2 and react-packager Reviewed By: davidaurelio Differential Revision: D2911210 fb-gh-sync-id: 8ac2f213e8a9e089281bb065f9a7190d2e0f5b18 shipit-source-id: 8ac2f213e8a9e089281bb065f9a7190d2e0f5b18
2016-02-16 06:33:11 +00:00
"fast-path": "^1.1.0",
Remove knowledge of fbjs from the packager Summary:Follow-up to https://github.com/facebook/react-native/pull/5084 This… - changes all requires within RN to `require('fbjs/lib/…')` - updates `.flowconfig` - updates `packager/blacklist.js` - adapts tests - removes things from `Libraries/vendor/{core,emitter}` that are also in fbjs - removes knowledge of `fbjs` from the packager Closes https://github.com/facebook/react-native/pull/5084 Reviewed By: bestander Differential Revision: D2926835 fb-gh-sync-id: 2095e22b2f38e032599d1f2601722b3560e8b6e9 shipit-source-id: 2095e22b2f38e032599d1f2601722b3560e8b6e9
2016-03-02 12:27:13 +00:00
"fbjs": "^0.7.2",
Bump fbjs-scripts version
2015-11-11 13:41:16 +00:00
"fbjs-scripts": "^0.4.0",
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"graceful-fs": "^4.1.2",
"image-size": "^0.3.5",
"immutable": "^3.7.5",
"joi": "^6.6.1",
Replace custom rolled stable string hashing with library Reviewed By: cpojer Differential Revision: D2937202 fb-gh-sync-id: dc08547c71da2bc35cfad108e63fd5e87f0ba734 shipit-source-id: dc08547c71da2bc35cfad108e63fd5e87f0ba734
2016-02-15 14:57:26 +00:00
"json-stable-stringify": "^1.0.1",
Unbreak jest tests (and travis e2e tests) Reviewed By: mkonicek Differential Revision: D2652002 fb-gh-sync-id: 8aab8da47dd737acc4ee9acddc484bd3bbdf1184
2015-11-14 11:23:46 +00:00
"json5": "^0.4.0",
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"jstransform": "^11.0.3",
Fix Shrinkwrap & package.json Reviewed By: vjeux Differential Revision: D2791699 fb-gh-sync-id: 180687718ded0f4c4078ccf56ca0eb114966c8bf
2015-12-29 17:10:22 +00:00
"mkdirp": "^0.5.1",
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"module-deps": "^3.9.1",
Add `node-fetch` node module to repo Reviewed By: vjeux Differential Revision: D2542225 fb-gh-sync-id: a94e799d5595eb7909b42bc8acb6d80259ca1609
2015-10-19 21:58:38 +00:00
"node-fetch": "^1.3.3",
bump node-haste to 2.4.0 Reviewed By: sam-swarr Differential Revision: D2982427 fb-gh-sync-id: 3a78f6e10c6af8eb92a711dd59760215c3f21b14 shipit-source-id: 3a78f6e10c6af8eb92a711dd59760215c3f21b14
2016-02-26 23:14:44 +00:00
"node-haste": "~2.4.0",
npm install --save opn Reviewed By: mkonicek Differential Revision: D2570884 fb-gh-sync-id: 89f9ab8e8b04081442da28e8c30caa80b454d696
2015-10-23 18:28:48 +00:00
"opn": "^3.0.2",
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"optimist": "^0.6.1",
"progress": "^1.1.8",
Add support for promise rejection tracking Summary: Adds support for tracking unhandled rejections with `console.warn` (= yellow box). I will create a follow-up with proper error stack formatting. related: #4971 fixes: #4045, #4142 public {F59857438} {F59857439} Reviewed By: bestander Differential Revision: D2803126 fb-gh-sync-id: 376b33e42a967675a04338cbff3ec315a77d1037
2016-01-07 17:30:14 +00:00
"promise": "^7.1.1",
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"react-timer-mixin": "^0.13.2",
Use "babel-preset-react-native" Summary: Rather than specifying Babel plugins in the `.babelrc` packaged with react-native, leverage a Babel preset to define the plugins (https://github.com/exponentjs/babel-preset-react-native). This allows for a much better user experience for those who want (or need) to override options in their project's `.babelrc`. Prior to this PR, if a user wanted to use a custom babel-plugin (or a custom set of babel plugins), they'd have either 1) manually override the `.babelrc` in the react-packager directory (or fork RN), or 2) specify a custom transformer to use when running the packager that loaded their own `.babelrc`. Note - the custom transformer was necessary because without it, RN's `.babelrc` options would supersede the options defined in the project's `.babelrc`...potentially causing issues with plugin ordering. This PR makes the transformer check for the existence of a project-level `.babelrc`, and if it it's there, it _doesn't_ use the react-native `.babelrc`. This prevents any oddities with Babel plug Closes https://github.com/facebook/react-native/pull/5214 Reviewed By: davidaurelio Differential Revision: D2881814 Pulled By: martinbigio fb-gh-sync-id: 4168144b7a365fae62bbeed094d8a03a48b4798c
2016-02-03 16:14:38 +00:00
"react-transform-hmr": "^1.0.2",
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"rebound": "^0.0.13",
"regenerator": "^0.8.36",
[react-packager] Update sane to fix bug and add new features Summary: Updates sane to get: 1. Fix error plumbing (surface watchman errors correctly) 2. Better capability testing 3. Use watchman's globbing 4. Other minor fixes
2015-09-08 08:34:44 +00:00
"sane": "^1.2.0",
Fix Shrinkwrap & package.json Reviewed By: vjeux Differential Revision: D2791699 fb-gh-sync-id: 180687718ded0f4c4078ccf56ca0eb114966c8bf
2015-12-29 17:10:22 +00:00
"semver": "^5.0.3",
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"source-map": "^0.4.4",
"stacktrace-parser": "^0.1.3",
Require transform file eagerly in transform worker Summary: One consequence we didn't predict after introducing the Internal Transform Pipeline, was that when the workers would get started, we won't require the external transformer the user specified up until the first time each worker received a job. There're 2 visible consequences of this: (1) the transform progress bar seems to get stuck for about 5 seconds the first time the packager receives a request and (2) the first N (# of cores) HMR requests take way longer (about 4 seconds with FB's transformer instead of << 1 second) as we need to require lots of modules. This diff creates a temporary file for the js transformer workers that requires the user-specified transform file eagerly. That makes sure workers have imported babel and the transforms before receiving the first request. There are better ways to do this, like adding an `init()` method to the workers and call that eagerly. I will follow with another diff doing that. public Reviewed By: javache Differential Revision: D2812153 fb-gh-sync-id: 15be316b792d1acd878ed9303bea398aa0b52e1d
2016-01-08 16:34:52 +00:00
"temp": "0.8.3",
Add Jest test to check dependency version matches. Reviewed By: @vjeux Differential Revision: D2396634
2015-09-11 08:23:38 +00:00
"uglify-js": "^2.4.24",
"underscore": "^1.8.3",
"wordwrap": "^1.0.0",
"worker-farm": "^1.3.1",
"ws": "^0.8.0",
"yargs": "^3.24.0",
"yeoman-environment": "^1.2.7",
"yeoman-generator": "^0.20.3"
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
},
"devDependencies": {
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 12:15:15 +00:00
"babel-eslint": "^5.0.0",
"eslint": "^2.2.0",
"eslint-plugin-react": "^4.1.0",
"flow-bin": "^0.21.0",
Update jest to 0.9.0-fb2 Reviewed By: davidaurelio Differential Revision: D2953741 fb-gh-sync-id: 10a76c7c00f542740eb820c400429ea81a7073ea shipit-source-id: 10a76c7c00f542740eb820c400429ea81a7073ea
2016-02-19 12:40:06 +00:00
"jest-cli": "0.9.0-fb2",
Update Babel/React Dependencies Summary:PR does as it says -- updates Babel dependencies to latest versions. In general, this changes nothing for 99.9% of users (everyone that isn't FB). If they were to `npm install react-native` right now, they would get all of these dependencies anyway. However, this does revert a previous change where we were using "~" instead of "^" in front of the Babel deps in order to attempt to lock them to minor dependencies. However, due to the fact that each Babel package uses "^", and there are so many interdependencies, this actually would cause an issue where multiple versions of babel-core, et. al. to be installed. *Edit* - In addition, we add React to `devDependencies` so that it behaves properly in testing, now that it's a peer dependency. Closes https://github.com/facebook/react-native/pull/5811 Reviewed By: davidaurelio Differential Revision: D2931184 Pulled By: martinbigio fb-gh-sync-id: 7b9fc640d37fb2d98fc1808860f9f64074aff475 shipit-source-id: 7b9fc640d37fb2d98fc1808860f9f64074aff475
2016-03-04 05:18:49 +00:00
"portfinder": "0.4.0",
"react": "^0.14.5"
[react-packager][streamline oss] Move open sourced JS source to react-native-github
2015-02-20 04:10:52 +00:00
}
}