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
Background https://stackoverflow.com/questions/75452137/unable-to-build-with-angular-12-13
Problem It seems that there are two problems happening when someone is using stream-chat-angular with Angular@12 (or 13):
Workaround For Angular 12 (tested with node v16): npm install stream-chat-angular stream-chat @ngx-translate/core [email protected] ngx-popperjs@12 --legacy-peer-deps
npm install stream-chat-angular stream-chat @ngx-translate/core [email protected] ngx-popperjs@12 --legacy-peer-deps
For Angular 13 (tested with node v16): npm install stream-chat-angular stream-chat @ngx-translate/core [email protected] ngx-popperjs@13 --legacy-peer-deps
npm install stream-chat-angular stream-chat @ngx-translate/core [email protected] ngx-popperjs@13 --legacy-peer-deps
Proper solution
angular-mentions
ngx-popperjs
1.4.0
npm
The text was updated successfully, but these errors were encountered:
Fixed in version 5 (in beta)
Sorry, something went wrong.
No branches or pull requests
Background
https://stackoverflow.com/questions/75452137/unable-to-build-with-angular-12-13
Problem
It seems that there are two problems happening when someone is using stream-chat-angular with Angular@12 (or 13):
Workaround
For Angular 12 (tested with node v16):
npm install stream-chat-angular stream-chat @ngx-translate/core [email protected] ngx-popperjs@12 --legacy-peer-deps
For Angular 13 (tested with node v16):
npm install stream-chat-angular stream-chat @ngx-translate/core [email protected] ngx-popperjs@13 --legacy-peer-deps
Proper solution
angular-mentions
andngx-popperjs
peer dependenciesangular-mentions
version to1.4.0
npm
bugThe text was updated successfully, but these errors were encountered: