build(deps): bump the npm_and_yarn group across 4 directories with 33 updates

[dependabot]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

Important

Bump esbuild, uglify-js, send, and serve-static dependencies across multiple package.json files.

• Dependencies:
  • Bump esbuild from ^0.14.27 to ^0.25.0 in browser-sync-client/package.json and browser-sync-ui/package.json.
  • Bump uglify-js from ^2.6.1 to ^3.19.3 in browser-sync-ui/package.json.
  • Bump send from 0.16.2 to 1.2.0 and serve-static from 1.13.2 to 1.16.2 in browser-sync/package.json.

^{This description was created by for 89cc021. You can customize this summary. It will automatically update as commits are pushed.}

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 89cc021

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 89cc021 in 1 minute and 8 seconds. Click for details.

• Reviewed 51 lines of code in 3 files
• Skipped 4 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. packages/browser-sync-client/package.json:42

• Draft comment:
  esbuild bumped to ^0.25.0. Verify build config compatibility with potential API changes.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. packages/browser-sync-ui/package.json:44

• Draft comment:
  Updated esbuild to ^0.25.0. Confirm that any esbuild task options remain valid.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. packages/browser-sync-ui/package.json:55

• Draft comment:
  uglify-js updated to ^3.19.3; check for breaking changes in minification.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency update, specifically the 'uglify-js' library. The comment suggests checking for breaking changes in minification, which falls under the category of dependency changes. According to the rules, I should not comment on pure dependency changes or library versions that I don't recognize. Therefore, this comment should be removed.

4. packages/browser-sync/package.json:60

• Draft comment:
  send bumped to 1.2.0. Ensure middleware usage aligns with new API semantics.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is related to a dependency version change, which is not allowed according to the rules. It asks to ensure middleware usage aligns with new API semantics, which is a form of asking the author to ensure something, which is also not allowed.

5. packages/browser-sync/package.json:62

• Draft comment:
  serve-static upgraded to 1.16.2. Verify no unintended side effects with static file serving.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_EQ1lHdoo5YF9zf5e

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}