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

npm-filepack

v0.5.1

Published

Install dependencies from built tarballs with ease

Downloads

10

Readme

npm file+pack protocol feature

This is an idea for RFC https://github.com/npm/rfcs/pull/150

Trying it locally

After cloning the project, do:

npm install
npm link

Then you can cd into tests/npm-filepack/root-package and run:

npm-filepack
npm start

Or cd into tests/filepack/root-package and run:

filepack
npm start

This will install two local dependencies test-package-a and test-package-b, where test-package-b also depends on test-package-a while also requiring typescript compiling, which will be executed before packing and linking to root-package

npm-filepack vs filepack?

npm-filepack is meant to be like a "built-in" behavior of npm, if npm allowed file+pack: protocol.

filepack is an external tool (very much like lerna or others), which will use filepackDependencies and filepackDevDependencies from package.json to resolve tarballs. This produces a side effect on package.json, adding tarball entries in dependencies and devDependencies respectively!

Once filepack has been run once:

  • it's not necessary to run it again until we want to rebuild tarballs
  • npm install can be run normally, and all npm commands will be working :tada: