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

httpignore

v3.0.2

Published

Programmatic and CLI access to reading and computing the results of a .httpignore file

Downloads

11

Readme

httpignore

Build Status

This is a utility and CLI for interfacing with httpignore files.

A word on httpignore files

I made them up (thanks to @lund0n for the inspiration). I wanted a way to be able to serve up files from my node_modules directory but to allow individual modules to mark things which, while they are published, ought not to be served over HTTP.

My use case was for a private npm registry where I don't mind if internal people can see, say, our README.md files, but I don't want all our internal documentation to be customer facing.

The approach is simple and should be very familiar if you've used a .npmignore or a .gitignore file. It follows all the same rules as those files. In this case they define what files ought not be served over HTTP.

Installation

npm install httpignore. All the normal flags apply.

API

ignored()

Returns a promise which resolves with an array of all the filters that are being applied via the httpignore files.

files()

Returns a promise which resolves with an array of all files which are allowed after the filters are applied.

copy(dest)

Returns a promise which resolves once all files from the files call are copied to the directory dest. If dest does not exist, it will create it.

CLI

Usage:

httpignore-copy <dest>

Performs the copy api method on the directory specified by dest. Paths are relative to the current working directory.

Development

A standard npm install and npm test will get you running here. Please merge squash PRs.

License

MIT

Copyright 2016 Matt Winchester

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.