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

spectools-fetch-spec

v0.9.6

Published

Gathers the HTML content of a spec, a list of subresources it fetches and, optionally, a screenshot of the spec.

Downloads

11

Readme

fetch-spec Build Status

spectools-fetch-spec is a PhantomJS-based node module designed to fetch specs, their subresources, and, optionally, grab a screenshot.

It thus contains specific code to deal with specs whose rendering is client-side such as ReSpec.

API

fetchSpec(url [, options], callback)

Visits url, waits for the spec to be fully rendered, grabs its HTML, stores in TMP_DIR, optionally takes a screenshot (which it also stores in TMP_DIR), and returns a JSON object which contains the following properties:

  • filepath (str): filepath of the rendered Web page.
  • screenshot (obj?): an obj with the filepath and dimensions of the optional screenshot.
  • resources (array): a list of all HTTP requests made.
  • clientsideRendering (bool): whether or not the Web page was rendered on the client (e.g. ReSpec drafts).

A JSON Schema describes the return object in more details.

options is… optional and accepts the following values:

  • filename (str): name of the filename in which to save the HTML in TMP_DIR. Defaults to "[UUID].html".
  • screenshot (boolean): takes a 1280x1024 PNG screenshot of the page and saves it as "{filename}.png" in TMP_DIR.
  • screenshot (object):
    • filename (str): name of the filename in which to save the screenshot in TMP_DIR. Defaults to "{filename}_{width}x{height}.png".
    • width (int): width of screenshot. Defaults to 1280.
    • height (int): height of screenshot. Defaults to 1024.
  • timeout (int): the length, in ms before a request is killed. Defaults to none.
  • attempts (int): number of attempts at visiting the page before reporting an error (note this uses an exponential backoff). Defaults to 1.
  • delay (int): time in ms before the second attempt, default to 0 ms.
  • config (str): Path to the PhantomJS JSON config file. Optional.