-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: auth0/node-jsonwebtoken
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.2.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: auth0/node-jsonwebtoken
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.3.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 7 files changed
- 8 contributors
Commits on Dec 7, 2016
-
Configuration menu - View commit details
-
Copy full SHA for 05d9978 - Browse repository at this point
Copy the full SHA 05d9978View commit details
Commits on Feb 3, 2017
-
rauchg/ms.js changed to zeit/ms (#303)
* rauchg/ms.js changed to zeit/ms * Update README.md
Configuration menu - View commit details
-
Copy full SHA for 35d8415 - Browse repository at this point
Copy the full SHA 35d8415View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1b6ec8d - Browse repository at this point
Copy the full SHA 1b6ec8dView commit details -
* Fixed a simple typo The example didn't work because of a missing comma. * Fixed a simple typo The example didn't work because of a missing comma.
Configuration menu - View commit details
-
Copy full SHA for a542403 - Browse repository at this point
Copy the full SHA a542403View commit details
Commits on Feb 9, 2017
-
Raise jws.decode error to avoid confusion with "invalid token" error (#…
…294) * Corrected indistinguishable error messages jws.decode() never throws an error. At least, in its current version. However, if it were to throw an exception, the diagnostics would be indistinguishable from a soft failure to decode a token. I had an extra trailing space on my JWT and it took me some additional debugging work to trace the actual root cause because the error message was not distinct. * Allowed an exception from inside of jws.decode to be handled by the caller. Currently, jws.decode never throws an exception. The change is made per discsussion in the original PR * Added a test case and proper forwarding of the possible exception thrown from jws.decode * Typo correction
Configuration menu - View commit details
-
Copy full SHA for 7f68fe0 - Browse repository at this point
Copy the full SHA 7f68fe0View commit details
Commits on Feb 10, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 8fdc150 - Browse repository at this point
Copy the full SHA 8fdc150View commit details
Commits on Feb 13, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 1b0592e - Browse repository at this point
Copy the full SHA 1b0592eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 94007b3 - Browse repository at this point
Copy the full SHA 94007b3View commit details
There are no files selected for viewing