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

dfpm

v0.0.2

Published

[![npm version](https://badge.fury.io/js/dfpm.svg)](https://badge.fury.io/js/dfpm)

Downloads

5

Readme

dfpm

npm version

A developer friendly JavaScript package manager.

Goals:

  • Developer productivity with existing JavaScript ecosystem and tooling
  • The best performance achievable with Node.js
  • Good explanation of package manager behavior - why the dependency is placed here or there during installation, what factors contributed to this decision and what to do to make the dependency singular for the project
  • Fine-grained control of package manager behavior for various types of workflows
  • Experimental features that has good compatibility with current JavaScript ecosystem

Implemented experimental features:

  • Reproducible installs without "fat" lockfiles. lockTime field is used instead in the package.json file to fixate the time of install. On subsequent installs the highest dependency versions are picked that were published before lockTime. When new dependencies added to the project that were published after lockTime their ranges are resolved to the minimal satisfying version (typically the ranges of newly added dependencies are the latest at the moment when they are added to the package.json).

Usage:

  1. Install dfpm globally first:
npm i -g dfpm
  1. Run installation within your Node.js project directory:
dfpm
  1. Run script foo from package.json:
dfpm foo
  1. Add/remove packages to your project:
dfpm add lodash
  1. Get command line help:
dfpm -h