-
Notifications
You must be signed in to change notification settings - Fork 81
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
Angular 13 compatibility #186
Comments
I Created a fork. |
Thank you Henk Kelder so much!, at July 2022, we have to upgrade to angular 13, within an ASP NET web app, this is a lot of help! |
You are welcome. Had the same problem |
Can you please update your fork to support angular 14? |
Hi Andrey,
It supports Angular 14 already as far as I know.
I use it in a Angular 14 project
From: Andrey Bykiev ***@***.***>
Sent: vrijdag 12 augustus 2022 08:18
To: HNeukermans/ng2-signalr ***@***.***>
Cc: Henk Kelder ***@***.***>; Comment ***@***.***>
Subject: Re: [HNeukermans/ng2-signalr] Angular 13 compatibility (Issue #186)
I Created a fork. ***@***.***/ng2-signalr
Can you please update your fork to support angular 14?
—
Reply to this email directly, view it on GitHub <#186 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACFZ6NW5IFF56E6AYRXKKS3VYXUCVANCNFSM5IVWBPNA> .
You are receiving this because you commented. <https://github.com/notifications/beacon/ACFZ6NTL2GL5XEYUIRMABYDVYXUCVA5CNFSM5IVWBPNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJBEVXFY.gif> Message ID: ***@***.*** ***@***.***> >
|
Thank you for quick response, I'll try to use it |
Have an angular 12 project and ng2-signalr is not working so I should replace ng2-signalr with @henkkelder/ng2-signalr?...can you provide me a sample code @henkkelder |
There are no changes except making it work for newer Angular versions
So the examples from HNeukermans are still valid.
From: Supi2810 ***@***.***>
Sent: donderdag 2 februari 2023 07:35
To: HNeukermans/ng2-signalr ***@***.***>
Cc: Henk Kelder ***@***.***>; Mention ***@***.***>
Subject: Re: [HNeukermans/ng2-signalr] Angular 13 compatibility (Issue #186)
Have an angular 12 project and ng2-signalr is not working so I should replace ng2-signalr with @henkkelder/ng2-signalr?...can you provide me a sample code @henkkelder <https://github.com/henkkelder>
—
Reply to this email directly, view it on GitHub <#186 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACFZ6NQ5577NV3556YCOLI3WVNIQPANCNFSM5IVWBPNA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/ACFZ6NSQNFQM6DSD3FFPVRDWVNIQPA5CNFSM5IVWBPNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOKQ6BE3A.gif> Message ID: ***@***.*** ***@***.***> >
|
Hi @henkkelder , |
I am using it as it is with Angular17. |
Ok, I will give it a try. |
When installing Angular 13 with ng update, I got the message:
Package "ng2-signalr" has an incompatible peer dependency to "@angular/core" (requires "^10.0.0" (extended), would install "13.0.2").
Is it possible to update the package to be comaptible with Angular 13?
The text was updated successfully, but these errors were encountered: