[Snyk] Security upgrade next from 10.2.0 to 12.0.8

[ayusuf-mq]

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

Snyk changed the following file(s):

• package.json
• 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
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	590

---

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 major version upgrade from Next.js 10 to 12 introduces significant breaking changes, including a new Rust-based compiler, the removal of Webpack 4 support, and updated Node.js requirements. Code modifications are required to ensure compatibility.

Highlights:

• Webpack 4 Support Removed: Webpack 5 is now mandatory. Custom webpack configurations must be updated.
• Node.js & React Versions: The minimum Node.js version is now 12.22.0, and the minimum React version is 17.0.2.
• next/image Wrapper Change: The component now uses a <span> wrapper instead of a <div>, which may break specific CSS selectors.

Source: Next.js documentation
Recommendation: First, ensure your environment meets the new Node.js version requirement. Then, migrate any custom Webpack 4 configurations to Webpack 5. Finally, audit CSS targeting next/image components before merging.

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