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

@pnp/buildsystem

v4.0.1

Published

pnp - the build system used within the @pnp/pnpjs monorepo

Downloads

180

Readme

Build system

This project contains the system used to build, package, and publish the npm packages created for each package in the ./packages folder.

Configuration

Configuration is driven entirely by the buildsystem-config.ts file, which uses TypeScript to allow type checking for the elements. The file should provide a default export of an array of build configurations as described below. There can be any number of configurations as needed, but to support the full lifecycle you typically need to cover one config for each role: build, package, and publish.

For each of the three roles, build, package, and publish there exists an interface defining what it should contain. You can have multiple configurations per role, differentiated by name.

The definitions for the configuration options are available in the source. It is intended your buildsystem.config.ts export a valid ConfigCollection;

For an example buildsystem-config please see the one used by PnPjs within this repo.

Run

You can install the tool globally but that isn't requried as it is installed locally when you npm install within the root of the main library project. It has a simple command line:

pnpbuild -n <name of the configuration to run>

OR default to using the "build" configuration:

pnpbuild