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

forkup

v0.3.0

Published

Updater for forked Beaker sites

Downloads

19

Readme

forkup

Updater for forked Beaker sites. It simply checks the version in package.json and downloads a set of files from the upstream.

installation

npm i -S forkup

example

package.json:

{
	"update": {
		"url": "dat://b89507488b68892978dcdc6cb32e21040b2cd0fdcd304c502e17289aad10d95e/",
		"files": [
			"/bundle.js"
		]
	}
}

Somewhere in your project:

const update = require('forkup')

update() // with package.json (recommended)
update('dat://b89507488b68892978dcdc6cb32e21040b2cd0fdcd304c502e17289aad10d95e/', ['/bundle.js']) // alternatively, without package.json (not recommended)

usage

Add an "update" field to your package.json (located in the root folder).

{
	"update": {
		"url": "<upstream dat url>",
		"files": [
			"<file>",
			"<file>"
		]
	}
}

I usually add an /update route to my Choo pages that calls this method. See in solo.

Alternatively you can use the check and update functions separately.

api

forkup([dat_url, files])

Parameters required only if not using package.json. Updates every file in files if the version is less then the version at dat_url (the URL of the upstream site).

check([dat_url])

Parameter required only if not using package.json. Checks if update is available. If yes returns an Array, else false.

update(archives, [files])

files is only required if not using package.json. archives is the output of check. Does the update.