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

gitter-archive-cli

v1.0.4

Published

Gitter Chat room message downloader

Downloads

24

Readme

npm npm

Usage

Install yarn package manager.

Install gitter-archive-cli as global.

$ yarn global gitter-archive-cli

# OR

$ npm install -g gitter-archive-cli

Add a .gitterarchiverc[.json|.js|.yml|.yaml] or gitterarchive.config.js file in the directory where you execute the CLI in the following format.

The configuration is loaded using cosmiconfig module.
The archive and no archive room lists are matched using extglob module.

NOTE: if you're copy pasting the following example, remove the comments.

{
  "rooms": {
    "noArchiveList": [
      // rooms not to archive
      // e.g.

      "FreeCodeCamp/FreeCodeCamp"
    ],
    "archiveList": [
      // list of rooms to archive
      // e.g.

      "FreeCodeCamp/*"
    ]
  },

  "groups": {
    "enabled": [{
      "uri": "FreeCodeCamp",
      "id": "57542cf4c43b8c6019778297"
    }],
    "disabled": [
      // groups not to be scanned
    ]
  }
}

Copy the example.env as .env and fill in the details.
Start the archive process.

$ gitter-archive

Use node v7 to run.

# run build
$ yarn run build

# start gitter archive
$ yarn run start

Development

$ yarn global nodemon
$ nodemon -q -x yarn run start:dev

OR for build watch

$ yarn global nodemon
$ yarn run build:watch

Then link it as global

# for globally making the cli and the module available
$ npm link


CLI

Features

CLI options

  • --boost - boost archiving using skip parameter
  • -b - beforeId
  • --gid - group id (required)
  • --guri - group uri (optional)
  • --uri - room uri (optional)
  • --id - room id (required)
  • --ignore, -i - ignore room uri pattern (multiple)

Notes

With a limit of 100 messages/request and 100 requests/minute,
total downloadable messages/minute = 100 x 100 = 10,000 messages per minute

:question: With a skip limit of 5000, how can the scrapping be improved?

Known Bugs

  • After complete archive of rooms, they're marked isArchived as true.
    Hence, the next time the app is run, it removes the archived rooms from the list.
    The expected behavior is that it should simply ignore the archived rooms and only consider the non archived rooms.
    This results in archive pattern download behaving weird i.e. since it cannot verify if a particular room was archived, it redownloads the room and appends it to the end. (resulting in duplication)
  • HTTP Status 429 rate limiter error. Requests are not being rate limited even if using rate-limiter-api

TODO

  • Add cli processor modules