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

@niord-org/niord-info

v0.1.0

Published

Reusable Angular library for Notices to Mariners (NM)

Readme

niord-info

Reusable Angular library for Niord-based apps.

Published package name: @niord-org/niord-info

This directory is intended to become the standalone library repo.

The temporary standalone staging remote can be a fork, but the final canonical home is:

  • https://github.com/NiordOrg/niord-info

During the temporary combined-workspace phase, niord-info-dk still consumes this library source directly from the parent workspace for fast local development.

Standalone library development

Install dependencies and build:

npm install
npm run build

Build output:

  • dist/

Temporary workspace development

From the parent workspace root:

npm run dev

That lets niord-info-dk use this library source directly without publishing every change.

GitHub Actions release flow

  • CI workflow: .github/workflows/ci.yml
  • Release workflow: .github/workflows/release.yml

Required GitHub secret:

  • NPM_TOKEN (npm publish token)

Release steps:

# in the standalone niord-info repo
npm version patch
git push
git tag v$(node -p "require('./package.json').version")
git push --tags

The tag-triggered workflow validates the v* tag against package.json, builds the library, creates a GitHub Release with the packed .tgz artifact, and publishes to npm.