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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@the-story/standard-core

v1.1.1

Published

Standard landing boilerplate

Readme

Standard Core by The Story

A set of core UI components, configuration, and utilities to be reused across other projects. The library is developed in isolation in Storybook and then verified inside external applications.

How to use the library in a project

During development, we use yalc for local linking (a lightweight alternative to a private npm registry).

  • yalc repository: https://github.com/wclr/yalc

Quick start (local link via yalc) — using PyCharm Run configurations

  1. In the library (this repository):
    • In PyCharm, use the already added Run configurations: "build", "yalc:publish" (optionally also "yalc:push").
    • Run "yalc:publish".
  2. In the consuming application:
    • Use the existing project configuration that adds the package via yalc (e.g., "yalc:add" or a "Shell Script" configuration with: yalc add @the-story/standard-core).
    • Run the prepared configuration that installs dependencies (e.g., NPM "install"/"yarn install").
    • Start the application using its dedicated Run configuration and verify it works.
  3. Updating when the library changes:
    • In the library: run "yalc:publish" to push the update to all consumers.
    • In the app: run the "yalc:update" configuration to update the package; optionally restart the dev server.
  4. Removing the yalc package in the app: run the existing configuration that removes the package (e.g., a "Shell Script" with: yalc remove @the-story/standard-core).

Note: Eventually the package may be published to an npm registry (public or private). yalc is intended only for local development.

Component development (Storybook)

We use Storybook to build and preview components. Every component MUST have at least one story that demonstrates its basic usage and state variants.

  • Launching Storybook: in PyCharm run the existing NPM configuration "storybook" from the Run toolbar.
  • Building a static version: in PyCharm run the existing NPM configuration "build-storybook".
  • Hosted Storybook: https://standard-core.storyline.cloud

Guidelines:

  • In this project, stories live in the src/stories directory, grouped into categories (e.g., Atoms, Molecules) and mirroring component structure, e.g., src/stories/Atoms/Button/Button.stories.tsx.
  • Use the *.stories.ts(x) naming and include multiple usage variants of the component.
  • Add different prop variants and states (loading/disabled/error), including edge cases.
  • If a component has external dependencies or requires context (Theme/Intl/Router), prepare appropriate Storybook decorators.

Verification in an external application

After confirming the component works in Storybook:

  1. In the library, run the NPM "build" configuration in PyCharm.
  2. Next run the "yalc:publish" configuration.
  3. In the consuming app, use its prepared PyCharm configurations (e.g., "yalc add", "install", "dev") and test the integration (styles, interactions, SSR/CSR, etc.).

Environment variables

These variables should be configured in the application that uses the library (in its .env file), not in this package.