React Octicons!

[shawnbot]

This is a rehash of #196 introducing a React component API that looks like this:

import Octicon, {Zap} from '@github/react-octicons'

export default () => <Octicon><Zap /></Octicon>
// or
export default () => <Octicon icon={Zap} />

With credit to @hiendv for the inspiration in #196 (comment) 🍻

Note that there's one wild assumption in the generated per-icon components here, and it's that the SVG from the octicons package is valid XML, which is what allows us to use it in JSX without munging it. I've checked the generated icon component JS into git so that we can look at it without the module having to publish.

TODO

• Add new tests for React Octicons
• Get tests passing
• Update README.md with new API (see rendered)
• Deploy test site

[shawnbot]

If both the width and height aren't provided, we compute the width or the height — depending on whether they provide width, height, or size (which can be either a number or a string that's mapped via sizeMap).

[shawnbot]

Note: the parens on that last line above are a linting requirement. * and / have the same operator precedence, so I think the rule that wants one expression grouped exists to help us be more explicit about what it's doing.

[shawnbot]

Is there a good reason not to allow bottom here?

[shawnbot]

This was wrong for me to include. I removed it in 02a007a.

[shawnbot]

This is used when we call NODE_ENV=production next in the start run-script.

[shawnbot]

Don't lint the generated files. 🙈

[shawnbot]

This is for development. I've added the equivalent to engines.node in the package.json as well.

[shawnbot]

FYI you can see what the separate ESM and UMD builds look like in the alpha release of b61e03c:

• ESM (with import and export statements)
• UMD (with require() statements)