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/react-native-git-upgrade/package.json

31 lines
709 B
JSON
Raw Normal View History

New upgrading process, relying on Git Summary: The upgrading process based on Yeoman is a pain. For each file, Yeoman (or the brand new copyAndReplace solution a477aec) compares the newly generated content with the existing one and prompts the user if it differs, with very basic options: overwrite or skip. I have digged into this problem and came with [rn-diff](https://github.com/ncuillery/rn-diff) (you may have read [this article](https://medium.com/ncuillery/easier-react-native-upgrades-with-rn-diff-5020b5c3de2d#.llvy2dym5)). This repository helps people to upgrade RN on their projects. An alternative upgrading process using `git apply` instead of Yeoman is described [here](https://github.com/ncuillery/rn-diff/blob/master/USAGE.md). This PR is the integration of this process into the core. I got rid of the drawbacks mentioned in the link below in order to make it a clean, elegant, one-step operation. This process is based on some Shell operations that: - Generate the blank sources of both old and new versions Closes https://github.com/facebook/react-native/pull/11110 Differential Revision: D4237107 Pulled By: mkonicek fbshipit-source-id: 15e82e030b762415c925ccb2a62ddb354a6e18b9
2016-11-28 16:17:51 +00:00
{
"name": "react-native-git-upgrade",
Fix react-native-git-upgrade cache busting Summary: **Motivation** This PR fixes #12420. For the first time, the version 0.41.2 includes a change in the generator (see #12162). The [require cache busting](https://github.com/facebook/react-native/blob/master/react-native-git-upgrade/cliEntry.js#L157-L163) of `react-native-git-upgrade`, designed to face this situation , was ineffective. The entry in `require.cache` is the file path including the `.js` extension. We have to delete this entry with the same key. **Test plan** - Publish `react-native-git-upgrade` to Sinopia, - Follow the reproduction steps of #12420 - 👉 The name of the app shouldn't be changed Closes https://github.com/facebook/react-native/pull/12422 Differential Revision: D4585549 Pulled By: mkonicek fbshipit-source-id: 508ac925c17d02b7739d47f9351a5aa336589f2e
2017-02-19 00:41:30 +00:00
"version": "0.2.7",
New upgrading process, relying on Git Summary: The upgrading process based on Yeoman is a pain. For each file, Yeoman (or the brand new copyAndReplace solution a477aec) compares the newly generated content with the existing one and prompts the user if it differs, with very basic options: overwrite or skip. I have digged into this problem and came with [rn-diff](https://github.com/ncuillery/rn-diff) (you may have read [this article](https://medium.com/ncuillery/easier-react-native-upgrades-with-rn-diff-5020b5c3de2d#.llvy2dym5)). This repository helps people to upgrade RN on their projects. An alternative upgrading process using `git apply` instead of Yeoman is described [here](https://github.com/ncuillery/rn-diff/blob/master/USAGE.md). This PR is the integration of this process into the core. I got rid of the drawbacks mentioned in the link below in order to make it a clean, elegant, one-step operation. This process is based on some Shell operations that: - Generate the blank sources of both old and new versions Closes https://github.com/facebook/react-native/pull/11110 Differential Revision: D4237107 Pulled By: mkonicek fbshipit-source-id: 15e82e030b762415c925ccb2a62ddb354a6e18b9
2016-11-28 16:17:51 +00:00
"license": "BSD-3-Clause",
"description": "The React Native upgrade tool",
"main": "cli.js",
"bin": {
"react-native-git-upgrade": "index.js"
},
"engines": {
"node": ">=4"
},
"repository": {
"type": "git",
"url": "https://github.com/facebook/react-native.git"
},
"dependencies": {
"babel-core": "^6.18.0",
"babel-preset-es2015-node": "^6.1.1",
"babel-preset-stage-3": "^6.17.0",
"babel-register": "^6.18.0",
Fix react-native-git-upgrade by get package.json instead of selective field Summary: Explain the **motivation** for making this change. What existing problem does the pull request solve? To fixes #11330 and fixes #11334 Regarding to this command (using in `react-native-git-upgrade` - [cliEntry.js#L261](https://github.com/facebook/react-native/blob/master/react-native-git-upgrade/cliEntry.js#L261)) ```bash npm view react-native@latest peerDependencies.react version --json ``` The result from this command are not consistent across a different npm versions. We better get a whole `package.json` file by calling (remove field and subfield option) ``` npm view react-native@latest --json ``` **Test plan (required)** **Setup** - Publish `react-native-git-upgrade` to `sinopia` - `npm install -g react-native-git-upgrade` - Test against multiple npm versions (`2.15.8` or `3.7.5` or `3.10.10` or ` 4.0.3`) - `react-native init AwesomeApp --version 0.38.0 && cd AwesomeApp` - `react-native-git-upgrade` and `react-native-git-upgrade 0.39.0` should be working properly --- Closes https://github.com/facebook/react-native/pull/11348 Differential Revision: D4305894 Pulled By: mkonicek fbshipit-source-id: 36ea7846926b424f4dd63c77b47db5cb69285027
2016-12-09 15:55:18 +00:00
"minimist": "^1.2.0",
New upgrading process, relying on Git Summary: The upgrading process based on Yeoman is a pain. For each file, Yeoman (or the brand new copyAndReplace solution a477aec) compares the newly generated content with the existing one and prompts the user if it differs, with very basic options: overwrite or skip. I have digged into this problem and came with [rn-diff](https://github.com/ncuillery/rn-diff) (you may have read [this article](https://medium.com/ncuillery/easier-react-native-upgrades-with-rn-diff-5020b5c3de2d#.llvy2dym5)). This repository helps people to upgrade RN on their projects. An alternative upgrading process using `git apply` instead of Yeoman is described [here](https://github.com/ncuillery/rn-diff/blob/master/USAGE.md). This PR is the integration of this process into the core. I got rid of the drawbacks mentioned in the link below in order to make it a clean, elegant, one-step operation. This process is based on some Shell operations that: - Generate the blank sources of both old and new versions Closes https://github.com/facebook/react-native/pull/11110 Differential Revision: D4237107 Pulled By: mkonicek fbshipit-source-id: 15e82e030b762415c925ccb2a62ddb354a6e18b9
2016-11-28 16:17:51 +00:00
"npmlog": "^4.0.0",
"promise": "^7.1.1",
"rimraf": "^2.5.4",
"semver": "^5.0.3",
"shelljs": "^0.7.5",
"yeoman-environment": "1.5.3"
}
}