[Snyk] Security upgrade esbuild from 0.21.5 to 0.28.1

[pushkala-datastax]

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

Snyk changed the following file(s):

• src/frontend/package.json
• src/frontend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Resources Downloaded over Insecure Protocol SNYK-JS-ESBUILD-17750822	746

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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.

[pushkala-datastax]

This upgrade spans several minor versions and introduces significant behavioral changes that require verification.

Key Changes:

• --packages=external is now default (v0.22.0): When the platform is set to node, dependencies from node_modules will now be treated as external and will not be bundled by default. This was a common point of confusion and is now the default behavior. If you rely on esbuild to bundle your node dependencies, you must explicitly add --packages=bundle to your build command.

• esbuild-wasm requires top-level await (v0.23.0): The WebAssembly-based package esbuild-wasm now requires an environment that supports top-level await. This is a breaking change for users of the wasm package in older browsers or environments that lack this feature.

• Minimum Node.js version increased to 18 (v0.24.0): The minimum required Node.js version for using esbuild's JavaScript API was increased from 12 to 18.

Recommendation:
Review your build scripts to ensure they are compatible with the new default behavior of externalizing packages. If you bundle for a node environment, you may need to add --packages=bundle. If you use esbuild-wasm, confirm your target environments support top-level await. Verify that your development and CI environments are using at least Node.js v18.

Source: esbuild 2024 Changelog

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