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

plook

v0.2.2

Published

Package lookup service for Bower.

Downloads

14

Readme

Plook

Build Status Dependency Status devDependency Status Code Climate

Package lookup service for Bower.

Usage

Plook is a HTTP server that does package and version lookup in the Bower registry and, if the file is hosted in GitHub, it will print the contents of that file with the right mime type.

The requests format is the following:

http://<plook-server>/<package>/<version>/<file-path>

where:

  • <plook-server> is the address of a running Plook server;
  • <package> is the name of a package registered in the Bower registry, like jquery or angular. The package name must be URL encoded if it contains special chars (like /).
  • <version> is the targeted package version, like 1.0.0 or v2.1.0. The v prefix will be ignored.
  • <file-path> is the path to the file you want to print, like foobar.css or foobar/baz/qux.js.

We have an online server running in http://plook.injoin.io so that you can use it freely with the main Bower registry.

Running and testing Plook

Plook requires only that Node.js and NPM are installed on your system.
Please ensure you have them before continuing on this tutorial.

  1. Clone this repository on your computer:

    $ git clone https://github.com/injoin/plook.git
  2. Next, move into the cloned repository and install NPM dependencies:

    $ cd plook
    $ npm install
  3. Finally, run the plook service:

    $ npm start
  4. In the case you're developing Plook, test your modifications with:

    $ npm test

The service will run in the port 3000 by default, but you can easily override this by setting a PORT env var.

Publishing your own Plook instance

If you want to, you are free to run your own Plook instance. However, we just require that you inform us about it if this instance is going to be public in the internet.
If you are willing to do so, please get in touch via hello [at] injoin.io.

License

Copyright (c) 2014 InJoin Team Licensed under the Apache License.