[Snyk] Security upgrade webpack from 4.46.0 to 5.0.0

[abdulrahman305]

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

Snyk changed the following file(s):

• examples/sapper/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
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8187303	170
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8172694	131

---

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.

Description by Korbit AI

What change is being made?

Upgrade the webpack dependency from version 4.7.0 to 5.0.0 in the examples/sapper/package.json file.

Why are these changes being made?

This upgrade addresses security vulnerabilities present in the older version of webpack and ensures compatibility with the latest features and improvements offered in version 5.0.0. The change is necessary to maintain the security and performance of the project.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
vercel	❌ Failed (Inspect)			Oct 15, 2024 5:03pm
vercel-cli-dj12	❌ Failed (Inspect)			Oct 15, 2024 5:03pm
vercel-remix	❌ Failed (Inspect)			Oct 15, 2024 5:03pm

[korbit-ai]

👋 I'm here to help you review your pull request. When you're ready for me to perform a review, you can comment anywhere on this pull request with this command: /korbit-review.

As a reminder, here are some helpful tips on how we can collaborate together:

• To have me re-scan your pull request, simply re-invoke the /korbit-review command in a new comment.
• You can interact with me by tagging @korbit-ai in any conversation in your pull requests.
• On any comment I make on your code, please leave a 👍 if it is helpful and a 👎 if it is unhelpful. This will help me learn and improve as we work together
• Lastly, to learn more, check out our Docs.