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

@velocitycareerlabs/template-package

v1.21.0-dev-build.15d7e70f3

Published

Example package for monorepo packages, to be copied as a starting point

Downloads

1,741

Readme

Introduction

The package contains the minimum starting point, of what defines a package for us.

New Package Creation Instructions

Steps

  1. This directory should be copied and renamed to the package name. The "name" field in the package.json should be updated to match the directory name, prefixed by @velocitycareerlabs as seen by the template-package name: "@velocitycareerlabs/template-package"

  2. A description should be added in the "description" field in the package.json

  3. This README.md should be cleared and used for relevant information in the new package.

Some points to take note of:

  • "repository" field in package.json is important and is used later when we setup scopes with lerna

  • They packages actually get published, but we don't consume the packages directly from their publish location, instead we rely on lerna cli within the repository like so:

    lerna add [CONSUMED-PACKAGE-NAME] --scope [CONSUMING-PACKAGE-NAME]

    So if you want did-docs package to use the crypto package, you would do:

    lerna add @velocitycareerlabs/crypto --scope @velocitycareerlabs/did-docs

  • Packages uses standard structure, of src directory, and then test directory for corresponding tests

  • Tests can be run from package.json script

  • Tests will be automatically included in global test suite and run in CI