Chore/angular v19 migration #7
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Angular v20 is now officially released and in production. To prepare for a full upgrade, i first updated the project from Angular v18 to v19. This intermediate step allows for proper validation of all functionalities before completing the final upgrade to v20 in a separate branch.
I followed the first part of the official Angular upgrade guide: Angular Update Guide (v18 to v20).
During this upgrade, i addressed the deprecation of
HttpClientModule
by replacing it with the newprovideHttpClient()
function, as recommended in the Angular documentation: HttpClientModule API Reference.Additionally, i encountered an issue with the Tauri build. Although the build process completed successfully, running the app resulted in the error: "Asset 'index.html' not found". Upon investigation, i discovered that Angular now outputs build artifacts to
/dist/browser
instead of just/dist
. Updating thedistDir
path intauri.conf.json
resolved the issue.I also made some changes to the workflows build process, updating the dependencies.
Type of change
Checklist: