Currently, the react-oui-icons build process includes a copy of development react, production react, and prop-types within the code that is built for the NPM module. This is not ideal as the application using react-oui-icons should be responsible for including the appropriate versions of these libraries.

1. Convert PM icon strokes to outlines
2. Figure out why when I update the svg inside /assets/svgs it doesn't update the yarn storybook icon.

Add some stroke width knob to storybook.

Hey @jamesopti, I know it's been a while since we last looked at this together but I am confused when working in this repo with these two issues:

1. Do we still require yarn build (which runs npm run babel && gulp svg:combined)? If so, should we we incorporate this into a single yarn icons command?

2. Which icon folder is the source of truth now?
   /assets/svgs/*.svg (used in yarn svgson)
   or
   /src/Icon/icons/*.svg

Verify this folder is no longer needed—then delete!

Todo

• Simplify build steps so SVGs can be used directly with transparency effects and other visuals that might not fit within the rigid svg -> json structure
• Remove svgson from build step
• Create build script that generates React components for each SVG
• Update documentation so adding icons is as easy as: 1) add icon, verify in storybook, release
• Release 3.0 icons update and present at FECoP

Questions

• How do we handle 16 and 24px versions
• How do we handle stroked icons

Since root-id attr have been remove from react, we need to add a data attr to map where are the React components in the Optimizely app while transitioning to React.

Make the release just like OUI

create file related icons (csv, pdf, etc)

The icons have an error caused by the iteration of the generator of shapes on the construction of the SVG.

watch task for exported svgs from sketch