-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.57.0-rc.0] react-native-git-upgrade and old school upgrade are broken #20710
Comments
confirm. could upgrade by
|
Have you tried manually upgrading to 0.57? EDIT: for clarity sake until we release the changelog, to manually upgrade you should need to do these things:
|
@kelset I don't think you need to set dependency on the preset anyway, because it's part of Metro dependencies and ends up being in your node modules anyway. Remember that its version has to always match internal Metro version, which may be hard to keep in sync due to lack of peer dependency on RN. |
I guess that I've to lock this issue too, apparently it's impossible to avoid disruptive people when trying to fix issues related to release candidates 🤷♂️ I'll keep saying it, it's an open source project. Don't you like something? Fork it and fix it yourself. Writing these kinds of comments is just pathetic. EDIT: Apparently, the user who posted the disruptive comment deleted it. And yes, I have a screenshot of the comment. EDIT2: Unlocking, hoping that the conversation will now move towards helpful interactions. And, again, PRs are the first way to move forward this issue. |
Tried upgrading the old fashioned way. I first ran
Then I ran
Metro still? PS. output: #20720 (comment) from |
I also face this problem |
@fungilation can you copy/paste your |
My package.json{
"name": "wonderswipe",
"version": "0.0.1",
"private": true,
"eslintConfig": {
"parserOptions": {
"ecmaVersion": 7,
"sourceType": "module",
"ecmaFeatures": {
"jsx": true
}
},
"env": {
"browser": true,
"node": true
},
"plugins": [
"react",
"react-native"
],
"rules": {
"comma-dangle": [
2,
"always-multiline"
],
"semi": [
2,
"never"
],
"react-native/no-unused-styles": 2,
"react-native/split-platform-components": 2
}
},
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start"
},
"dependencies": {
"babel-plugin-idx": "^2",
"he": "^1.1.0",
"lodash": "^4.17.2",
"moment": "^2.19.0",
"moment-timezone": "^0.5.10",
"node-summary": "../node-summary",
"react": "16.4.1",
"react-native": "0.57.0-rc.0",
"react-native-actionsheet": "^2.4.2",
"react-native-blur": "^3.2.0",
"react-native-cached-image": "../react-native-cached-image",
"react-native-code-push": "^5.3",
"react-native-custom-tabs": "^0.1.7",
"react-native-easy-toast": "^1.0.9",
"react-native-firebase": "^3.0",
"react-native-fit-image": "^1.4.8",
"react-native-flanimatedimage": "^0.4.0",
"react-native-highlight-words": "^1.0.1",
"react-native-keep-awake": "^3.0.1",
"react-native-linear-gradient": "^2.0.0",
"react-native-modalbox": "^1.6.0",
"react-native-orientation": "^3.1.3",
"react-native-parallax-scroll-view": "../react-native-parallax-scroll-view",
"react-native-rate": "^1.0.8",
"react-native-safari-view": "^2.0.0",
"react-native-sentry": "^0.38.0",
"react-native-sha256": "^1.1.1",
"react-native-status-bar-size": "^0.3.2",
"react-native-swiper": "../react-native-swiper",
"react-native-tooltip": "^5.2.0",
"react-native-tts": "^1.5.0",
"react-native-vector-icons": "^4.1.1",
"react-native-webview-bridge": "../react-native-webview-bridge-RN0.51",
"react-redux": "^5.0.1",
"redux": "^4.0.0",
"redux-thunk": "^2.1.0"
},
"devDependencies": {
"redux-logger": "^3.0.6"
}
} |
Uhm so you don't have the "explicit" dependency to metro nor babel? What happens if you add
To ensure that you are locking at the right versions? |
Made those changes and ran But running |
I've done some investigation and the original reported issue is caused by react-native/react-native-git-upgrade/cli.js Lines 12 to 19 in 9c1ea45
Babel by default tries to find The easiest patch to fix this issue is to add @fungilation can you give this a try? feel free to send a PR if this fixes the issue 😃 |
On running `react-native-git-upgrade` with `babelrc: false`
Suspicious warnings:
and
Tried nuking /node_modules/ before running So the line change in
|
FWIW, @rafeca's fix worked for me. Patched and ran Environment
|
Good to hear, @ngraef would you mind creating a PR with the fix so that it can be merged and cherry-picked for a rc1 release, so that it can be available? |
I tried upgrading to react 57 rc by first Change its cli.js to
yarn react-native-git-upgrade 0.57.0-rc.0 It does seem to upgrade the node modules to 0.57.0 but the package.json is not updated. |
@ngraef did you have to do some additional babel configuration?
Which also "solves" that problem for me. However I get error from |
Per [this comment on the issue](facebook#20710 (comment)): > Babel by default tries to find .babelrc files to configure itself, and once it finds the one from the RN app (which links to the RN preset that only works on Babel 7) it fails. > The easiest patch to fix this issue is to add babelrc: false to the babel-register method, so Babel does not read any additional .babelrc file. Fixes facebook#20710
Summary: Per [this comment on the issue](#20710 (comment)): > Babel by default tries to find .babelrc files to configure itself, and once it finds the one from the RN app (which links to the RN preset that only works on Babel 7) it fails. > The easiest patch to fix this issue is to add babelrc: false to the babel-register method, so Babel does not read any additional .babelrc file. Fixes #20710 Pull Request resolved: #20790 Differential Revision: D9458502 Pulled By: hramos fbshipit-source-id: 3a0ed7261322fdd9e0c0840f8a3944974f38b233
Summary: Per [this comment on the issue](facebook#20710 (comment)): > Babel by default tries to find .babelrc files to configure itself, and once it finds the one from the RN app (which links to the RN preset that only works on Babel 7) it fails. > The easiest patch to fix this issue is to add babelrc: false to the babel-register method, so Babel does not read any additional .babelrc file. Fixes facebook#20710 Pull Request resolved: facebook#20790 Differential Revision: D9458502 Pulled By: hramos fbshipit-source-id: 3a0ed7261322fdd9e0c0840f8a3944974f38b233
Summary: Per [this comment on the issue](facebook#20710 (comment)): > Babel by default tries to find .babelrc files to configure itself, and once it finds the one from the RN app (which links to the RN preset that only works on Babel 7) it fails. > The easiest patch to fix this issue is to add babelrc: false to the babel-register method, so Babel does not read any additional .babelrc file. Fixes facebook#20710 Pull Request resolved: facebook#20790 Differential Revision: D9458502 Pulled By: hramos fbshipit-source-id: 3a0ed7261322fdd9e0c0840f8a3944974f38b233
Summary: Per [this comment on the issue](facebook#20710 (comment)): > Babel by default tries to find .babelrc files to configure itself, and once it finds the one from the RN app (which links to the RN preset that only works on Babel 7) it fails. > The easiest patch to fix this issue is to add babelrc: false to the babel-register method, so Babel does not read any additional .babelrc file. Fixes facebook#20710 Pull Request resolved: facebook#20790 Differential Revision: D9458502 Pulled By: hramos fbshipit-source-id: 3a0ed7261322fdd9e0c0840f8a3944974f38b233
Environment
I'm upgrading from React Native 0.56.0.
Description
Reproducible Demo
Run
react-native-git-upgrade 0.57.0-rc.0
. I can reproduce same error on both Windows and MacOS (latest High Sierra).I've never encountered a similar breakage with
git-upgrade
for about the last 10 version of RN upgrades I've done withreact-native-git-upgrade
.Ref: react-native-community/releases#34
The text was updated successfully, but these errors were encountered: