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

int-widgeter

v1.0.2

Published

This library is under construction! Expect major breaking changes.

Downloads

10

Readme

Widgeter

This library is under construction! Expect major breaking changes.

Widgeter is a command-line tool that helps you build a system of flat JS widgets.

Let's say we want to make a poll template. Here's our poll project folder:

  poll/
    README.md
    src/
      poll.js
      instances/
        best_movie/
          best_movie.json

poll.js contains the code for injecting the poll onto a page:

  var INSTANCE_DATA = require('instance_data');

  function Poll($cont, data){
    // etc. code to insert a polling widget at $cont
  }

  new Poll($('#poll'), INSTANCE_DATA);

And best_movie.json is an instance configuration. It defines, for examples, the vote options for ONE instance of the poll:

  {
    "options": ["Inception", "The Dark Knight", "Interstellar"]
  }

When you run wid build gop_debate, widgeter creates a bundle at src/instances/best_movie/poll.best_movie.js.

In this bundle, the variable INSTANCE_DATA now resolves to the parsed contents of best_movie.json.

So now you can use <script src="/path/to/your/system/poll/src/instances/poll.best_movie.js"> anywhere on your site.

Now suppose you have a second and third poll in your instances/ folder. Running wid build from anywhere inside the poll folder will rebuild all the poll instances.

This allows you to instantly rebuild all the instances if you modify the template.

Commands

Build

Build a single instance, or all the instances of a project, or all the instances of every project.

Watch

Alias for build, except -w flag is turned on.

List

List all the instance names of a single project