[bug report] library is not compatible with Angular v16

[pawelofieldly]

• My issue title starts with [bug report]
• I have read the README, especially the 'classic blunders' section, and the dragula docs.
• I have searched through the ng2-dragula issues for related problems, including closed issues.
• I have browsed through the issues labeled "future reference" for problems that have been solved before or have a known workaround.
• I am using the latest version of ng2-dragula.

Dragula is not compatible with Angular 16

Steps to reproduce the behavior:

There are two scenarios:

I. You want to install dragula in ng16 project

1. npm install --save ng2-dragula
2. See error: unable to resolve dependency tree

II. You want to migrate current project to ng16

1. use ng update to update ng15 to ng16
2. See error when ng serve has been run: Error: node_modules/ng2-dragula/dist/components/dragula.module.d.ts:3:23 - error TS2314: Generic type 'ModuleWithProviders<T>' requires 1 type argument(s). static forRoot(): ModuleWithProviders;

[reda-alaoui]

I made it work without any issue.

[ohsk23]

Hi, I have a similar problem here.
ng2-dragula has dependency conflict with @angular/[email protected]

❯ npm i [email protected]                                                      took 5s
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [PROJ_NAME]@1.16.10
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"16.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"15.2.9" from @angular/[email protected]
npm ERR! node_modules/@angular/animations
npm ERR!   peer @angular/animations@"^15.0.0" from [email protected]
npm ERR!   node_modules/ng2-dragula
npm ERR!     ng2-dragula@"4.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Any updates for angular v16?

[mrkava]

Similar problem after update to Angular 16. Do you plan to support Angular 16?

[Petronio1982]

PS C:\Users\attim\Documents\virtualroom3d> npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/animations
npm ERR! @angular/animations@"^16.0.3" from the root project
npm ERR! peer @angular/animations@"^16.0.0 || ^17.0.0" from @angular/[email protected]
npm ERR! node_modules/@angular/material
npm ERR! @angular/material@"^16.0.2" from the root project
npm ERR! peer @angular/material@"16.0.2" from @angular/[email protected]
npm ERR! node_modules/@angular/material-moment-adapter
npm ERR! @angular/material-moment-adapter@"^16.0.2" from the root project
npm ERR! 1 more (@angular/platform-browser)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/animations@"^15.0.0" from [email protected]
npm ERR! node_modules/ng2-dragula
npm ERR! ng2-dragula@"^4.0.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/animations
npm ERR! peer @angular/animations@"^15.0.0" from [email protected]
npm ERR! node_modules/ng2-dragula
npm ERR! ng2-dragula@"^4.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

[onaluf]

I've got the same exact issue. If installed with --force everything works correctly so fixing this is probably as simple as updating the package.json to be a bit more flexible as to which version of angular it requires.

[pjc2007]

Would also like to use with Angular 16.

[pawelofieldly]

@reda-alaoui do you consider updating compatibility to ng16? I would like not to use npm install --force

[neodescis]

Why is this issue closed? The current version of the project specifically lists ^15.0.0 in its peer dependencies.

[ghbob]

@valorkin @SvetlanaMuravlova Could you kindly give us some information if there are plans to make this package support Angular 16? Thank you!
Someone prepared a PR as well: #1092