This shows up when running the Metro Bundler from React Native v0.60.0:
warn The following packages use deprecated "rnpm" config that will stop working from next release:
- native-base: https://github.com/GeekyAnts/NativeBase#readme
See https://github.com/react-native-community/cli/blob/master/docs/configuration.md#migration-guide
I see that rnpm is mentioned twice in package.json but I suspect it's not really being used.
Any update on this? I found the same thing after doing npm install and updating to some latest dependencies.
I am over a react native project and have met with similar issue.
**> warn The following packages use deprecated "rnpm" config that will stop working from next release:
- native-base: https://github.com/GeekyAnts/NativeBase#readme
- react-native-google-signin: https://github.com/react-native-community/react-native-google-signin
- react-native-maps: https://github.com/airbnb/react-native-maps#readme
- react-native-video: https://github.com/react-native-community/react-native-video#readme
**
@jim20june1989 yes, basically you have to check each dependency repo and see if they released a version where they don't use nrpm anymore. It sucks, i know.
I'm waiting on NativeBase to see if they will be releasing a hotfix soon.
@msqar thanks.
Well then let's hope they sort this out as it's just ridiculous how things have turned after latest release by firebase and google play services. My project feels like mess now.
Here's a PR fixing the issue
https://github.com/GeekyAnts/NativeBase/pull/2749
We'll probably need to test it, anybody volunteering?
@RohanTalip @jim20june1989 @msqar
I made the same changes as PR #2749 in my node_modules/native-base/ directory.
I restarted the Metro Bundler process and no longer got the warning about the rnpm config in native-base. I was also able to start my Vue Native app using Native Base sucessfully from Xcode.
So, it works for me 馃槃!
Agree, it works. Can we merge this PR so i can update native-base ? Thanks :)
Has been merged, the next release won't be out till the end of the coming week.
Till then, please point your package.json to the master branch.
@sanketsahusoft ah nvm :D i can wait 1 week. Not in a rush. Thanks again.
the next release with the fix is already ?
Any updates on when this will be released?
creating a "react-native.config.js" at the root of the project
package.json entry:
{
"rnpm": {
"ios": {},
"android": {},
"assets": ["./path-to-assets"],
"plugin": "./path-to-commands.js"
}
}
becomes react-native.config.js
module.exports = {
project: {
ios: {},
android: {}, // grouped into "project"
},
assets: ['./path-to-assets'], // stays the same
commands: require('./path-to-commands.js'), // formerly "plugin", returns an array of commands
};
@asdword
Fixed in 2.13.0
I have the same issues in react-native 0.60.04.
But I can't find rnpm key in package.json.
@sankhadeeproy007 absolutely true! it's finally fixed. Thanks everyone for your job! :)
Hi I麓m just a few months into react-native, trying to implement custom fonts into my app. It worked perfectly with rnpm but as I shouldn麓t use it any more I麓m not figuring out how to use cf.
Can anyone here please write down the few steps? I麓m sure I麓m just missing a small part.. Thanks!
Most helpful comment
Fixed in 2.13.0