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

node.pack

v0.0.3

Published

node.pack =========

Downloads

15

Readme

node.pack

Pack a bunch of installed NodeJS (and other self-contained) code packages into an archive for optimized batch provisioning in identical environments.

This means you take npm and other package registries out of the picture when deploying your code for the second time in an identical environment. It makes deployment much more resilient to failure and guarantees you are running IDENTICAL code every time.

node.pack empowers you to create multiple packs from the same installation so you can put infrequently changing third party packages into one pack and your own code into another pack.

node.pack also creates NodePACK build stream branches which have all submodule source code inlined and contain node.pack.json descriptors with pointers to packs for runtime installation.

Origin: This project stems from work I have been doing for sm.genesis and serves to validate the filename format and built package bundles for reliable runtime code distribution.

Filenames

Format: <PackageName>~<PackageVersion>~<PackName>~<Platform>~<Architecture>~<Environment>~<PackAspect>.<FormatExtension>

Where:

  • Environment - Defaults to NodeJS-4 and can be set to describe a more specific compile environment

License

MIT