-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[expo] Unable to resolve "@openauthjs/openauth/client" #113
Comments
apparently I'm not the only one. a user found a workaround, which is to copy the client in a local context, along with the files it depends on:
https://gist.github.com/xinha-sh/723fae6bad78a303bbaeeb2b41634c76 |
any improvements on this?? i dont like the copy/paste approach |
Forking the client is an approach hard to maintain. |
i managed to make it work using AuthSession by manually providing the urls for discovery . const discovery = {
authorizationEndpoint: "your.auth.domain/authorize",
tokenEndpoint: "your.auth.domain/token"
}
const [ request, response, promptAsync] = useAuthRequest(
{
clientId:"your-mobile-app",
redirectUri: makeRedirectUri() // from expo-auth-session
},
discovery
) Have you try this option on metrobundler ? |
reproduction workflow
npx create-expo-app@latest
for info, the tsconfig of the expo app will be https://github.com/expo/expo/blob/main/packages/expo/tsconfig.base.json
You will get the error
The type error disappear, but now I get an error at build time
The text was updated successfully, but these errors were encountered: