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

47 lines
2.0 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",
Fixed HMR for React Native Android Summary:Needs to be published to npm and version be updated in RN Closes https://github.com/facebook/react-native/pull/7208 Differential Revision: D3218870 Pulled By: davidaurelio fb-gh-sync-id: 1caac6eb79be16f2e3ed230f413835341c7291dc fbshipit-source-id: 1caac6eb79be16f2e3ed230f413835341c7291dc
2016-04-25 13:30:37 +00:00
"version": "1.6.0",
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": {
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",
"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",
Add transform-es2015-function-name to the react-native babel preset. Fixes #6716 Summary:Stateless function components (at least those using arrow functions) are not assigned names when this transform is omitted. Rebased against master and kept the original author from #6717 cc martinbigio bestander Closes https://github.com/facebook/react-native/pull/6794 Differential Revision: D3133791 Pulled By: mkonicek fb-gh-sync-id: bb7790ad17d1520da5ab95580548d29d0c0f397d fbshipit-source-id: bb7790ad17d1520da5ab95580548d29d0c0f397d
2016-04-13 14:40:47 +00:00
"babel-plugin-transform-es2015-function-name": "^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-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",
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
"babel-plugin-transform-es2015-constants": "^6.1.4",
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-destructuring": "^6.5.0",
"babel-plugin-transform-es2015-for-of": "^6.5.0",
"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",
"babel-plugin-transform-react-jsx": "^6.5.0",
"babel-plugin-transform-regenerator": "^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
"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
}
}