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

node-why

v0.1.0

Published

Zooomr koofers cotweet dropio plaxo plickers, sifteo heekya meebo plickers chegg

Downloads

3

Readme

why

Off-load expensive rendering operations to your back-end cloud servers, using the magic of nodejs.

Never again will you suffer from cross-browser inconsistencies, with this powerful application server (or "app server", if you prefer), all users, everywhere, get an 100% equal rendered page.

Demo: http://why-demo.herokuapp.com/

But how??

why (name pending) acts as a proxy to your static web application, by capturing requests, and dispatching them to a phantomjs instance, which captures a screenshot of your webpage, in its ideal webkit environment, at the correct dimensions for the user's device, and embeds it in a light-weight frame.

Pros:

  • it's ajaxy
  • faster
  • webkit
  • nodejs?!
  • retina ready probably
  • web scale
  • renders cross-browser issues a thing of the past
  • webkit

Cons:

  • none

Are you serious?

Well, it does actually work. Yes, you can even click links...mostly.

Usage:

  1. Install nodejs, npm.
  2. Install phantomjs, make sure it's in your $PATH: $ npm -g install phantomjs
  3. Clone this repo: $ git clone https://github.com/filp/why.git
  4. Install dependencies: $ cd why && npm install
  5. Start the server: $ cd why && bin/server.js [--port 8181 --privPort 9292 --root /path/to/your/app]
  6. Check it :cat:

To-do:

  • Add a kick-ass example web app