neetoIcons

The neetoIcons and neetoIconsRN library are a collection of SVG React component icons that drives the experience in the neeto products built at BigBinary.

Contents

• Installation
• Usage
• How it works
• Instructions for publishing

Installation

Web:

yarn add @bigbinary/neeto-icons

React Native:

yarn add @bigbinary/neeto-icons-rn

Instructions for development

Check the Frontend package development guide for step-by-step instructions to develop the frontend package.

Adding a new icon to the library

1. Add the SVG file - Place the SVG file for the new icon in the appropriate folder under the source directory. For example:

   • icons/ for normal icons
   • logos/ for product logos
   • typefaceLogos/ for product typeface logos
   • appIcons/ for app icons
   • misc/ for miscellaneous icons
   • elements/ for elements

2. Name the file appropriately - Use PascalCase for the file name (e.g., NewIcon.svg).

3. Verify the icon - Run the yarn start command to verify the React component for the new icon:

Usage

Web:

import { Clock } from "@bigbinary/neeto-icons";

React Native:

import { Clock } from "@bigbinary/neeto-icons-rn";

Anywhere in your React file

<Clock color="#1e1e20" size={24} />

React Native imports

Every category is available as a barrel:

import { NeetoSite } from "@bigbinary/neeto-icons-rn/app-icons";
import { Keyboard } from "@bigbinary/neeto-icons-rn/elements";
import { Clock } from "@bigbinary/neeto-icons-rn/icons";
import { Neeto } from "@bigbinary/neeto-icons-rn/logos";
import { Windows } from "@bigbinary/neeto-icons-rn/misc";
import { Neeto as NeetoTypeface } from "@bigbinary/neeto-icons-rn/typeface-logos";

Each icon can also be imported on its own, as a default export, so that the bundler only pulls in what is used:

import Clock from "@bigbinary/neeto-icons-rn/icons/Clock";
import Neeto from "@bigbinary/neeto-icons-rn/logos/Neeto";

Every category is also reachable through a single namespaced entry point:

import { Icons, Logos, Misc } from "@bigbinary/neeto-icons-rn/namespaces";

<Icons.Clock size={24} />;

The props type is exported separately:

import type { IconProps } from "@bigbinary/neeto-icons-rn/types";

Metro configuration

These subpaths are declared through the exports field of the package, which Metro honours by default only from React Native 0.79 onward. On earlier versions the field is ignored and the imports above fail to resolve, so enable it in metro.config.js:

module.exports = {
  resolver: {
    unstable_enablePackageExports: true,
  },
};

Product logos

import { Neeto } from "@bigbinary/neeto-icons/logos";

App icons

import { NeetoSite } from "@bigbinary/neeto-icons/app-icons";

Props

Misc icons

import { Windows } from "@bigbinary/neeto-icons/misc";
<Windows  size={36} />

import { Razorpay } from "@bigbinary/neeto-icons/misc";
<Razorpay  width={100}  height={32} />
<Razorpay  width={100}  />

Props

Typeface logos

import { Neeto } from "@bigbinary/neeto-icons/typeface-logos";

Anywhere in your React file

<Neeto height={24} width={48} />

Elements

import { Keyboard } from "@bigbinary/neeto-icons/elements";

Anywhere in your React file

<Keyboard height={80} width={41} />

How it works

• We use a custom rollup plugin (which can be found in build/index.mjs) to take all the .svg files from the source folder and convert them to React components that render the respective SVG icon.

• The plugin accepts a configuration object as an argument which can contain the following keys:

  Name	Type	Description
  options	object	Options passed to the transform function from react-svgr. (See full opions list)
  additionTransformations	function	Additional string transformation that can be applied to the generated React code.
  source	string	Path to the folder where the SVG files are located
  destination	string	Path to the folder to place the generated react code

• For each icon, a React icon file will be generated in generate/icons folder.

• From there babel through rollup takes the wheel and generates the bundles.

Instructions for Publishing

Consult the building and releasing packages guide for details on how to publish.