npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@launchpad-ui/icons

v0.17.0

Published

An element that supplements content and represents an action or feature within LaunchDarkly.

Downloads

8,041

Readme

@launchpad-ui/icons

An element that supplements content and represents an action or feature within LaunchDarkly.

See it on NPM! How big is this package in your project?

Installation

$ yarn add @launchpad-ui/icons
# or
$ npm install @launchpad-ui/icons

Usage

Basic

By default, the Icon component expects the package's provided sprite.svg file to be located in /static/sprite.svg of your app. The name prop specifies which icon to render.

import { Icon } from '@launchpad-ui/icons';

const MyIcon = () => <Icon name="info" />;

Custom static location

A custom path to the sprite can be set via the IconContext provider. For example, if importing a static asset returns a resolved URL (like in Vite or Remix) you can do the following in your app to load the icons:

import { IconContext } from '@launchpad-ui/icons';
import icons from '@launchpad-ui/icons/sprite.svg';
import { createRoot } from 'react-dom/client';

const domNode = document.getElementById('root');
const root = createRoot(domNode);

root.render(
  <IconContext.Provider value={{ path: icons }}>
    <App />
  </IconContext.Provider>
);

CORS limitation

Unfortunately SVG sprites cannot be accessed cross-domain. If you are hosting the sprite file in a CDN or different domain you will have to fetch the file and inject it into the document to access the icons directly.

First set the Icon context path to an empty string to indicate the symbols are available in the DOM:

import { IconContext } from '@launchpad-ui/icons';
import { createRoot } from 'react-dom/client';

const domNode = document.getElementById('root');
const root = createRoot(domNode);

root.render(
  <IconContext.Provider value={{ path: '' }}>
    <App />
  </IconContext.Provider>
);

Then fetch and inject the sprite for Icon to render icons correctly:

fetch('https://cdn.example.com/sprite.svg')
  .then(async (response) => response.text())
  .then((data) => {
    const div = document.createElement('div');
    div.id = 'lp-icons-sprite';
    div.style.display = 'none';
    div.innerHTML = data;
    document.body.appendChild(div);
  })
  .catch((err) => {
    console.log('Failed to fetch sprite', err);
  });

To minimize latency, you can preload the sprite file accordingly:

<link
  rel="preload"
  href="https://cdn.example.com/sprite.svg"
  as="fetch"
  type="image/svg+xml"
  crossorigin
/>