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
iconoir -> @iconoir/core (not sure if we should switch this as well or leave it)
The main reason for my suggestion is that this way it would be clearly visible that the packages are official "iconoir" packages and there would be no risk of conflicts with "community" packages (for example, iconoir-vue).
I like the proposal. It looks cleaner and more scalable.
But can this change be applied without disrupting the experience of those who are already using the packages?
We agreed on Discord (for now at least) that we will leave the existing package names as they are, but will use scoped packages for any new libraries (like we did with the VueJS library).
As a big overhaul is coming anyway (#185) I'd like to discuss how you, @lucaburgio & @sammarks, feel about switching to scoped NPM packages.
For example:
iconoir-react
->@iconoir/react
iconoir-react-native
->@iconoir/react-native
iconoir
->@iconoir/core
(not sure if we should switch this as well or leave it)The main reason for my suggestion is that this way it would be clearly visible that the packages are official "iconoir" packages and there would be no risk of conflicts with "community" packages (for example, iconoir-vue).
Ref #56.
The text was updated successfully, but these errors were encountered: