
Please I'm putting this issue up here so that it can be corrected and better user experience
@jerryheir can you specify the native-base version you are using. Checked with version 2.4.3. Couldn't see this issue.
I was using 2.4.3 and i was running into the same thing. it is probably related to windows machines viewing a change of Utils to utils... not sure of the best way for it to be resolved on the module side of things in this case. But renaming node_modules/native-base/src/Utils to .../utils and node_modules/native-base/dist/src/Utils to .../utils worked for me as well.
Experiencing the same problem with 2.4.3 on a Mac as well, non-case-sensitive APFS volume.
Same for me.
@jerryheir @kstolte @arvidkahl @d4n1b
after installing node_modues, clear cache before run
npm start -- --reset-cache
@kstolte I run into the same issue and cleaning the cache did help me. I just install native-base again and it worked :)
@franzejr Good to know that you got it working
Closing this issue
just cleaning up cache didn't work for me.
I deleted node_modules folder, yarn.lock file and then ran
yarn cache clean
then installed packages again using yarn
My friend, is the moment for make a 鈽曪笍.
rm -fr node_modules
yarn install
react-native run-android
and continue programming... the life is short...
My friend, is the moment for make a 鈽曪笍.
rm -fr node_modules yarn install react-native run-androidand continue programming... the life is short...
working with me
Most helpful comment
I was using 2.4.3 and i was running into the same thing. it is probably related to windows machines viewing a change of
Utilstoutils... not sure of the best way for it to be resolved on the module side of things in this case. But renamingnode_modules/native-base/src/Utilsto.../utilsandnode_modules/native-base/dist/src/Utilsto.../utilsworked for me as well.