Uppy Angular 17

[stephanevallejo]

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

Hello,

When will uppy angular be compatible with angular 17?

Solution

Hello,

When will uppy angular be compatible with angular 17?

Alternatives

Hello,

When will uppy angular be compatible with angular 17?

[gongAll]

I believe there is some under the hood code still being refactored, according to this comment by @aduh95. This will probably have to wait. Still, an ETA would be greatly appreciate, in order for devs to be able to make more informed decisions.

[aduh95]

It should be part of the Uppy 4.x release, which we aim to do in Q1 2024. We won't be able to commit to any specific date, as we are in the process of refactoring all Uppy plugins to TypeScript, and it is simply hard to predict how long it's going to take exactly.
Working on Angular in the mean time would be fighting a losing batlle, as Angular is already written in TS but the types in the plugins it consumes are evolving rapidly as the refactor progresses.

[Rahul-codoffer]

Please Upgrade to Angular 17.x

[aduh95]

It's certainly still on the roadmap, as you can see I've even opened a PR yesterday upgrading the library. The goal would be to release that along with Uppy 4.x which hopefully will be released (at least as beta) in the next few weeks.

Could you give more details on how pressing this is for you? Does the current @uppy/angular release does not work with Angular 17.x?

[Rahul-codoffer]

@aduh95 no right now i'm unable to install the uppy in my angular 17 project .

Found: @angular/common@17.3.0
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"^17.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^16.2.0" from @uppy/angular@0.6.1
npm ERR! node_modules/@uppy/angular
npm ERR! @uppy/angular@"*" from the root project

[Murderlon]

Can't we just do this, wouldn't be a breaking change:

"peerDependencies": {
- "@angular/common": "^16.2.0",
- "@angular/core": "^16.2.0",
+ "@angular/common": "^16.2.0 || ^17.0.0",
+ "@angular/core": "^16.2.0 || ^17.0.0",

Even if we upgrade to 17, it would be unnecessary to make this a breaking change to only support 17 if it runs fine on both.

[aduh95]

We've just release @uppy/angular v0.7.0-beta.1, which is built for Angular 17. Don't hesitate to give it a try and report any issue you encounter.

[TiKevin83]

We've just release @uppy/angular v0.7.0-beta.1, which is built for Angular 17. Don't hesitate to give it a try and report any issue you encounter.

@aduh95 the peer dependencies in v0.7.0-beta.1 still restrict angular to ^16.2.0 - any suggestions or does another release need to be made fixing that for us to use the update with v17?

[aduh95]

@TiKevin83 Thanks for pointing it out. A new beta release is out with the correct peer dependency info.