[Snyk] Security upgrade parcel from 1.12.4 to 2.0.0

[prodsecmachine]

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

Snyk changed the following file(s):

• package.json

---

This major version upgrade from Parcel 1 to 2 is a complete rewrite and introduces significant breaking changes. It requires updates to dependencies, configuration, and potentially source code. The npm package has been renamed, and build configurations have moved from CLI flags to package.json.

Highlights:

• Update package name: The npm package must be changed from parcel-bundler to parcel.
• Enable transpilation: Parcel 2 does not transpile modern JavaScript by default. You must add a browserslist field to your package.json to configure target browsers and enable transpilation.

Source: Parcel documentation
Recommendation: Follow the official Parcel 1 to 2 migration guide carefully. Update the package name, configure browserslist in package.json, and verify build outputs and application behavior before merging.

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

---

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-JSYAML-13961110	631

---

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

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[shainaraskas]

hey @elastic/docs-engineering, cna you look at this security upgrade?

[reakaleek]

#3267 (comment)

[prodsecmachine]

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

• SNYK-JS-JSYAML-13961110

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.

---

This action was performed automatically by Snyk.