In this post, we will discuss some options to solve this problem.īefore we discuss the options, let me give you a suggestion.
EXPO VECTOR ICONS INSTALL
In this article, we will go over the steps to install and use the package in your Expo app, with code examples. When you install one of these libraries in a react-native-web project, esbuild will ask you to install rnvi and will bundle the large GlyphMap for the MaterialCommunityIcons, even if you haven't used any icons in your project. E xpo Vector Icons is a popular package for adding customizable icons to your React Native projects. You can opt-out rnvi using babel-plugin-optional-require, but, as you can infer, it doesn't work with esbuild. It can get even worse, because popular libraries as react-native-paper and depend on rnvi for the MaterialCommunityIcons font.
EXPO VECTOR ICONS DOWNLOAD
And the MaterialCommunityIcons.ttf, which is more than 900 kb, will be download into your app. Some GlyphMaps, such as Ionicons and MaterialCommunityIcons, are over 100 kb, and minimization has almost no effect. Even if you use only one icon in your project, the entire GhyphMap and the entire ttf will be imported by esbuild during the bundling. Each ttf font has a corresponding GlyphMap, which is a json file that associates the icon's name with its Unicode value. When used with react-native-web, rnvi significantly increases the bundle size. node_modules/regenerator-runtime/runtime.The react-native-vector-icons ( rnvi) is a popular library in the react-native world, which is compatible with react-native-web.īut there is a problem. node_modules/regenerator-runtime/runtime.js:293:29 in invoke node_modules/regenerator-runtime/runtime.js:63:36 in tr圜atch node_modules/expo-error-recovery/build/ErrorRecovery.fx.js:9:32 in tGlobalHandler$argument_0 node_modules/react-native/Libraries/Core/setUpErrorHandling.js:24:6 in handleError node_modules/react-native/Libraries/Core/ExceptionsManager.js:171:19 in handleException node_modules/react-native/Libraries/Core/ExceptionsManager.js:104:6 in reportException
node_modules/react-native/Libraries/LogBox/LogBox.js:148:8 in registerError
Invariant Violation: Native module cannot be null. * :null in callFunctionReturnFlushedQueue node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:108:4 in callFunctionReturnFlushedQueue node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:364:10 in _guard node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:109:6 in _guard$argument_0 node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:416:4 in _callFunction node_modules/react-native/Libraries/ReactNative/AppRegistry.js:200:6 in runApplication node_modules/expo/build/environment/react-native-logs.fx.js:18:4 in warn node_modules/react-native/Libraries/LogBox/LogBox.js:36:4 in console.warn node_modules/react-native/Libraries/LogBox/LogBox.js:63:8 in warnImpl node_modules/react-native/Libraries/LogBox/LogBox.js:117:10 in registerWarning node_modules/react-native/index.js:319:12 in _DatePickerAndroid It can now be installed and imported from instead of 'react-native'. Warning: DatePickerAndroid has been merged with DatePickerIOS and will be removed in a future release. node_modules/metro/src/lib/polyfills/require.js:201:44 in guardedLoadModule
node_modules/metro/src/lib/polyfills/require.js:321:11 in loadModuleImplementation node_modules/react-native/index.js:134:12 in _DatePickerIOS node_modules/react-native/Libraries/Utilities/warnOnce.js:29:9 in warnOnce node_modules/fbjs/lib/warning.js:51:4 in node_modules/fbjs/lib/warning.js:30:4 in printWarning node_modules/expo/build/environment/react-native-logs.fx.js:27:4 in error node_modules/react-native/Libraries/LogBox/LogBox.js:33:4 in console.error node_modules/react-native/Libraries/LogBox/LogBox.js:59:8 in errorImpl node_modules/react-native/Libraries/LogBox/LogBox.js:173:8 in registerError Warning: DatePickerIOS has been merged with DatePickerAndroid and will be removed in a future release.
0 kommentar(er)
