@phosphor-icons/core
This repository hosts the raw SVGs and catalog data – including tags, categories, and release versions – of all icons in the Phosphor Icons family. It serves as the basis for our fuzzy-search on our website and other tools, and as a dev dependency in the build process in some of our framework-specific libraries. You may find this package is useful to you in implementing a port of Phosphor to your preferred framework, or as a source of truth for our current SVG assets.
Installation
pnpm add @phosphor-icons/core
Assets
This package exposes all icons as SVG assets, grouped by weight, under the /assets
directory (i.e. /assets/<weight>/<kebab-name>-<weight>.svg
), and also aliased so that /assets
can be omitted from the path in projects that support import maps. These files can be used as needed for custom implementations or ports. Your framework and build tooling may require custom type declarations to recognize and transform "*.svg"
files into modules.
Note for Vite users: As of Vite 4.0.4 (current at the time of writing), a bug in one of its dependencies prevents wildcard exports from being resolved. This will be fixed in Vite 4.1.
Example
import ghostDuotone from "@phosphor-icons/core/duotone/ghost-duotone.svg";
Using SVGR (includes create-react-app
projects):
import { ReactComponent as GhostDuotone } from "@phosphor-icons/core/duotone/ghost-duotone.svg";
Catalog
This package exposes a named export icons
, which is an array of IconEntry
objects represententing each icon, its name in both kebab-case
and PascalCase
, the catergories and tags associated with it, as well as the version it was published in and the most recent version it was updated in.
It also includes an optional alias
field, which if present, contains deprecated names for the icon for backwards-compatibility purposes, and a codepoint
field, which is a stable decimal representation of its Unicode code point in font implementations such as @phosphor-icons/web and @phosphor-icons/flutter.
interface IconEntry {
name: string;
pascal_name: string;
alias?: {
name: string;
pascal_name: string;
};
codepoint: number;
categories: readonly IconCategory[];
tags: readonly string[];
published_in: number;
updated_in: number;
}
Note: Duotone icons rely on overlaying two glyphs (a background and foreground layer), and thus use 2 codepoints. All codepoint bases are even numbers, so the codepoints associated with duotone icons are codepoint
and codepoint + 1
. The codepoint
feature is not yet stabilized, and should only be relied upon in versions >=2.1.0
.
An additional type export, PhosphorIcon
, represents the literal type of the icons
list. You can use it to extract narrowed types such as valid icon names, which can be useful for constraining parameter types in ports:
type IconName = PhosphorIcon["name"];
Our Related Projects
If you've made a port of Phosphor and you want to see it here, just open a PR here!
License
MIT © Phosphor Icons