The configuration for this has a habit of changing between RN versions. See below for version-specific instructions on creating a config file, loading the config file and clearing the cache. For React Native >= 0.64(?) This is speculative as 0.64 is not yet released, but a rename from blacklist to exclusionList made in metro 0.60 … Read more
There are two ways you can do this. Firstly import AsyncStorage correctly. This will remove the warning and fix the problem. Secondly, suppress the warning. This will just hide the warning but will cause you issues once AsyncStorage has been removed from react-native. I would not do this as the first way actually solves the … Read more
We can use the built-in nestedscrollenabled prop for the children FlatList/ScrollView components. <FlatList nestedScrollEnabled /> This is only required for Android (Nested scrolling is supported by default on iOS).
export {default as Module} from ‘./Module/Module’; is the standard ES6 way, as long as you don’t need Module to also be available inside the module doing the exporting. export Module from ‘./Module/Module’; is a proposed ESnext way to do it, but that only works if you’ve enabled it in Babel for now.
Using a RegExp to replace any non digit is faster than using a for loop with a whitelist, like other answers do. Use this for your onTextChange handler: onChanged (text) { this.setState({ mobile: text.replace(/[^0-9]/g, ”), }); } Performance test here: https://jsperf.com/removing-non-digit-characters-from-a-string
You can use the __DEV__ global variable in JavaScript to determine if you’re using React Native packager or not. If you are running your app in the iOS Simulator or Android emulator __DEV__ will be set to true. https://reactnative.dev/docs/javascript-environment
You should move all the code from the componentWillMount to the constructor or componentDidMount. componentWillMount() is invoked just before mounting occurs. It is called before render(), therefore calling setState() synchronously in this method will not trigger an extra rendering. Generally, we recommend using the constructor() instead. Avoid introducing any side-effects or subscriptions in this method. … Read more
It seems like a bug in 0.56 related to dependencies. The “solution” is to find the correct combination of dependencies’ versions. We found a workaround by installing those versions EXACTLY: react-native >> 0.55.4 babel-core >> latest babel-loader >> latest babel-preset-react-native >> 4.0.0 So you have to run those commands in order: react-native init AwesomeProject cd … Read more
In React Navigation 5, this becomes much easier by passing in the screen as the second parameter: navigation.navigate(‘Nested Navigator 2’, { screen: ‘screen D’ }); You can also include additional levels if you have deeply nested screens: navigation.navigate(‘Nested Navigator 2’, { screen: ‘Nested Navigator 3’, params: { screen: ‘screen E’ } });
Linux uses the inotify package to observe filesystem events, individual files or directories. Since React / Angular hot-reloads and recompiles files on save it needs to keep track of all project’s files. Increasing the inotify watch limit should hide the warning messages. You could try editing # insert the new value into the system config … Read more