auth-server - npm Package Compare versions

Comparing version 2.2.3 to 2.3.0

package.json

@@ -9,10 +9,10 @@ {
   ],
-  "version": "2.2.3",
-  "homepage": "https://github.com/wpreul/oauth",
+  "version": "2.3.0",
+  "homepage": "https://github.com/geek/oauth",
   "repository": {
     "type": "git",
-    "url": "git://github.com/wpreul/oauth.git"
+    "url": "git://github.com/geek/oauth.git"
   },
   "bugs": {
-    "url": "https://github.com/wpreul/oauth/issues"
+    "url": "https://github.com/geek/oauth/issues"
   },
@@ -22,3 +22,4 @@ "main": "index",
   "devDependencies": {
-    "lab": "0.1.x"
+    "code": "1.x.x",
+    "lab": "5.x.x"
   },
@@ -35,5 +36,5 @@ "optionalDependencies": {},
       "type": "MIT +no-false-attribs",
-      "url": "https://github.com/wpreul/OAuth/blob/master/LICENCE"
+      "url": "https://github.com/geek/OAuth/blob/master/LICENCE"
     }
   ]
 }

README.md

 # OAuth for Node
 =====
 
-[![Build Status](https://travis-ci.org/wpreul/OAuth.png)](https://travis-ci.org/wpreul/OAuth)
+[![Build Status](https://travis-ci.org/geek/OAuth.png)](https://travis-ci.org/geek/OAuth)
 
@@ -72,2 +72,2 @@ ## Contributors
 
-4. So there is an odd amount of extra work involved in for a confidential client using the authorization_code grant type.  After a user authorizes a client to operate on their behalf the response is either a token or a code.  If it is a token then the client doesn't get a refresh token.  If it is a code then the client must make an extra request to get a token, but will also get a refresh token.  I have decided to provide a third option, which is surprisingly lacking from the spec.  This third option is to pass in response_type=code_and_token.  When the client does this it will get a token back that it can immediately use while at the same time making a request to the token endpoint to get a more permanent token with a refresh token.  I hope you will see this extra option as an improvement over the spec.
+4. So there is an odd amount of extra work involved in for a confidential client using the authorization_code grant type.  After a user authorizes a client to operate on their behalf the response is either a token or a code.  If it is a token then the client doesn't get a refresh token.  If it is a code then the client must make an extra request to get a token, but will also get a refresh token.  I have decided to provide a third option, which is surprisingly lacking from the spec.  This third option is to pass in response_type=code_and_token.  When the client does this it will get a token back that it can immediately use while at the same time making a request to the token endpoint to get a more permanent token with a refresh token.  I hope you will see this extra option as an improvement over the spec.

test/auth.js

 // Load modules
 
+var Code = require('code');
 var Lab = require('lab');
@@ -14,7 +15,6 @@ var AuthServer = require('../lib/');
 
-var expect = Lab.expect;
-var before = Lab.before;
-var after = Lab.after;
-var describe = Lab.experiment;
-var it = Lab.test;
+var lab = exports.lab = Lab.script();
+var describe = lab.describe;
+var it = lab.it;
+var expect = Code.expect;
 
@@ -21,0 +21,0 @@

test/context.js

 // Load modules
 
+var Code = require('code');
 var Lab = require('lab');
@@ -14,7 +15,6 @@ var Context = require('../lib/context');
 
-var expect = Lab.expect;
-var before = Lab.before;
-var after = Lab.after;
-var describe = Lab.experiment;
-var it = Lab.test;
+var lab = exports.lab = Lab.script();
+var describe = lab.describe;
+var it = lab.it;
+var expect = Code.expect;
 
@@ -21,0 +21,0 @@

test/util.js

 // Load modules
 
+var Code = require('code');
 var Lab = require('lab');
@@ -14,7 +15,6 @@ var Util = require('../lib/util');
 
-var expect = Lab.expect;
-var before = Lab.before;
-var after = Lab.after;
-var describe = Lab.experiment;
-var it = Lab.test;
+var lab = exports.lab = Lab.script();
+var describe = lab.describe;
+var it = lab.it;
+var expect = Code.expect;
 
@@ -21,0 +21,0 @@

No alert changes

Improved metrics

Total package byte prevSize

36787

increased by0.16%

Number of lines in readme file

73

increased by1.39%

Worsened metrics

Dev dependency count

2

increased by100%

No dependency changes