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/babel-preset/package.json

51 lines
2.2 KiB
JSON
Raw Normal View History

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
{
"name": "babel-preset-react-native",
react-native: release new babel-preset version Summary: The `3.0.0` contained syntax errors for older versions of Node. See also https://github.com/facebook/react-native/issues/15496 Reviewed By: cpojer Differential Revision: D5677965 fbshipit-source-id: cae07fdce7e887c6fb1d6087791db8307f6f72f3
2017-08-22 13:43:27 +00:00
"version": "3.0.1",
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
"description": "Babel preset for React Native applications",
"main": "index.js",
"repository": "https://github.com/facebook/react-native/tree/master/babel-preset",
"keywords": [
"babel",
"preset",
"react-native"
],
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
"license": "BSD-3-Clause",
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
"bugs": {
"url": "https://github.com/facebook/react-native/issues"
},
"homepage": "https://github.com/facebook/react-native/tree/master/babel-preset/README.md",
"dependencies": {
babel-preset - transform-es2015-constants was replaced by check-es2015-constants. Summary: The babel plugin transform-es2015-constants was replaced by check-es2015-constants. References: T2970 rBW0a3b3b03dbcfc8d1e809a0eaf6270eec8de80763 T3053 This patch updates the babel preset to use check-es2015-constants which should be more future-proof and will receive bug fixes. Closes https://github.com/facebook/react-native/pull/6943 Reviewed By: davidaurelio Differential Revision: D3189222 Pulled By: bestander fb-gh-sync-id: a5ec23e297e1d3591d51641dd567049f4310b107 fbshipit-source-id: a5ec23e297e1d3591d51641dd567049f4310b107
2016-05-03 13:42:08 +00:00
"babel-plugin-check-es2015-constants": "^6.5.0",
Update hot reloading dependencies Summary:These updates include important changes to correctness in the linked and underlying packages: * https://github.com/gaearon/babel-plugin-react-transform/releases/tag/v2.0.1 * https://github.com/gaearon/babel-plugin-react-transform/releases/tag/v2.0.2 * https://github.com/gaearon/react-proxy/releases/tag/v1.1.3 * https://github.com/gaearon/react-proxy/releases/tag/v1.1.4 * etc We need to include these if we want to ship hot reloading. Create a new project with those versions of packages. <img width="761" alt="screen shot 2016-03-06 at 18 49 20" src="https://cloud.githubusercontent.com/assets/810438/13556222/2d45ca62-e3cc-11e5-8a3f-a2346efe19dd.png"> Verify hot reloading still works. ![](http://cl.ly/2J150y0Y3E1z/download/Screen%20Recording%202016-03-06%20at%2018.48.gif) martinbigio skevy I wasn’t sure whether to touch the shrinkwrap. Closes https://github.com/facebook/react-native/pull/6325 Reviewed By: yungsters Differential Revision: D3019470 Pulled By: martinbigio fb-gh-sync-id: 99bad390cd898f58aa7f74494066561a81eb40e6 shipit-source-id: 99bad390cd898f58aa7f74494066561a81eb40e6
2016-03-12 00:27:18 +00:00
"babel-plugin-react-transform": "2.0.2",
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-plugin-syntax-async-functions": "^6.5.0",
"babel-plugin-syntax-class-properties": "^6.5.0",
RN babel preset: add import() syntax Summary: Allows us to parse the `import()` syntax. For now it's not transformed, so it would crash at runtime (or at minification with UglifyJS). However I want to release this under a new major version, so this wouldn't be allowed in OSS right away. Also we bump to version 3.0.0 before release. D5443966 possibly introduced breaking changes, so it needs a major bump. Reviewed By: cpojer Differential Revision: D5630084 fbshipit-source-id: b271bbb8577ba7184e975f996ec415a915e869d9
2017-08-15 15:08:53 +00:00
"babel-plugin-syntax-dynamic-import": "^6.18.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-plugin-syntax-flow": "^6.5.0",
"babel-plugin-syntax-jsx": "^6.5.0",
"babel-plugin-syntax-trailing-function-commas": "^6.5.0",
"babel-plugin-transform-class-properties": "^6.5.0",
"babel-plugin-transform-es2015-arrow-functions": "^6.5.0",
"babel-plugin-transform-es2015-block-scoping": "^6.5.0",
"babel-plugin-transform-es2015-classes": "^6.5.0",
"babel-plugin-transform-es2015-computed-properties": "^6.5.0",
"babel-plugin-transform-es2015-destructuring": "^6.5.0",
"babel-plugin-transform-es2015-for-of": "^6.5.0",
Fixing Issue #7526 Summary: Thanks for submitting a pull request! Please provide enough information so that others can review your pull request: Fixing a bug detailed in Issue #7526 where Android app was crashing when using a binary number. **Test plan:** - Build & Run UIExplorer - Build & Run UIExplorer with `const binaryNumber = 0b101010` inserted into UIExplorerApp.android.js - Use `react-native init` to create a new blank project, then replace files in node_modules and insert `const binaryNumber = 0b101010` into index.android.js. Closes https://github.com/facebook/react-native/pull/7730 Reviewed By: avaly Differential Revision: D3353119 Pulled By: bestander fbshipit-source-id: 098442da32a29c369f5932b7a4004e8d7f4cb91f
2016-05-26 20:36:31 +00:00
"babel-plugin-transform-es2015-function-name": "^6.5.0",
"babel-plugin-transform-es2015-literals": "^6.5.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-plugin-transform-es2015-modules-commonjs": "^6.5.0",
"babel-plugin-transform-es2015-parameters": "^6.5.0",
"babel-plugin-transform-es2015-shorthand-properties": "^6.5.0",
"babel-plugin-transform-es2015-spread": "^6.5.0",
"babel-plugin-transform-es2015-template-literals": "^6.5.0",
"babel-plugin-transform-flow-strip-types": "^6.5.0",
"babel-plugin-transform-object-assign": "^6.5.0",
"babel-plugin-transform-object-rest-spread": "^6.5.0",
"babel-plugin-transform-react-display-name": "^6.5.0",
Add transform-react-jsx-source to react-native preset Summary: Putting this up as request for comments. The PR adds [transform-react-jsx-source](https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-react-jsx-source) to the list of plugins that come by default with the `react-native` preset. It will enable the use of a bunch of really cool tooling around JSX, however those are generally useful only in development mode. Is changing `react-native` preset the right thing to do in this case? Is there a way to enable this transform only in DEV? Should I add this somewhere else? Closes https://github.com/facebook/react-native/pull/6351 Differential Revision: D3302906 Pulled By: frantic fbshipit-source-id: 012d3a4142168f9f90d30d1686115d4dc3996eb9
2016-05-18 19:32:20 +00:00
"babel-plugin-transform-react-jsx-source": "^6.5.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-plugin-transform-react-jsx": "^6.5.0",
"babel-plugin-transform-regenerator": "^6.5.0",
metro-bundler: transform import() to basic require() Reviewed By: mjesun Differential Revision: D5631078 fbshipit-source-id: a8d4955a723c1846b9406e734c3e3fa2c0df3fb7
2017-08-16 11:26:31 +00:00
"babel-template": "^6.24.1",
Update hot reloading dependencies Summary:These updates include important changes to correctness in the linked and underlying packages: * https://github.com/gaearon/babel-plugin-react-transform/releases/tag/v2.0.1 * https://github.com/gaearon/babel-plugin-react-transform/releases/tag/v2.0.2 * https://github.com/gaearon/react-proxy/releases/tag/v1.1.3 * https://github.com/gaearon/react-proxy/releases/tag/v1.1.4 * etc We need to include these if we want to ship hot reloading. Create a new project with those versions of packages. <img width="761" alt="screen shot 2016-03-06 at 18 49 20" src="https://cloud.githubusercontent.com/assets/810438/13556222/2d45ca62-e3cc-11e5-8a3f-a2346efe19dd.png"> Verify hot reloading still works. ![](http://cl.ly/2J150y0Y3E1z/download/Screen%20Recording%202016-03-06%20at%2018.48.gif) martinbigio skevy I wasn’t sure whether to touch the shrinkwrap. Closes https://github.com/facebook/react-native/pull/6325 Reviewed By: yungsters Differential Revision: D3019470 Pulled By: martinbigio fb-gh-sync-id: 99bad390cd898f58aa7f74494066561a81eb40e6 shipit-source-id: 99bad390cd898f58aa7f74494066561a81eb40e6
2016-03-12 00:27:18 +00:00
"react-transform-hmr": "^1.0.4"
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
}
}