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

hardware-resolve

v0.1.6

Published

Resolves hardware dependencies in package.json

Downloads

40

Readme

hardware-resolve

Resolver for a hardware key in your package.json. Using this, you can can whitelist, blacklist, or substitute files from your directory when pushing to an embedded device.

This is similar to the "browser" field package.json spec: https://gist.github.com/defunctzombie/4339901

For example,

{
  "name": ...,
  "hardware": {
    "grunt": false,
    "./test": false
  }
}

This would prevent the "grunt" module from being pushed, as well as the nested folder "test" (with a leading './') and all files underneath it.

Because the "hardware" key whitelists all packages by default, you can switch to a "blacklist" mode simply by unincluding all modules/files first:

{
  "name": ...,
  "hardware": {
    "*": false,
    "./": false,
    "async": true,
    "./src": true
  }
}

This would only push the "async" module and the "src" directory.

In addition, you can alias files to other files.

{
  "name": ...,
  "hardware": {
    "./index.js": "./hardware-shim/index.js",
    "./hardware-shim": false
  }
}

This would replace the "index.js" root file with the "hardware-shim/index.js" file, but not include the "hardware-shim" directory in the upload.

license

MIT