[Snyk] Fix for 1 vulnerabilities

[RealTschoegl]

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

Snyk changed the following file(s):

• 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
	Allocation of Resources Without Limits or Throttling SNYK-JS-SERIALIZEJAVASCRIPT-15809196	696

---

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:

🦉 Allocation of Resources Without Limits or Throttling

Note

Fix vulnerability by upgrading webpack to v5 and copy-webpack-plugin to v14

Updates webpack from ^4.30.0 to ^5.1.1 and copy-webpack-plugin from ^5.0.3 to ^14.0.0 in package.json to address a Snyk-reported vulnerability. Risk: both are major version bumps and may introduce breaking changes to the build configuration.

^{Macroscope summarized 4047492.}

[macroscopeapp]

Approvability

Verdict: Approved

This Snyk security fix updates two devDependencies (webpack and copy-webpack-plugin) to address vulnerabilities. Since these are build-time tools that don't affect the library's runtime behavior, the changes are low-risk and straightforward.

^{You can customize Macroscope's approvability policy. Learn more.}