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

eci-cygnus

v0.0.5

Published

ECI Cygnus - Design System and Component Library

Downloads

11

Readme

Built With Stencil

Design System Core

This package is based off the stenciljs component library starter.

This package is responsible for:

  • Development of shared web-components under ./src/components/
  • Building of framework specific wrappers under ../frameworks
  • Building of distributable web-components under ./dist

There are also utilities for publishing to an internal npm repository.

Requirements

Development

npm install
npm start

To build the component for production, run:

npm run build

To run the unit tests for the components, run:

npm test

For further information check out StencilJS Docs.

Storybook

npm run storybook

To connect a figma document to a story, you must add this to the parameters key in the default export of the story file:

design: {
    type: "figma",
    url: "<figma-file-url>",
}

The Design tab will then read this configuration to populate it's content. The design tab is enabled for all stories using withDesign global parameters.

Naming Components

We prefix all components with eci-

Using this component

There are three strategies we recommend for using web components built with Stencil.

The first step for all three of these strategies is to publish to NPM.

Elements can be directly loaded (with a bundler) via eci-cygnus/components/my-component'. Alternatively (not recommended), you may use lazy loading by requiring eci-cygnus/loader/` and use the components in your markup which will then be lazy loaded via network request. This will cause a flash of unstyled component and is thus not recommended generally.

Script tag

  • Put a script tag similar to this <script type='module' src='https://unpkg.com/[email protected]/dist/my-component.esm.js'></script> in the head of your index.html
  • Then you can use the element anywhere in your template, JSX, html etc

Node Modules

  • Run npm install eci-cygnus --save
  • Put a script tag similar to this <script type='module' src='node_modules/eci-cygnus/dist/my-component.esm.js'></script> in the head of your index.html
  • Then you can use the element anywhere in your template, JSX, html etc