You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please Describe.
This library currently relies upon react-native-vector-icons@v10 as a dependency. This is quite an old version of the library and it's since changed it's structure entirely and is now installed as @react-native-vector-icons/[fontName].
Describe the solution you'd like
I think this library should completely drop its dependency on an external icon package, remove the Icon component. All props on components that received icon configuration (like Avatar) should simply receive a react element and render it accordingly.
Describe alternatives you've considered
The other alternative is to upgrade this library to support the most modern version of @react-native-vector-icons. However, this will the increase overall maintenance burden as it will require this library to have parity with react-native-vector-icons into the future.
Additional context
I'd be happy to work on a PR for this change if this direction is approved.
Reacted by Yann Zahringer Ferrando, Kash and Donato Aguirre
Thanks for the suggestion and for taking the time to look into ways we can reduce unnecessary dependencies.
The Icon and Avatar components are core parts of our library. They're used extensively both internally and by many of our consumers, so removing them completely would be a major breaking change. That’s not something I’m looking to do at this point.
That said, I’m definitely open to exploring a switch to the newer modular icon packages you mentioned. Before we make any moves, though, we’ll need to consider a few things carefully:
How many breaking changes this would introduce
The level of effort required from users to migrate
Whether we can provide a smooth transition or fallback option for existing users
Whether the effort involved is justified by the overall benefit especially since react-native-vector-icons is still actively maintained
Right now, my focus is on fixing the issue from the parent branch and making the transition as smooth as possible for users. The current major version will continue to be supported with the existing library, so teams with larger codebases won’t face any immediate breaking changes. Meanwhile, the new major version can offer a cleaner setup for new users moving forward.
I’ll spend some time over the weekend reviewing the icon packages and seeing how they might fit into our path forward.
we are in talk with original maintainer and contributors of react native elements and there are chances this repo to be merged in original library. We need to take review from other maintainer about this. So we all hold this plan for some time.
Hi @deepktp, I'm working on an app using react-native-element AND react-native-vector-icons...
And I've bumped to the new v12 architecture : "react-native-vector-icons/{font-name}".
But react-native-element still relies to react-native-vector-icon ...
Even with this kind of patch I wasn't able to have the font working. ( I can build but the 'close' icon isn't rendered )
I got this "error icon" :
Is it even possible to make rne@3.x to work with rnvi@12.x only ?
Does the "talk with original maintainer and contributors" leaded to something interesting ?
Hii, @seba9999 we haven't reached a specific point to confirm wether original maintainer are willing to upgrade vector icons.
I will look into this, if patch work for me. I will update you with findings as soon as possible.
I am getting a warning in react-native 0.78 its seems to be related to the legacy version of react-native-vector-icons.
our app (or one of its dependencies) is using an outdated JSX transform.
Update to the modern JSX transform for faster performance: https://react.dev/link/new-jsx-transform Error
Component Stack:
at Icon (create-icon-set.js:1:3419)
at RCTView (<anonymous>)
I migrated to this package because it solved many of the issues and conflicts of the old unmaintained package.
Its makes sense that this becomes a stand alone package, not relying on the old one, to be faster and better at handling such cases.
I am getting a warning in react-native 0.78 its seems to be related to the legacy version of react-native-vector-icons.
our app (or one of its dependencies) is using an outdated JSX transform.
Update to the modern JSX transform for faster performance: https://react.dev/link/new-jsx-transform Error
Component Stack:
at Icon (create-icon-set.js:1:3419)
at RCTView (<anonymous>)
I migrated to this package because it solved many of the issues and conflicts of the old unmaintained package. Its makes sense that this becomes a stand alone package, not relying on the old one, to be faster and better at handling such cases.
@kashmiry
I’m currently using version react native 0.81.4 with this library and haven’t run into this issue. Would you mind sharing your package.json and tsconfig.json files? That might help in reproducing the problem and narrowing down the cause.
I am getting a warning in react-native 0.78 its seems to be related to the legacy version of react-native-vector-icons.
our app (or one of its dependencies) is using an outdated JSX transform.
Update to the modern JSX transform for faster performance: https://react.dev/link/new-jsx-transform Error
Component Stack:
at Icon (create-icon-set.js:1:3419)
at RCTView (<anonymous>)
I migrated to this package because it solved many of the issues and conflicts of the old unmaintained package. Its makes sense that this becomes a stand alone package, not relying on the old one, to be faster and better at handling such cases.
@kashmiry I’m currently using version react native 0.81.4 with this library and haven’t run into this issue. Would you mind sharing your package.json and tsconfig.json files? That might help in reproducing the problem and narrowing down the cause.
Thank you for all the work on this.
I noticed docs needs to be update on installation page for the icons instructions.
I tried version 6.0.0-rc.0 but I am getting errors for getIconType
Error: Requiring unknown module "undefined". If you are sure the module exists, try restarting Metro. You may also want to run `yarn` or `npm install`., js engine: hermes Error Component Stack:
at Icon (Icon.js:9:95)
at Themed.Icon (withTheme.js:18:44)
at RCTView (<anonymous>)
at View (View.js:32:34)
at Animated(View) (createAnimatedComponent.js:65:57)
at TouchableOpacity (TouchableOpacity.js:132:23)
at TouchableOpacity (<anonymous>)
for:
ionicon: () => {
try {
return require('@react-native-vector-icons/ionicons').default;
} catch {
// Check if old library exists
try {
const oldLib = require('react-native-vector-icons/Ionicons').default;
console.warn(
'Warning: "react-native-vector-icons" has been deprecated. Please install the modular library "@react-native-vector-icons/ionicons" instead.'
);
return oldLib;
} catch {
console.warn(
'Ionicons icon set is not available. Please install "@react-native-vector-icons/ionicons" to use it.'
);
return null;
}
}
},
Even though I have installed @react-native-vector-icons/ionicons and removed legacy react-native-vector-icons.
also tried to clear yarn cache + restart Metro. still getting Error: Requiring unknown module "undefined". for fonts requires.
A migration guide for this would be helpful.
Could you please share the code snippet you’re using? We’re currently unable to reproduce this issue on our end, and having that context would help us investigate further.
Regarding the installation documentation, we’re in the process of finalizing the v6 release and will be updating the relevant docs.
@deepktp
Working correctly now! I was able to migrate with no issues.
not sure what was the issue before. what changed is that I am on RN v0.81. Also maybe I followed steps more correctly now.
Activity
deepktp commentedon Jul 3, 2025
@jspizziri
Thanks for the suggestion and for taking the time to look into ways we can reduce unnecessary dependencies.
The
IconandAvatarcomponents are core parts of our library. They're used extensively both internally and by many of our consumers, so removing them completely would be a major breaking change. That’s not something I’m looking to do at this point.That said, I’m definitely open to exploring a switch to the newer modular icon packages you mentioned. Before we make any moves, though, we’ll need to consider a few things carefully:
How many breaking changes this would introduce
The level of effort required from users to migrate
Whether we can provide a smooth transition or fallback option for existing users
Whether the effort involved is justified by the overall benefit especially since
react-native-vector-iconsis still actively maintainedRight now, my focus is on fixing the issue from the parent branch and making the transition as smooth as possible for users. The current major version will continue to be supported with the existing library, so teams with larger codebases won’t face any immediate breaking changes. Meanwhile, the new major version can offer a cleaner setup for new users moving forward.
I’ll spend some time over the weekend reviewing the icon packages and seeing how they might fit into our path forward.
deepktp commentedon Jul 11, 2025
hii, @jspizziri sorry for late reply,
we are in talk with original maintainer and contributors of react native elements and there are chances this repo to be merged in original library. We need to take review from other maintainer about this. So we all hold this plan for some time.
seba9999 commentedon Aug 12, 2025
Hi @deepktp, I'm working on an app using react-native-element AND react-native-vector-icons...
And I've bumped to the new v12 architecture : "react-native-vector-icons/{font-name}".
But react-native-element still relies to react-native-vector-icon ...
Even with this kind of patch I wasn't able to have the font working. ( I can build but the 'close' icon isn't rendered )
I got this "error icon" :
Is it even possible to make rne@3.x to work with rnvi@12.x only ?
Does the "talk with original maintainer and contributors" leaded to something interesting ?
deepktp commentedon Aug 12, 2025
Hii, @seba9999 we haven't reached a specific point to confirm wether original maintainer are willing to upgrade vector icons.
I will look into this, if patch work for me. I will update you with findings as soon as possible.
kashmiry commentedon Sep 23, 2025
I am getting a warning in react-native 0.78 its seems to be related to the legacy version of react-native-vector-icons.
I migrated to this package because it solved many of the issues and conflicts of the old unmaintained package.
Its makes sense that this becomes a stand alone package, not relying on the old one, to be faster and better at handling such cases.
deepktp commentedon Sep 23, 2025
@kashmiry
I’m currently using version react native 0.81.4 with this library and haven’t run into this issue. Would you mind sharing your package.json and tsconfig.json files? That might help in reproducing the problem and narrowing down the cause.
Vector icon issue it looks like we need to upgrade to rnvi to v12.
github-actions commentedon Sep 23, 2025
kashmiry commentedon Sep 23, 2025
I can identify where exactly it happens.
it happens if you use this component: createIconSetFromIcoMoon
main dependencies:
tsconfig:
feat: added modular vector icons #50
feat: added modular vector icons #50
Upgrade library from react-native-vector-icons to modular icons packa…
Upgrade library from react-native-vector-icons to modular icons packa…
Upgrade library from react-native-vector-icons to modular icons packa…
deepktp commentedon Oct 23, 2025
We have updated the library with Modular Vector Icons
Bleeding Edge Version With RN Vector Icons V12
Docs
feat: added modular vector icons #50
feat: added modular vector icons #50
Icon lib upgrade (#66)
deepktp commentedon Nov 24, 2025
Now library supports latest vector icons v12+ also the older library with deprecation warning.
v6.0.0-rc.0
kashmiry commentedon Feb 9, 2026
Thank you for all the work on this.
I noticed docs needs to be update on installation page for the icons instructions.
I tried version
6.0.0-rc.0but I am getting errors forgetIconTypefor:
Even though I have installed
@react-native-vector-icons/ioniconsand removed legacyreact-native-vector-icons.also tried to clear yarn cache + restart Metro. still getting
Error: Requiring unknown module "undefined".for fonts requires.A migration guide for this would be helpful.
deepktp commentedon Feb 12, 2026
Hi @kashmiry ,
Could you please share the code snippet you’re using? We’re currently unable to reproduce this issue on our end, and having that context would help us investigate further.
Regarding the installation documentation, we’re in the process of finalizing the v6 release and will be updating the relevant docs.
Thanks
kashmiry commentedon Aug 26, 2026
@deepktp
Working correctly now! I was able to migrate with no issues.
not sure what was the issue before. what changed is that I am on RN
v0.81. Also maybe I followed steps more correctly now.Tested on:
Working on both ios & android.
Thank you!