Some help needed I upgraded a product to Angular 18.0.3 and there is a peer dependency

[lkovari]

Hi,

I would appreciate if you help me.
When I would update from 17 to 18 an angular project I faced with the following:

npm error Could not resolve dependency:
npm error peer @angular/common@"^17.0.0" from @danielmoncada/angular-datetime-picker@17.0.0
npm error node_modules/@danielmoncada/angular-datetime-picker
npm error @danielmoncada/angular-datetime-picker@"^17.0.0" from the root project

Could you please notify me when you updated your package?

[T4toh]

The package still works on 18, you can force the update (I did that last week). There is a PR with the update here.

[lkovari]

Hi I think the force is not the best solution. Because if you delete node_modules and run npm install you need to use again the —force which not recommended. Can see in the following article about what did the —force https://weekendprojects.dev/posts/how-to-use-npm-legacy-peer-deps-command/#should-i-use-the---force-flag-or---legacy-peer-deps-flag L. Kővári

…

On Thu, 13 Jun 2024 at 14:04, Ignacio Martín Arano ***@***.***> wrote: The package still works on 18, you can force the update (I did that last week). There is a PR with the update here <#199>. — Reply to this email directly, view it on GitHub <#201 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ6ZEADYUX4OO45Q7MM3HLZHGDDVAVCNFSM6AAAAABJHDVEFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRVGQ3DCNJWGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[T4toh]

You're right, but I never said that it was a solution, just possible. If you need to update (like in my case) you can, that's all.

[LesanuNicolas]

@danielmoncada can you please look into this pull request posted by NetWin: #199 , would solve our issues :)

[NetWin]

FYI i published the library with angular 18 support.

See: #199 (comment)

[danielmoncada]

@LesanuNicolas published