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

hoodie-plugin-debug

v1.0.1

Published

Basic Hoodie plugin layout

Downloads

3

Readme

Hoodie Plugin Template

This is a template layout for a Hoodie plugin. It contains a Gruntfile with appropriate tasks for running jshint, unit tests and browser tests against a Hoodie server.

You'll need to have phantomjs and grunt installed:

npm install -g phantomjs grunt-cli

To run tests / linting

Install dev dependencies:

npm install

Then run the 'test' task

grunt test

You can also run test:unit or test:browser individually.

If your plugin depends on other plugins being present (usually it will at least depend on the hoodie users plugin), then make sure they're included in your devDependencies in package.json and listed in the hoodie.plugins property. This way, they'll also get started when the browser tests are run.

NOTE: When running the browser tests, the grunt tasks will remove the local Hoodie 'data' directory completely so you get a clean database to test against. Be careful you don't use this path for any data you may want to keep!