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

penn-sdk

v0.2.1

Published

A wrapper for the Penn OpenData APIs

Downloads

16

Readme

Penn OpenData Node SDK

Build Status

This is the Penn Open Data API implementation in NodeJS, currently with support for the registrar, directory, dining, transit, and map APIs. You can view the complete API reference here.

Install

To get started, just run

npm install penn-sdk

Overview

var api = require("penn-sdk")
Registrar = api.Registrar

registrar = new Registrar("API_USERNAME", "API_PASSWORD")
registrar.course("CHEM", "241", function(result) {
  console.log(result)
})

Requesting an API key

To use this library, you must first obtain an API token and password for the API you want to use, which can be done here.

Note: There are separate API tokens for each API.

Contributing

We'd love to accept pull requests! Also, file bugs or ask questions in GitHub issues if you have any problems.

Getting Started

  1. Fork the repository using GitHub's interface
  2. Git clone your repository using git clone YOUR_GIT_URL
  3. Install the required dependencies using npm install.
  4. Start editing the CoffeeScript source files in src.
  5. Write tests!
  6. Make a pull request back to the original repository.

Building

The SDK is written in CoffeeScript, so please make your changes in the CoffeeScript source files in src and they can be compiled into JavaScript using make js.

Testing

You can test the work you have using make test, which uses Mocha to run the tests inside of the test directory. You should have environment variables in your shell that specify your API keys in the format REGISTRAR_API_USERNAME and REGISTRAR_API_PASSWORD. If you prefer to have these tests run while you're editing automatically, you can run make watch from your terminal.

TODO

  • [ ] Open Data APIs
    • [x] Implement registrar API
    • [x] Implement directory API
    • [x] Implement dining API
    • [x] Implement transit API (Partial)
    • [x] Implement map API (Partial)
    • [ ] Implement news API
  • [x] Publish to npm
  • [x] Continuous testing using Travis CI
  • [ ] Return result_data in methods
  • [ ] Write full API documentation using jsdoc

Authors

  • Adel Qalieh

License

MIT Licensed