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

depie

v0.1.5

Published

Package for managing external dependencies on various systems

Downloads

7

Readme

depie

Build Status

A tool that attempts install 3rd party dependencies so you don't have to!

There is a lot of duplicated work/code going into native node modules. This work could be entirely mitigated if node modules used OS packaging systems which have, for the most part, already built these dependencies.

Example usage

The primary entrypoint for depie is intended to be the package.json file. This lets you install dependencies prior to needing them. For example:

{
  "name": "example",
  "version": "1.0.0",
  "description": "a test module for depie",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "install": "echo 'var d = require(\"depie\"); d.install([\"libsodium\"])' | node"
  },
  "author": "",
  "license": "MIT",
  "dependencies": {
    "depie": "^0.1.0"
  }
}

The above would install depie using npm then libsodium using the operating systems native package manager.

Now you can build your native module without needing to repackage and rebuild all the source code for libsodium!

Package aliases

Packages are aliased to allow for a single entrypoint across all systems. This requires work, but ultimately, it will be less work/time than is spent downloading/compiling the dependent code for every install of your native module!

Here is an example of the alias for libsodium on Ubuntu:

"libsodium": "libsodium-dev"