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/core

v0.49.11

Published

Contains all LaunchPad design system packages.

Downloads

7,857

Readme

@launchpad-ui/core

A modern, intuitive, and accessible design system made and used by the LaunchDarkly team. Built on React, TypeScript, and CSS.

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

Installation

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

Usage

First, import the CSS variable tokens into your project:

@import '@launchpad-ui/tokens/dist/index.css';
@import '@launchpad-ui/tokens/dist/media-queries.css';
@import '@launchpad-ui/tokens/dist/themes.css';

Voilà, you can now begin using any of the components available in LaunchPad. For the full list, view our Storybook.

import { Alert, AlertKind } from '@launchpad-ui/core';

...

return (
  <Alert kind={AlertKind.ERROR}>
    An unexpected error occurred.
  </Alert>
)

Importing stylesheets

Side-effect imports of CSS files are used for component styles. In LaunchPad, we also expose each component's stylesheets so you can import them directly. For a Remix example, click here.


FAQs

Should I import each component package separately, or import everything at once via the core package?

To guarantee strict compatibility between the component packages your app uses, we suggest importing @launchpad-ui/core instead of importing each component package separately.

If you choose to use LaunchPad via single component imports (e.g. @launchpad-ui/button) on its own, there are two things to be aware of:

  1. You may create token conflicts that expose difficult to diagnose bugs as described here.
  2. You may create inconsistencies in UI styling where subdependencies are used in components as shown here.

View the list of component NPM packages here: https://www.npmjs.com/search?q=%40launchpad-ui

Can I test pre-release versions of components?

To feature flag and test a pre-release version of a component, first install the pre-release using an alias:

$ yarn add @launchpad-ui/alert-beta@npm:@launchpad-ui/[email protected]

Then import and use the pre-release version alongside the version from core:

import { Alert, AlertKind } from '@launchpad-ui/core';
import { Alert as BetaAlert } from '@launchpad-ui/alert-beta';

...

if (enableNewAlert()) {
  return (
    <BetaAlert>...</BetaAlert>
  );
}

return (
  <Alert kind={AlertKind.ERROR}>
    An unexpected error occurred.
  </Alert>
)