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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sds-stream/library

v1.0.60

Published

Shared components for CANapps by Stream Data Systems

Readme

SDS Nextjs Component Library

To directly view an example of how this library works, look at the existing files in the src folder.

It is desirable to abstract out components that are regularly used across sites into a separate library which you then call from a higher level. Often when using components in sites, you use default exports. When importing your component to this library, you want to use named exports. For example

const Component = ... // Code for component
... // Misc other supporting code

export default Component;

The above is instead written as

const Component = ... // Code for component
... // Misc other supporting code

export { Component };

You also don't need the index.js file instead of the component folder. In the library, the index.js file lives one folder up in the parent and exports the individual components like so:

export { Component } from './Component/Component';

All of this will be fairly clear when going over the existing components and index.js file in the src folder.

How to update library

Once you're done adding your component appropriately, run the following commands: NOTE: DO THE LOG IN ONLY THE FIRST TIME

git add . # run this on whatever particular folder/files you want to add
git commit -m 'commit message'
npm login # the username and password in Case 476, choose your own email address
npm run build
npm version patch # the npm version command can take other flags like major, minor, patch. but going with patch for now
npm publish

Using components from library in other places

The above steps are only really necessary when you're adding or modifying the library. If you simply want to use a component from the library, you don't even need to clone this repository. All you do is go inside the folder that you'd like to add a component to and run the following:

npm install @sds-stream/library

And then in your appropriate source code, do an import like:

import { Component1, Component2, ... } from '@sds-stream/library';