@envelop/generic-auth
Advanced tools
Comparing version 0.0.2 to 0.1.0
{ | ||
"name": "@envelop/generic-auth", | ||
"version": "0.0.2", | ||
"version": "0.1.0", | ||
"sideEffects": false, | ||
@@ -15,8 +15,18 @@ "peerDependencies": { | ||
"license": "MIT", | ||
"main": "index.cjs.js", | ||
"module": "index.esm.js", | ||
"main": "index.js", | ||
"module": "index.mjs", | ||
"typings": "index.d.ts", | ||
"typescript": { | ||
"definition": "index.d.ts" | ||
}, | ||
"exports": { | ||
".": { | ||
"require": "./index.js", | ||
"import": "./index.mjs" | ||
}, | ||
"./*": { | ||
"require": "./*.js", | ||
"import": "./*.mjs" | ||
} | ||
} | ||
} |
@@ -61,3 +61,3 @@ ## `@envelop/generic-auth` | ||
// Here you can implement any custom to check if the user is valid and have access to the server. | ||
// This method is being triggered in different flows, besed on the mode you chose to implement. | ||
// This method is being triggered in different flows, based on the mode you chose to implement. | ||
@@ -64,0 +64,0 @@ // If you are using the `protect-auth-directive` mode, you'll also get 2 additional parameters: the resolver parameters as object and the DirectiveNode of the auth directive. |
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
28467
1