Latest version does not support Angular 15 which results in dependency conflicts for ngx-flow when updating to Angular 15.

[sukantoghsh]

What would be the best approach to solve this ?

[Quentigus]

I need Angular 15 support too 👍

EDIT : NPM overrides work as temporary workaround :

"overrides": {
    "@flowjs/ngx-flow": {
        "@angular/animations": "15",
        "@angular/common": "15",
        "@angular/compiler": "15",
        "@angular/core": "15",
        "@angular/forms": "15",
        "@angular/platform-browser": "15",
        "@angular/platform-browser-dynamic": "15",
        "@angular/router": "15"
    }
}

[evilaliv3]

@sukantoghsh / @Quentigus : which is your experience with Angular15? Did you encounter any incompatibility?

@MartinNuc : which are you evaluations?

[evilaliv3]

Hello @MartinNuc, i just wanted to reming you about this ticket in case you missed to see my comment.

@sukantoghsh @Quentigus: do you confirm that all is working perfectly on the current Angular?

[Quentigus]

I haven't tested everything, no. I was waiting to see if official support would be offered.

[evilaliv3]

Thank you.

Did you encounter any error testing it?

[StavNoyAkur8]

Our project has been working with Angular 15 and ngx-flow since January using legacy-peer-deps. No issues.
Thanks @Quentigus for the tip on NPM overrides

[rmhubley]

What about Angular 16? I am getting this error:

Error: src/app/workbench/workbench.module.ts:53:5 - error NG6002: 'NgxFlowModule' does not appear to be an NgModule class.

53     NgxFlowModule,
       ~~~~~~~~~~~~~

  node_modules/@flowjs/ngx-flow/lib/ngx-flow.module.d.ts:2:22
    2 export declare class NgxFlowModule {
                           ~~~~~~~~~~~~~
    This likely means that the library (@flowjs/ngx-flow) which declares NgxFlowModule is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

Turns out the missing magic was:
update to ngx-flow 0.6.0 and employ the suggestions from another issue (#81):

npm i --save-dev @types/flowjs__flow.js

# Then changed to this import form rather than what the docs say to use
import * as Flow from '@flowjs/flow.js';

[Quentigus]

Is it possible de release a new version with a more permissive peerDependencies ?

For exemple :

"peerDependencies": {
    "@angular/common": ">=14.0.0",
    "@angular/core": ">=14.0.0",
    "@flowjs/flow.js": "^2.13.0"
},

Actual values ("^14.0.0-") seems to be invalid semver values

[CosmoFruit]

fixed #105

[CosmoFruit]

@MartinNuc @AidasK @evilaliv3 Hi, can you publish 0.7.0 release?

[Quentigus]

According to the semver syntax documentation, I think that the syntax is not valid. In my opinion, the "-" should be removed.

"peerDependencies": {
    "@angular/common": "^14.0.0-", // here
    "@angular/core": "^14.0.0-", //here
    "@angular/common": "^16.0.0-", // here 
    "@angular/core": "^16.0.0-", // and here
    "@flowjs/flow.js": "^2.13.0"
},

[evilaliv3]

Thank you for the reminder.

Are you all confident that the version 0.7.0 is working properly?
Can someone confirm this and eventually ensure that the dependencies included in 0.7.0 are up to date and tests working?

I'm not following the project so much but i may try to do the publishing if you could confirm this.

Is there anyone that would like to support the maintainance of the project?

[CosmoFruit]

Is there anyone that would like to support the maintainance of the project?

@evilaliv3 i can support the maintainance of the project, bcz we use it in our enterprise, and we need ability update dependencies

[evilaliv3]

Thank you @CosmoFruit

Would you like to make a pull request in relation to the up to date changes that you consider are needed?
Viewing some contributions would help us all evaluate who could move on with the maintainance of the project on the long run.