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

@tatumcreative/get

v1.0.0

Published

A simple XMLHttpRequest wrapper

Downloads

5

Readme

@tatumcreative/get

A collection of zero-config GET functions for fetching things on the internet. Make sure node and npm is installed and then run npm install @tatumcreative/get. Then require the function you need like const { getText } = require("@tatumcreative/get"). The internals use only ES5 code, but all examples and tests are ES6.

getText(url) => Promise(text)

Load the text, returns a Promise that resolves to the text. The error is the failing XMLHttpRequest object.

getText("/foo.txt").then(
  (text) => console.log('Here is the text', text),
  (error) => console.error('There was an error', error),
)

getJSON(url) => Promise(json)

Load some JSON, returns a Promise that resolves to the parsed JSON object. The error is either the failing XMLHttpRequest object, or a SyntaxError if the JSON failed to parse.

getJSON("/foo.json").then(
  (json) => console.log('Here is the JSON object', json),
  (error) => console.error('There was an error', error),
)

getImage(url) => Promise(imageElement)

Load an HTMLImageElement. It only resolves after the image is fully downloaded.

getImage("/foo.png").then(
  (imageElement) => document.body.append(imageElement),
  (error) => console.error('There was an error', error),
)

getImageData(url) => Promise({data, width, height})

Load an image and get an ImageData object {data, width, height}. The data property is a Uint8ClampedArray that is an array with values 0-255.

getImageData("/foo.png").then(
  ({data, width, height}) => console.log('The first pixel is', data.slice(0,4)),
  (error) => console.error('There was an error', error),
)

Example with parameters

These functions don't care about fancy parameters, but it's trivial to do with the query-string package.

query-string

const { getText } = require('@tatumcreative/get')
const { stringify } = require("query-string")

getText("/foo?" + stringify({
  bar: 'a',
  baz: 'b',
}))