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

foursquare-js

v0.1.0

Published

Fault-tolerant Foursquare API v2 wrapper for Node JS.

Downloads

7

Readme

node-foursquare-2

Fault-tolerant Foursquare API wrapper for Node JS. With slight update.

Install

npm install node-foursquare-2

Version History

  • v. 0.0.1 Added a small update to the Venue.search() method to support using the near parameter.

Use

The Foursquare module takes a configuration parameter containing logging and client keys. It also supports alternate Foursquare URLs if necessary, (but that is unlikely).

var config = {
  "secrets" : {
    "clientId" : "CLIENT_ID",
    "clientSecret" : "CLIENT_SECRET",
    "redirectUrl" : "REDIRECT_URL"
  }
}

var foursquare = require("node-foursquare")(config);

Once instantiated, you just need to set up endpoints on your own server that match your OAuth configuration in Foursquare. Using Express, for example:

var app = express.createServer();

app.get('/login', function(req, res) {
  res.writeHead(303, { "location": Foursquare.getAuthClientRedirectUrl() });
  res.end();
});


app.get('/callback', function (req, res) {
  Foursquare.getAccessToken({
    code: req.query.code
  }, function (error, accessToken) {
    if(error) {
      res.send("An error was thrown: " + error.message);
    }
    else {
      // Save the accessToken and redirect.
    }
  });
});

Foursquare API Version and Deprecation Warnings

Foursquare allows consumers to specify a "version" of their API to invoke, based on the date that version became active. For example, passing a version string of "20110101" uses the API as of Jan 1, 2011. By default, this library will use a version of today's date.

To enable a different version of the API, add the following to configuration.

var config = {
  ...
  "foursquare" : {
    ...
    "version" : "20110101",
    ...
  }
  ...
}

When using an older API, Foursquare will provide deprecation warnings, (if applicable). By default, this library will write these warnings to the log, which will only be visible if logging for "node-foursquare" is turned on, (see "Logging", below).

You can configure this library to throw an error instead:

var config = {
  ...
  "foursquare" : {
    ...
    "warnings" : "ERROR",
    ...
  }
  ...
}

Logging

This module uses Log4js to log events. By default, everything is set to "OFF" and no appenders are configured. If you want to output logging messages from the different modules of this library, you can add overrides to your configuration object. For example, to log INFO (and higher) messages in Venues to the console:

var config = {
  "log4js" : {
    "appenders" : [{
      "type" : "console"
    }],
    "levels" : {
      "node-foursquare.Venues" : "INFO"
    }
  }
  ...
}

var foursquare = require("node-foursquare")(config);

For a list of existing logging points, refer to config-default.js.

For more information, see: https://github.com/csausdev/log4js-node

Testing

To test, you need to create a config.js file in the /test directory as follows:

module.exports = {
  "secrets" : {
    "clientId" : "YOUR_CLIENT_ID",
    "clientSecret" : "YOUR_CLIENT_SECRET",
    "redirectUrl" : "http://localhost:3000/callback" // This should also be set in your OAuth profile.
  }
};

Then, simply invoke the test.js file with Node.JS:

node test.js

If you hit http://localhost:3000, you'll be redirected for an authentication token.

If you hit http://localhost:3000/test, you'll test the entire library with no authentication, (and get appropriate errors for protected endpoints).

If you hit http://localhost:3000/deprecations, you'll test an endpoint with older versions and errors vs. warnings.

Testing results will be logged to the console.

All tests use examples as suggested by the Foursquare Endpoint Explorer.

Documentation

Detailed documentation is available in the /docs directory.

(In the latest version of JSDoc 3, the file names are replaced with random identifiers. Not sure why, we'll see if they can get that fixed soon.)

Notes

This module is a read-only subset of the full Foursquare API, but further capability, (adding, posting, updating, etc), is forthcoming. Bugs and Pull Requests are, of course, accepted! :-)

This project is a ever-so-slight enhancement of: https://github.com/clintandrewhall/node-foursquare Which is a refactoring and enhancement of: https://github.com/yikulju/Foursquare-on-node