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

edh-widgets

v5.0.0

Published

Widgets are small Javascript components that integrate with everydayhero's API. These include search components and components for showing leaderboard and fundraising totals for campaigns, charities, and networks. Unlike iframe snippets, using widgets all

Downloads

20

Readme

Widgets

Widgets is a project consisting of pre-built JavaScript components that integrate with everydayhero's API. These include search components, components for showing leaderboards, fundraising totals, fitness data and more.

Demos and Documentation

View demos, example code and documentation here:

http://everydayhero.github.io/public-api-docs/

Location

You can find the minified assets at the following locations:

  • //d1ig6folwd6a9s.cloudfront.net/widgets-[0.0.0].js
  • //d1ig6folwd6a9s.cloudfront.net/widgets-[0.0.0].css

To view the uncached version of deployed files go to:

  • https://shared-scripts.s3.amazonaws.com/widgets-[0.0.0].js
  • https://shared-scripts.s3.amazonaws.com/widgets-[0.0.0].css

You can view the deployed example html file at:

  • https://shared-scripts.s3.amazonaws.com/widgets-[0.0.0].html

Commands

OSX users may need to increase the maximum number of open files (default is 256) using ulimit -Sn 1000 to use build, watch, and scripts commands.

$ npm run setup         # install global dependencies, node modules and build production assets
$ npm run build         # build production assets
$ npm run build-dev     # build un minified assets (for debugging)
$ npm run watch         # watch assets and build production (un-minified)
$ npm run jshint        # check javascript code quality
$ npm run scripts       # build production scripts
$ npm run scripts-dev   # build un-minified scripts (for debugging)
$ npm run styles        # build production styles
$ npm run styles-dev    # build un-minified styles (for debugging)
$ npm run deploy-assets # publish build files to S3 bucket (AWS_KEY and AWS_SECRET environment variables must be set)

$ npm test            # run tests
$ npm start           # run local server
$ node_modules/.bin/jest ./__test__/path.js # run an indivdual test file

Publishing updates

  • Non-breaking changes and bug fixes are a minor revision – e.g. 0.0.(2)
  • Breaking changes, css and template re-factors are major revisions – 0.(2).0
  • API updates and large additions/changes are major versions – e.g. (1).0.0

The version number should be updated in the package.json before publishing.