Support for angular19

[PillowPillow]

Initial checklist

• I understand this is a feature request and questions should be posted in the Community Forum
• I searched issues and couldn’t find anything (or linked relevant results below)

Problem

The current version of @uppy/angular use angular 18 as a dependency and cause issue during npm update.

Solution

Update the library to use the angular 19 version.

Alternatives

use dependency override in package.jsdon

[Murderlon]

We currently have no Angular expertise on the team. Do you think we can just include it in the semver range, or are things incompatible with with older versions?

[PillowPillow]

I m using your v18 build with angular v19 (by overriding the package.json version), so your code seems to be compatible. However you should migrate the version using the ng cli with the "ng update" command.
It will replace for you the breaking parts.

[Murderlon]

Would you be willing to contribute a PR for this?

[AravindMakam]

I have upgraded the uppy angular package to v19. I would be happy to contribute a PR.

[Murderlon]

Would be great if you can make a PR for it :)

[AravindMakam]

Would be great if you can make a PR for it :)

I do not have access to check in my code..would you be providing access or whats the process for it? Can we connect?

[bdirito]

@AravindMakam

You will want to create a personal fork of uppy

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks

Because it is your fork, you have whatever permissions you want and can push whatever changes you need.

Then, on the main (transloadit) version of uppy you will create a PR from your new version to the main version.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork

That will then show up as PR from which uppy maintainers can review, approve and then merge your proposed changes from your branch to the main (transloadit) branch.