fix(lucide-react-native): remove icons namespace export to enable tree-shaking

[jtomaszewski]

Summary

Remove the export * as icons from './icons' namespace export from lucide-react-native entry files to enable proper tree-shaking.

Related: #1559 , #3744

Problem

The namespace re-export defeats tree-shaking because bundlers cannot statically analyze which exports from the namespace are actually used. This causes all 1600+ icons to be included in the final bundle even when only a few are imported.

For example, in a React Native/Expo app using Metro bundler:

• Before: Bundle size ~10.5MB (all icons included)
• After: Bundle size ~8.3MB (only used icons included)

Solution

Remove the icons namespace export while keeping individual icon exports available via export * from './icons'.

Breaking Change

The icons namespace export is no longer available. Users should import icons directly:

// Before (no longer works)
import { icons } from 'lucide-react-native';
const Icon = icons.Activity;

// After (recommended)
import { Activity } from 'lucide-react-native';

This is perhaps a minor breaking change as the namespace import pattern was rarely used and defeats the purpose of tree-shaking.

Testing

Tested in a production Expo app with Metro bundler - bundle size reduced by ~20% after this change.

[ericfennis]

Good findings, but I'm not entirely comfortable removing this feature, since it is a breaking change.

I've added the exports property to the package.json to add a path to import the icons entry into projects.
This keeps this feature, but with a different import.
Also updated the docs with the new import.

import * as icons from 'lucide-react-native/icons';

interface IconProps {
  name: keyof typeof icons;
  color?: string;
  size?: number;
}

const Icon = ({ name, color, size }: IconProps) => {
  const LucideIcon = icons[name];

  return <LucideIcon color={color} size={size} />;
};

export default Icon;