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

@imposium-hub/components

v2.17.9

Published

React & Typescript component / asset library for Imposium front-ends

Readme

Imposium Component Library

A react component library for streamlining front end Imposium apps.

Installing via NPM

npm i @imposium-hub/components -s

How to develop or pull in components locally

If you are developing components or you are working on a fresh project in parallel with components, you may not want to have to go through the NPM publication process everytime you make changes. You can work locally by taking advantage of the npm link feature, for more detailed info on this see: link docs.

To make a symlink for the package locally run the following in the root of this repo:

npm link

Then in the root directory of the project you want to test with run:

npm link @imposium-hub/components

How to develop the library

To get started, first install the library dependencies:

npm i --legacy-peer-deps

Run the start script to build the library, and watch the source files for changes:

npm start

To lint the project, run:

npm run lint-fix

To build the project without watching for changes, run:

npm run build

How to release a new version of to NPM

To release a new version of the library, make sure you are on the master branch, and then run the following commands:

npm login

this will trigger to login to nodejs then

npm run release-as

This will lint & build the library, then use np to deploy a new version to npm & github. Follow the steps in np to finish the release. If either the build or the lint fails, the release will be cancelled.

How to bundle components in your project

To import a react component in your project, use the following syntax to support tree-shaking:

import * as React from 'React';
import { render } from 'react-dom';
import { ImposiumHeader } from '@imposium-hub/components';

render(
    <ImposiumHeader
        accessData = {...}
        activeOrganization = {...}
        onOrganizationChange = {(id: string) => {...}}
        logout = {() => {...}} />
);

How to bundle styles in your project via LESS

To import the LESS for the component library, use one of the following imports:

@import "your_project_path/node_modules/@imposium-hub/components/dist/styles.less";

Right now styles are shipped as a single bundle however as the library grows in size & complexity individual CSS bundles per component may added at a later time.

Storybook

To run the storybook UI at localhost:6066, run:

npm run storybook

This will run a clean build of the component library, and spin up the storybook UI.