[Snyk] Fix for 3 vulnerabilities

[maniator]

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

Snyk changed the following file(s):

• docs/package.json

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.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Directory Traversal SNYK-JS-TAR-15032660	693
	Prototype Pollution SNYK-JS-LODASH-15053838	631
	Directory Traversal SNYK-JS-TAR-15127355	596

---

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:

🦉 Prototype Pollution
🦉 Directory Traversal

[Copilot]

Pull request overview

This is a Snyk-generated pull request that attempts to fix 3 security vulnerabilities (directory traversal and prototype pollution) by upgrading three dependencies in the docs package. However, the PR has critical issues that prevent it from being safely merged.

Changes:

• Upgraded lodash from ^4.17.15 to ^4.17.23 to fix prototype pollution vulnerability
• Upgraded next from ^9.5.0 to ^10.0.6 to address vulnerabilities in transitive dependencies
• Upgraded webpack from ^4.41.0 to ^5.0.0 to address directory traversal vulnerabilities in tar (a transitive dependency)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Upgrading webpack from version 4 to version 5 is a major breaking change that requires configuration updates in next.config.js. Specifically, the webpack 5 upgrade has deprecated the node.fs = 'empty' configuration option used in docs/next.config.js:96-98. This option should be replaced with resolve.fallback: { fs: false } for webpack 5 compatibility. Without this change, the build will fail or produce warnings.

Suggested change

	"webpack": "^5.0.0",
	"webpack": "^4.0.0",

[Copilot]

Upgrading Next.js from version 9.5 to 10.0 is a major version upgrade with breaking changes. Next.js 10 introduced changes to the build output, image optimization, and other features. While Next.js 10 does support webpack 5, it requires opting in via the future.webpack5: true configuration option in next.config.js. Without this configuration or without migrating to the default webpack 5 settings when they became default in later versions, the build may fail. Additionally, the PR description indicates that yarn.lock failed to update, which means dependencies may not be properly resolved.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.