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

46 lines
2.1 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",
Bump babel-preset-react-native version to 5.0.0 for Babel 7 Reviewed By: rafeca Differential Revision: D7685340 fbshipit-source-id: f229fb5da71f2f1d277d3d55eaa0f400aa76471b
2018-04-19 10:53:40 +00:00
"version": "5.0.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 to MIT license Summary: Manual changes. Reviewed By: TheSavior, yungsters Differential Revision: D7012152 fbshipit-source-id: de7459be3db13c687868b45059856f125c4f2eb1
2018-02-17 02:25:02 +00:00
"license": "MIT",
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": {
Lock down Babel to 7-beta.40 Summary: This will lock down the plugins to babel version 7-beta.40 Reviewed By: davidaurelio Differential Revision: D7707160 fbshipit-source-id: 6aec7f98348cac6ddd680c73ea4e36e0fb23e2a8
2018-04-20 12:06:41 +00:00
"@babel/plugin-proposal-class-properties": "7.0.0-beta.40",
"@babel/plugin-proposal-object-rest-spread": "7.0.0-beta.40",
"@babel/plugin-transform-arrow-functions": "7.0.0-beta.40",
"@babel/plugin-transform-block-scoping": "7.0.0-beta.40",
"@babel/plugin-transform-classes": "7.0.0-beta.40",
"@babel/plugin-transform-computed-properties": "7.0.0-beta.40",
"@babel/plugin-transform-destructuring": "7.0.0-beta.40",
"@babel/plugin-transform-exponentiation-operator": "7.0.0-beta.40",
"@babel/plugin-transform-flow-strip-types": "7.0.0-beta.40",
"@babel/plugin-transform-for-of": "7.0.0-beta.40",
"@babel/plugin-transform-function-name": "7.0.0-beta.40",
"@babel/plugin-transform-literals": "7.0.0-beta.40",
"@babel/plugin-transform-modules-commonjs": "7.0.0-beta.40",
"@babel/plugin-transform-object-assign": "7.0.0-beta.40",
"@babel/plugin-transform-parameters": "7.0.0-beta.40",
"@babel/plugin-transform-react-display-name": "7.0.0-beta.40",
"@babel/plugin-transform-react-jsx": "7.0.0-beta.40",
"@babel/plugin-transform-react-jsx-source": "7.0.0-beta.40",
"@babel/plugin-transform-regenerator": "7.0.0-beta.40",
"@babel/plugin-transform-shorthand-properties": "7.0.0-beta.40",
"@babel/plugin-transform-spread": "7.0.0-beta.40",
"@babel/plugin-transform-sticky-regex": "7.0.0-beta.40",
"@babel/plugin-transform-template-literals": "7.0.0-beta.40",
"@babel/plugin-transform-unicode-regex": "7.0.0-beta.40",
"@babel/template": "7.0.0-beta.40",
Bump metro@0.34.0 Differential Revision: D7708906 fbshipit-source-id: 3d8cdfd2745baf73c92f90e0960f7cd73a289f77
2018-04-20 21:03:35 +00:00
"metro-babel7-plugin-react-transform": "0.34.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
}
}