-
Notifications
You must be signed in to change notification settings - Fork 404
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
build: add angular 17 support #2079
build: add angular 17 support #2079
Conversation
- extend allowed range of ng peer dependency to 18 - add an additional integration test for NG17 with updated dependencies and tests. - add additional test in all places the other tests run fixes ngxs#2078
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 8011d01. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 3 targetsSent with 💌 from NxCloud. |
For all I can gather about the error this seems to be related to old(ish) |
0589d93
to
550beb6
Compare
Code Climate has analyzed commit 8011d01 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 95.5% (0.5% change). View more on Code Climate. |
BundleMon (Integration Projects)Unchanged files (1)
No change in files bundle size Final result: ✅ View report in BundleMon website ➡️ |
Will this be reviewed soon? @kuncevic @Carniatto @markwhitfeld @poloagustin @joaqcid @arturovt @splincode |
Yes, my plan was to release today, but we have had a massive fibre break in
the area and I am without internet.
Hopefully tomorrow the release will be going out.
…On Wed, 22 Nov 2023 at 21:34, Mohamed Nabous ***@***.***> wrote:
Will this be reviewed soon?
@kuncevic <https://github.com/kuncevic> @Carniatto
<https://github.com/Carniatto> @markwhitfeld
<https://github.com/markwhitfeld> @poloagustin
<https://github.com/poloagustin> @joaqcid <https://github.com/joaqcid>
@arturovt <https://github.com/arturovt> @splincode
<https://github.com/splincode>
—
Reply to this email directly, view it on GitHub
<#2079 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAO3U2LALMVDZSR4GN63JO3YFZHV7AVCNFSM6AAAAAA7EQDWOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRTGQYDGMBSGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for you time! |
When does this get published on npm? @markwhitfeld |
Keen to add this to a new Angular 17 project |
Same here!! 😅 |
* build: add angular 17 support - extend allowed range of ng peer dependency to 18 - add an additional integration test for NG17 with updated dependencies and tests. - add additional test in all places the other tests run fixes #2078 * Update index.html to correct version number in the title * chore: regenerate yarn.lock * build: angular v17 support in websocket-plugin * chore: run CI on node 18 --------- Co-authored-by: Dmitriy Stepanenko <[email protected]> (cherry picked from commit 744e67c)
Seems like its good to go now. 3.8.2 is out |
any news about it? |
@danielbraghini as the timeline above shows this landed in 3.8.2 |
fixes #2078
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Updating an application using ngxs to Angular 17 fails, because all the packages declare
< 17
as the range for their peer dependencyIssue Number: #2078
What is the new behavior?
Updating to Angular 17 works, the range of allowed Angular versions has been adapted to
<18
. Compatibility has been checked with an additional integration test.Does this PR introduce a breaking change?
Other information
Note that I first started by updating the dependencies for Angular to 17 too – that however results in a compile Error for the Angular 15 integration test, which is why I opted to not follow up on that change. The adaptation of
custom-rxjs-subject
below stems from that though (Updating Angular implies updating Typescript and the compiler complains about not being able to assert the type of<T>
which made the explicit cast necessary.I left that particular change in the commit, as I think it causes no harm and helps for further updates.