Conversation
aks96
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
On trying to deploy express-oidc on cloudfare workers getting error Uncaught TypeError: Joi.binary is not a function
at null.
Scope
This fix allows the SDK to initialize in cloudfare workers. But full support would require a larger migratiom (under development)
Changes
To support the joi.binary added the polyfill for fallback where it is not available.
The fix uses joi.binary() in node.js and falls back to the custom validator in environments like cloudfare workers where joi.binary is not avaialble.
Tests