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

meetup-fetcher

v0.0.7

Published

This is a little project that aims to help Meetup organizers know better their communities through data exploration.

Downloads

11

Readme

Meetup Fetcher

This is a little project that aims to help Meetup organizers know better their communities through data exploration.

Get Started

First of all, we create a new folder and install the module inside of it:

$ mkdir meetupFetcher ; cd meetupFetcher
$ npm install meetup-fetcher

We have to set our meetup API key . If you don't have one, go to:

Request your Meetup Api Key

and grab yours.

Once you have it , you can set an environment variable with your key:

$ export MEETUP_KEY=yourMeetupKey

or substitute 'YOUR_MEETUP_API_KEY' with your key (between quotes) in the following code:

Then create a file (Ex. index.js) that contains the following ( Make proper substitutions as explained by comments) :

var fetcher = require('meetup-fetcher')({
    "dataDir" : __dirname + '/data/', // It will create a folder if it doesn't exists
    "meetupKey" : process.env['MEETUP_KEY'] || 'YOUR_MEETUP_API_KEY', // go to https://secure.meetup.com/meetup_api/key/ and grab yours
    "apiTimeRate" : 15000 // Meetup API will accept around 200 requests/hour
});

// Add urlname communities you want to fetch
// Ex : http://meetup.com/<urlname_of_your_community>/
var communities = ['<urlname_of_your_community>']; // add urlnames without <> (Case Sensitive)

fetcher.get(communities,function(err,result){
    if(err) {
        console.log(err);
    } else {
        console.log("%j" , result);
    }
});

Save it , and from the folder you saved your file , run:

$ node index.js

If everything is OK, you will see something like this :

[YOUR_COMMUNITY - members] Processing 200 items
[YOUR_COMMUNITY - members] Processing 136 items
[YOUR_COMMUNITY - groups] Processing 1 items
[YOUR_COMMUNITY - organizers] Processing 2 items
[YOUR_COMMUNITY - events] Processing 25 items
[YOUR_COMMUNITY - rsvps] Processing 200 items
[YOUR_COMMUNITY - rsvps] Processing 200 items
[YOUR_COMMUNITY - rsvps] Processing 200 items
[YOUR_COMMUNITY - rsvps] Processing 21 items
--- JSON Output ----

If it runs without any error, you will have a new folder called 'data' , and inside of it , some json files (depends how many urlnames you put in communities array, in the example code above).

Each json file stored will have the following skeleton:

{
    "YOUR_COMMUNITY" : {
        "info" : {
            "id" : 124 // your community id
            "topics" : [
                {
                    "Web Design": 659
                },
            ],
            "group_photo" : {} //omitted
            "created" : "date"
            "team" : [
                {
                    "name" : 'yours',
                    "role" : 'Organizer',
                    "member_id" : 424
                }
            ]
        },
        "events" : {
            "count" : 23,
            "list : {} //omitted
        },
        "members" : {
            "count" : 139,
            "list" : {} //omitted
        }
    }
}