[Snyk] Security upgrade @docusaurus/core from 2.0.0-alpha.40 to 2.0.1

[ayusuf-mq]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• website/package.json
• website/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	595

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[ayusuf-mq]

This is a significant upgrade from a very old alpha version to a stable release. Docusaurus 2.0 underwent numerous breaking changes during its alpha and beta phases before stabilization. Key changes occurred in file structure, plugin APIs, and theme components. For example, source components were moved to a /src directory.

Highlights:

• File Structure Change: Custom source components (pages, themes) must be moved from the root into a newly created website/src directory.
• API and Configuration: Many APIs and configuration options were finalized between the alpha versions and the stable 2.0 release, potentially breaking existing setups.

Source: Docusaurus documentation
Recommendation: A full migration is required. Follow the official Docusaurus v2 documentation and migration guides, paying close attention to file paths and configuration updates. Manually validate all site functionality after the upgrade.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.