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

sero-enterprises

v0.0.40

Published

https://medium.com/@robinviktorsson/setting-up-a-modern-typescript-project-with-rollup-no-framework-e24a7564394c

Readme

READ ME

https://medium.com/@robinviktorsson/setting-up-a-modern-typescript-project-with-rollup-no-framework-e24a7564394c

https://medium.com/@toukirraju/building-a-react-component-library-with-typescript-rollup-and-storybook-9f480d828867

https://dev.to/vvkkumar06/setup-rollup-for-react-library-project-2024-3jea

How To Setup Rollup Config

https://dev.to/proticm/how-to-setup-rollup-config-45mk

NPM Login

Username: jon-yowe email: [email protected]

Security Key Name: jon-yowe 06cafad136aebf7ac965aeaf2f94bb4b8a7b446ff9bde90dc5747d0aa1e98df0 3bd08bde09ae18f884a0684c139c559a39b6f310f0e41c09f03f5b3fa5c7f4ef e55ac54d612d6e5538743c3e8c24680130f684f31afcfa3ba89e3733f7035a1c 39c67e9f49b9fe559f013afb39012c27f258e86ed2bc7bbeef8b157a979e580b 38daaba3ebeb39c1272d7e367124bddb62220cebb721021510a7c67d9eaf0fc0

yalc

https://www.npmjs.com/package/yalc https://dev.to/zachsnoek/using-local-npm-packages-as-dependencies-with-yalc-2g56

In roll-up project (sero-enterprise)

yalc publish

npm run build Publishes the /dist directory

yalc push

Pushes new changes to the .yalc local repo

In dependent project

yalc add sero-enterprises

Modifies the package.json and lock files to point the the yalc repo

Remake project dependecies

Delete node_modules npm install

yalc remove sero-enterprises

reverts the dependent project before adding yalc

npm link

To link a local npm package for development and testing within another project, the npm link command is used. This creates symbolic links, allowing changes in the local package to be immediately reflected in the consuming project without needing to publish and install the package. Steps to link a local package:

Prepare the local package

Navigate to the root directory of the local package you want to link (the one that will be used as a dependency).

Run npm link. This registers the package globally on your system, creating a symbolic link in the global node_modules directory that points to your local package.

cd /path/to/my-component
npm link

Link the package in the consuming project

Navigate to the root directory of the project that will use the local package as a dependency.

Run npm link , where is the name defined in the package.json of your local package. This creates a symbolic link within your project's node_modules directory that points to the globally registered link, which in turn points to your local package.

cd /path/to/my-app
npm link my-component

npm ls -g Check if package is linked

This command lists all globally installed packages. npm link creates a symbolic link in the global node_modules directory. Look for your package in the output. If it's npm linked, its entry will show the path to your local source directory.

Use

npm ls -g

/Users/jonathanyowe/.nvm/versions/node/v22.14.0/lib ├── [email protected] ├── [email protected] ├── [email protected] └── [email protected] -> ./../../../../../Documents/Projects/react/roll-up

npm unlink

By default, npm unlink also removes the package entry from package.json. If you want to keep the package listed in package.json but remove the symlink, use the --no-save flag

To unlink a specific package from a project

cd /path/to/your/project
npm unlink <package-name>

npm unlink <package-name> --no-save

To remove the global link for a package

cd /path/to/your/package-source
npm unlink

if npm unlink fails

npm unlink -g sero-enterprises

npm uninstall -g sero-enterprises