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

nock-github-oauth

v1.1.0

Published

GitHub OAuth HTTP intercepts via nock.

Downloads

8

Readme

nock-github-oauth

Build Status Dependency Status devDependency Status Code Climate

NPM

GitHub OAuth HTTP intercepts via nock.

Installation

Via npm: npm install nock-github-oauth --save-dev

Usage

nock-github-oauth is meant to be used from a testing context. Specifically, it mocks the following routes for https://github.com:443:

  • GET /login,
  • GET /login/oauth/authorize, and
  • POST /login/oauth/access_token (returns a mocked token in the body).

The package exposes a method (exports.nock) that establishes the intercepts for each of the aforementioned Github OAuth routes. Here is an example of how to use it in a (https://github.com/hapijs/lab)[lab] test:

var Lab = require('lab');
var lab = exports.lab = Lab.script();
var nock = require('nock');
var github = require('nock-github-oauth');

lab.experiment('module that depends on GitHub OAuth', function() {
	lab.before(function(done) {
		// Setup github oauth http intercepts
		github.nock(done);
	});

	lab.after(function(done) {
		// Remove all intercepts
		nock.cleanAll();
	});
});

Finally, for convience, the package also exposes the https host for GitHub OAuth via exports.host (https://github.com:443). and the mocked oauth token returned by the intercepted POST /login/oauth/access_token via exports.token. You can access these like so:

var github = require('nock-github-oauth');
var mockToken = github.token;
var githubHost = github.host;

Contributing & Tests

When adding new features, fixing bugs, etc. please make sure to include the appropriate tests and ensure all tests are passing before sending a pull request. We use lab for unit testing, here's how to run tests:

npm run test

Additionally you'll want to ensure the files lint:

npm run lint

License

MIT