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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@hansogj/utils-ws

v0.1.0

Published

[![example workflow](https://github.com/hansogj/utils-ws/actions/workflows/build.yml/badge.svg)](https://github.com/hansogj/utils-ws/actions/workflows/build.yml/badge.svg)

Downloads

3

Readme

example workflow

Various frontend utils and polyfills

This libs are using npm workspaces to achieve mono-repo multi-packages

Workspaces

Install

pnpm i --frozen-lockfile

Add new package

pnpm run generate -- "<name-of-package>"

Dependencies & devDependencies are installed into your new package with

cd  packages/<target>
pnpm add some-package
cd -

To in make internal dependencies, go to target package and do:

cd packages/<target>
pnpm add --workspace <name-of-package>
cd -

Test & Build

From root run

pnpm run test
pnpm run build

These commands will test and build all the packages respectively

Versioning

The pnpm-script ws:version:set:all will ensure all packages are updated with same strategy, and git tagging is done right

pnpm run ws:version:set:all <strategy: major|minor|patch....>

Changing version to a single workspace package, simply enter the package and do

cd packages/<target>
pnpm version <strategy: major|minor|patch....>
../../scripts/ws-scripts.sh gitCommitTagPush
cd -

Publish

pnpm run build
cd packages/<target>
pnpm publish
cd -

or

pnpm run build
pnpm -r publish