-
Notifications
You must be signed in to change notification settings - Fork 56
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
{ | ||
"name": "passport-localapikey", | ||
"version": "0.0.3", | ||
"version": "0.0.4", | ||
"description": "Local api key authentication strategy for Passport.", | ||
"author": { "name": "Sudhakar Mani", "email": "[email protected]", "url": "http://www.sudhakarmani.com/" }, | ||
"repository": { | ||
|
@@ -26,5 +26,5 @@ | |
"type": "MIT", | ||
"url": "http://www.opensource.org/licenses/MIT" | ||
} ], | ||
"keywords": ["passport", "local apikey", "auth", "authn", "authentication"] | ||
"keywords": ["passport", "passport apikey","local apikey", "auth", "authn", "authentication"] | ||
} |
d1246cd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
latest on npm is 0.0.3 still?
d1246cd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For those who are wondering, the 0.0.4 version has been published to npm under a new name:
https://www.npmjs.com/package/passport-localapikey-update
Hopefully the original owner will continue to maintain this project, or give access to others so it can live on (please!)
d1246cd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dylants. Spent a good amount of time chasing my tail wondering why the npm project was not the same as latest code on repo. Now it makes sense. Thanks for the link and explanation. All works perfectly now.