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

koa2-auth

v0.0.4

Published

A elegant authorization middleware for koa2

Downloads

5

Readme

Koa2-auth

996.icu LICENSE

中文

A elegant authorization middleware for Koa2.

Install

npm install --production koa2-auth

Usage

Before you use any authorization, please register it first.

Auth.prototype.register(authName,function callback(ctx[,next]))

The you can use following to check the permission.

ctx.auth.must("authName");

##Example

var Koa = require('koa');
var app = new Koa();
let Auth = require("koa2-auth");
let auth = new Auth();

auth.register("Never::base", async ctx => {
    ctx.throw(401, {
        code: 419,
        msg: "All Access denied!"
    })
})//before you use, you must register it first.

app.use(auth.auth());

app.use(async ctx => {
    await ctx.auth.must("Never");
    ctx.response.status = 200;
    ctx.response.body = JSON.stringify({
        code: 200,
        msg: "This will never return."
    })
})

Permisson Symbol Example

  • register:
    • base Base authorization Eg: You can use it to check if the session exist.
    • User::base User's base autorization Eg: Ensure it's a user.
    • User::password::write A custom authorzation
    • Item::base Item base authorzation
    • Item::*::Admin Illegibility matching
    • Item::*::base Illegibility matching can also use base mode
    • Item::main::creat Specific checking
  • usage
    • base will trigger following checking
      • base
    • User::base will trigger
      • base
      • User::base
    • User::password::write will trigger
      • base
      • User::base
      • User::password::write
    • Item::ASDFAWSL::Admin will trigger
      • base
      • Item::base
      • Item::*::base
      • Item::*::Admin
    • Item::main::creat will trigger
      • base
      • Item::base
      • Item::main::creat

Authorization Function

If the authorization funtion doesn't throw an error, it means that the permission checking pass. So please use Promise or async in your callback function, as the second param.

The callback function's first param is ctx, which are just the context we know in Koa.

Values in each illegibility matching will be stored in array ctx.auth.params.

If the checking pass, you can return any value, it has no influence on the running; if checking fail, please use ctx.throw to throw the error, or manually:

const err = new Error('Stop here!');
err.status = 403; // Set error code or client will get a 500.
err.expose = true; // Default is true
throw err;

During the checking, if you have something want to return, you can store it in the ctx.auth.checkBack and use it later. All checking will be executed in order, once throw an error, all checking will stop immediately, so you needn't to worry about undefined problem.