[Docusaurus] Plugin not installable on Docusaurus 3.7.0

[timothymamo]

Describe the bug

Trying to install the @orama/plugin-docusaurus-v3 plugin with version 3.1.0 or greater on Docusaurus with version 3.7.0 errors out with the following:

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @docusaurus/[email protected]
npm error node_modules/@docusaurus/plugin-content-docs
npm error   @docusaurus/plugin-content-docs@"^3.7.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @docusaurus/plugin-content-docs@"~3.6.0" from @orama/[email protected]
npm error node_modules/@orama/plugin-docusaurus-v3
npm error   @orama/plugin-docusaurus-v3@"^3.1.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error [redacted]
npm error A complete log of this run can be found in: [redacted]

It seems that currently the plugin only supports patched versions of Docusaurus 3.6.x as shown in the packag.json file (Line 42 and Lines 50-52.

To Reproduce

1. Create a Docusaurus website with version 3.7.0
2. Add "@orama/plugin-docusaurus-v3" to the plugins array in docusaurus.config.ts.
3. Run npm install
4. npm install errors out

Expected behavior

I expect to be able to install the latest version of @orama/plugin-docusaurus-v3 on Docusaurus with version 3.7.0 and greater minor versions (Docusaurus respects Semantic Versioning)

Environment Info

Orama: 3.1.0 and above
Docusaurus: 3.7.0

Affected areas

Initialization

[timothymamo]

Happy to create a PR with a fix, unless there is a specific reason this was done.

[micheleriva]

@raiindev can you please look at this?

[raiindev]

Sure, I'll take a look ASAP.

[jerdog]

Can confirm, having the same issues

[micheleriva]

should be fixed in v3.1.15, thanks for you patience and sorry for the delay 🙏