Docusaurus v3 upgrade

[james-kaguru]

Description

This upgraded the project dependancies to match up to what is required in docusaurus v3

Related Issues

#212

Check List

• [X ] I have read the Contributing Guidelines

[james-kaguru]

@Eomm There are some issues causes by upgrading docusaurus to v3 noteable the formatting from some files in the fastify/fastify docs. The previous versions of the docs have formarting (notably ones identified by running npx docusaurus-mdx-checker). The updrage to v3 might have to include seperate docs for v2 and below and v3 and above. Not sure how to achieve this but I just wanted to raise a potential bottleneck. In addition orama plugin for docusaurua moved from @orama/plugin-docusaurus to @orama/plugin-docusaurus-v3 . I have temporarily commented out the plugin in docusaurus config because it brought up some issues but Im currently working to resolve it.

[Eomm]

the version* files should not be committed

[james-kaguru]

well noted

[Eomm]

There are some issues causes by upgrading docusaurus to v3 noteable the formatting from some files in the fastify/fastify docs

Some example?

I don't get if it breaks the website build or the linting.
In the latter case, no problem if we must upgrade the linting in this repo

[james-kaguru]

The docs from the previous versions have errors that have to be solved so that they can be run by docusaurus v3. I recently updated the docs in fastify/fastify to match the docusaurus requirements for v3 but since the docs prior to that were not correctly formated there is an error when i run npm start dev as shown below.

They are minor errors but Im not sure how we are going to update the previous docs and have the same version numbers

[Eomm]

They are minor errors but Im not sure how we are going to update the previous docs and have the same version numbers

Can we do some regexp magic like this?

website/scripts/process-releases.js

Lines 105 to 113 in e3e433a

	await fixHtmlTags(versionedFolder)
	await fixBrokenLinks(versionedFolder)
	// We can't run this fix on version >=3 because it would make the code blocks ugly
	const v1Docs = orderedVersions.find((v) => v.startsWith('v1.'))
	await fixCodeBlocks(join(versionedFolder, `version-${v1Docs}`))
	const v2Docs = orderedVersions.find((v) => v.startsWith('v2.'))
	await fixCodeBlocks(join(versionedFolder, `version-${v2Docs}`))

[james-kaguru]

Really smart approach...Lemmi try to come up with some magic to address the issue. Also Ive just remembered that to ensure the docs in fastify/fastify continue to be compatible with docusaurus v3 we also need to ensure it runs

npx docusaurus-mdx-checker

as a requirement during build time

[Eomm]

Need to check this PR - I will do it - I'm just doing to many things 🥲

[james-kaguru]

@Eomm I also got a bit held up but Im back on it to ensure we have passing build before you review it..there some hitches as I was trying to upgrade but will notify you incase I make a breakthrough

[Eomm]

Sorry @james-kaguru , I want to ship this PR very soon 😮‍💨

[Eomm]

FINALLY!

Thanks @james-kaguru