Michael Salinger

Also please change the PR to point to the `dev` branch instead of `master`.

@visvk Can you rebase this PR to get rid of the conflicts?

@visvk That should be fine.

@TheNoim Can you describe your use case for this? I'm not quite sure why it's necessary...

`v3.1.0` should support this - you'll have access to the request context within all model methods. You can try it out now by using `next` for the version in your...

I'll get stuff merged next week and release a beta.

Just an update here - waiting on a few responses on a couple of more PRs to see if we can get it in. There's a breaking change, so we'll...

@razvanz It's a very small breaking change - changing the server_error status code from 503 to 500. I'm not sure if it's worth keeping the 3.x version around just for...

@razvanz The problem I'm running into here is security-related. node v4 is completely EOL by the node.js project, and no longer has security support; also, the linter we are using,...

Today I published two versions of node-oauth2-server: *3.0.1* contains dependency upgrades only *3.1.0-beta.1* installed under the `next` tag in npm, this contains a bunch of fixes and a couple of...