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

@confused-techie/atompackagesarchive

v1.0.1

Published

Lets archive all of the fantastic packages made for Atom Together.

Downloads

3

Readme

AtomPackagesArchive

This is a CLI application that can allow you to backup all exisitng packages from Atom.io

There are 9,241 packages or 416 pages paginated at 30 items of content.

Obviously I am using this to keep an archive myself. But HIGHLY recommend anyone else that has some disk space to spare to also archive this data. We don't want one possible failure causing this data to be lost.

Stats

Paginated data when complete creates a folder about 30MB large. With 832 files, comprising of the Paginated Content and Header Content of each page.

The Packages data creates a single file about 27MB large with all 9,241 packages in an array.

Usage

Install:

npm install -g @confused-techie/atompackagesarchive

Use:

atompackagesarchive

Additionally now AtomPackagesArchive supports the choice of what to backup.

This can be specified with the backup option.

atompackagesarchive --backup=OPTION

The following options are valid:

  • ALL

Backs up everything its able to.

  • PAGINATED

Backs up ONLY paginated files of all available packages.

  • PACKAGES

Backs up ONLY the complete package file.

  • WEB

Attempts to back up all web pages, and all web page resources.

! UNDER DEVELOPMENT !

Details

Paginated & Package Data

After making an initial request to determine the last page to grab it will request each page incremented by one until it has requested each page.

Once a page has been requested it will attempt to start saving data its received, and afterwards ask the new concocted packages data be written again. If this process fails it will wait 2 seconds multiplied by the number of failures until it has failed 50 times at which point the program exits. While saving data the output to the screen will show each page being saved very likely not in numerical order. It will show it in the order data is received.