[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

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	828

---

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

[prodsecmachine]

This major version upgrade from Parcel 1 to 2 is a complete rewrite and introduces significant breaking changes. The npm package has been renamed, configuration has been overhauled, and plugin APIs are not compatible. Manual intervention is required to migrate.

Highlights:

• Package Name Change: The npm package parcel-bundler must be replaced with parcel.
• Configuration: Parcel 2 introduces a .parcelrc file for configuration, replacing implicit setups. JavaScript is no longer transpiled by default; you must define a browserslist in package.json.

Source: Parcel documentation
Recommendation: Follow the official Parcel 1 to 2 migration guide, update package names, create a .parcelrc configuration, and test thoroughly before merging.

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

[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.}