capacitor/preferences for capacitor/core 5 not availeble

[vovagorodok]

capacitor/[email protected] depends on capacitor/core@"^4.0.0 capacitor/[email protected] depends on capacitor/core@"^6.0.0

There no capacitor/preferences depends on capacitor/core@"^5.0.0

Trying to migrate lichobile project from Capacitor 4 to 5:

:~/Projects/private/lichobile$ npm install --force
npm WARN using --force Recommended protections disabled.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @capacitor/[email protected]
npm WARN Found: @capacitor/[email protected]
npm WARN node_modules/@capacitor/core
npm WARN   @capacitor/core@"^5.0.0" from the root project
npm WARN   20 more (@capacitor/android, @capacitor/app, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @capacitor/core@"next" from @capacitor/[email protected]
npm WARN node_modules/@capacitor/preferences
npm WARN   @capacitor/preferences@"^5.0.0" from the root project
npm WARN 
npm WARN Conflicting peer dependency: @capacitor/[email protected]
npm WARN node_modules/@capacitor/core
npm WARN   peer @capacitor/core@"next" from @capacitor/[email protected]
npm WARN   node_modules/@capacitor/preferences
npm WARN     @capacitor/preferences@"^5.0.0" from the root project

[Ionitron]

This issue needs more information before it can be addressed. In particular, the reporter needs to provide a minimal sample app that demonstrates the issue. If no sample app is provided within 15 days, the issue will be closed.

Please see the Contributing Guide for how to create a Sample App.

Thanks! Ionitron 💙

[vovagorodok]

I mean that only capacitor/preferences ver 4 and 6 is available. No capacitor/core 5 required from capacitor/core 5

[jcesarmobile]

This was a problem in @capacitor/[email protected], but was fixed in @capacitor/[email protected]

[ionitron-bot[bot]]

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of the plugin, please create a new issue and ensure the template is fully filled out.