0.2.0

@tcbs/react-native-mazic-ui 0.2.0

This release modernizes icon support, improves package metadata for better ecosystem compatibility, and clarifies dependency ownership for consumers.

Highlights

• Migrated icon usage from legacy react-native-vector-icons imports to the new scoped per-family packages under @react-native-vector-icons.
• Added package exports map for clearer and safer module entry points.
• Added sideEffects: false to improve bundler tree-shaking.
• Added engines requirement (Node >= 18).
• Added bugs metadata for better issue routing.
• General package metadata cleanup for publish quality.

Breaking/Important Changes

• Dependency model updated: icon libraries are now peer dependencies instead of bundled runtime dependencies.
• Consumers must install the icon family packages used by the library.
• Legacy react-native-vector-icons package is no longer the expected integration path for this library.

Migration Guide

If you are upgrading from 0.1.x:

1. Remove legacy icon package usage in your app if still present.
2. Install required scoped icon packages:

• @react-native-vector-icons/ant-design
• @react-native-vector-icons/feather
• @react-native-vector-icons/fontawesome
• @react-native-vector-icons/foundation
• @react-native-vector-icons/ionicons
• @react-native-vector-icons/material-design-icons
• @react-native-vector-icons/material-icons
• @react-native-vector-icons/octicons

3. Keep react-native-mmkv and zustand installed (peer dependency requirements).
4. Reinstall pods and rebuild native apps.

Internal/Packaging Changes

• Updated source imports to scoped static icon entrypoints.
• Updated publish-facing package metadata for better interoperability with modern Node and bundlers.
• Aligned dependency boundaries with library best practices for React Native package authors.

Notes

• This is a modernization and compatibility-focused release.
• If your app previously relied on transitive icon dependencies from this package, you now need explicit app-level installs.

---