We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
My build began to fail just now with a surprising error relating to react-native:
[Container] 2022/03/31 23:15:26 Running command npm ci -- 43 | npm WARN ERESOLVE overriding peer dependency 44 | npm WARN While resolving: use-subscription@1.6.0 45 | npm WARN Found: react@17.0.2 46 | npm WARN node_modules/react 47 | npm WARN peer react@"17.0.2" from react-native@0.68.0 48 | npm WARN node_modules/react-native 49 | npm WARN peer react-native@"*" from @react-native-community/cli@7.0.3 50 | npm WARN node_modules/@react-native-community/cli 51 | npm WARN 1 more (react-native-get-random-values) 52 | npm WARN 1 more (react-shallow-renderer) 53 | npm WARN 54 | npm WARN Could not resolve dependency: 55 | npm WARN peer react@"^18.0.0" from use-subscription@1.6.0 56 | npm WARN node_modules/use-subscription 57 | npm WARN use-subscription@"^1.0.0" from react-native@0.68.0 58 | npm WARN node_modules/react-native 59 | npm WARN 60 | npm WARN Conflicting peer dependency: react@18.0.0 61 | npm WARN node_modules/react 62 | npm WARN peer react@"^18.0.0" from use-subscription@1.6.0 63 | npm WARN node_modules/use-subscription 64 | npm WARN use-subscription@"^1.0.0" from react-native@0.68.0 65 | npm WARN node_modules/react-native
Created this issue to track the bug and help find a solution.
The text was updated successfully, but these errors were encountered:
Migrating to (ember-cognito-identity)[https://github.com/fabscale/ember-cognito-identity] for now
Sorry, something went wrong.
No branches or pull requests
My build began to fail just now with a surprising error relating to react-native:
Created this issue to track the bug and help find a solution.
The text was updated successfully, but these errors were encountered: