Skip to content

build(deps): Bump the npm_and_yarn group across 2 directories with 5 updates - #31

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/npm_and_yarn-aff08d8c78
Open

build(deps): Bump the npm_and_yarn group across 2 directories with 5 updates#31
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/npm_and_yarn-aff08d8c78

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 22, 2025

Copy link
Copy Markdown

Bumps the npm_and_yarn group with 4 updates in the /frontend directory: esbuild, vite, wrangler and form-data.
Bumps the npm_and_yarn group with 1 update in the /frontend/clinician-portal directory: next.

Updates esbuild from 0.17.19 to 0.25.8

Release notes

Sourced from esbuild's releases.

v0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
  #has = (a: string) => dict.has(a);
  has = window
    ? (word: string): boolean => this.#has(word)
    : this.#has;
}

  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

  • Parse and print JavaScript imports with an explicit phase (#4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";
const bar = await import.source("<specifier>");

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

  • Fix TypeScript-specific class transform edge case (#3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
class Foo extends Bar {
  #private = 1;
  public: any;
  constructor() {
    super();
  }
}
// Old output (with esbuild v0.19.9)
class Foo extends Bar {
constructor() {
super();
this.#private = 1;
}
#private;
}
// Old output (with esbuild v0.19.10)
class Foo extends Bar {
constructor() {
this.#private = 1;
super();
}
#private;
}
// New output
class Foo extends Bar {
#private = 1;
constructor() {
super();
}
}

  • Minifier: allow reording a primitive past a side-effect (#3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (truncated)

Commits
  • 8c71947 publish 0.25.8 to npm
  • 0508f24 some parsing fixes for source phase imports
  • 6e4be2f js parser: recover from bad #private identifiers
  • c9c6357 fix #4248: #private ids in arrow fn body in ?:
  • 9b42f68 publish 0.25.7 to npm
  • 9ba01d1 abs-paths: js api and tests
  • ca196c9 fix for parser backtracking crash
  • 2979b84 fix #4241: ts arrow function type backtrack (hack)
  • 1180410 fix an unused variable warning
  • fc3da57 fix #4238: add defer and source import phases
  • Additional commits viewable in compare view

Updates vite from 5.4.19 to 7.0.5

Release notes

Sourced from vite's releases.

v7.0.5

Please refer to CHANGELOG.md for details.

v7.0.4

Please refer to CHANGELOG.md for details.

v7.0.3

Please refer to CHANGELOG.md for details.

create-vite@7.0.3

Please refer to CHANGELOG.md for details.

v7.0.2

Please refer to CHANGELOG.md for details.

create-vite@7.0.2

Please refer to CHANGELOG.md for details.

v7.0.1

Please refer to CHANGELOG.md for details.

create-vite@7.0.1

Please refer to CHANGELOG.md for details.

plugin-legacy@7.0.1

Please refer to CHANGELOG.md for details.

create-vite@7.0.0

Please refer to CHANGELOG.md for details.

plugin-legacy@7.0.0

Please refer to CHANGELOG.md for details.

v7.0.0

Please refer to CHANGELOG.md for details.

v7.0.0-beta.2

Please refer to CHANGELOG.md for details.

v7.0.0-beta.1

Please refer to CHANGELOG.md for details.

plugin-legacy@7.0.0-beta.1

Please refer to CHANGELOG.md for details.

plugin-legacy@7.0.0-beta.0

Please refer to CHANGELOG.md for details.

v7.0.0-beta.0

Please refer to CHANGELOG.md for details.

... (truncated)

Changelog

Sourced from vite's changelog.

7.0.5 (2025-07-17)

Bug Fixes

  • deps: update all non-major dependencies (#20406) (1a1cc8a)
  • remove special handling for Accept: text/html (#20376) (c9614b9)
  • watch assets referenced by new URL(, import.meta.url) (#20382) (6bc8bf6)

Miscellaneous Chores

  • deps: update dependency rolldown to ^1.0.0-beta.27 (#20405) (1165667)

Code Refactoring

  • use foo.endsWith("bar") instead of /bar$/.test(foo) (#20413) (862e192)

7.0.4 (2025-07-10)

Bug Fixes

  • allow resolving bare specifiers to relative paths for entries (#20379) (324669c)

Build System

7.0.3 (2025-07-08)

Bug Fixes

  • client: protect against window being defined but addEv undefined (#20359) (31d1467)
  • define: replace optional values (#20338) (9465ae1)
  • deps: update all non-major dependencies (#20366) (43ac73d)

Miscellaneous Chores

Code Refactoring

  • minor changes to reduce diff between normal Vite and rolldown-vite (#20354) (2e8050e)

7.0.2 (2025-07-04)

Bug Fixes

7.0.1 (2025-07-03)

Bug Fixes

... (truncated)

Commits
  • 832f687 release: v7.0.5
  • c9614b9 fix: remove special handling for Accept: text/html (#20376)
  • 862e192 refactor: use foo.endsWith("bar") instead of /bar$/.test(foo) (#20413)
  • 6bc8bf6 fix: watch assets referenced by new URL(, import.meta.url) (#20382)
  • 1a1cc8a fix(deps): update all non-major dependencies (#20406)
  • 1165667 chore(deps): update dependency rolldown to ^1.0.0-beta.27 (#20405)
  • 8a65433 release: v7.0.4
  • 324669c fix: allow resolving bare specifiers to relative paths for entries (#20379)
  • 5e29602 build: remove @oxc-project/runtime devDep (#20389)
  • f562df8 release: v7.0.3
  • Additional commits viewable in compare view

Updates wrangler from 3.114.9 to 4.25.0

Release notes

Sourced from wrangler's releases.

wrangler@4.25.0

Minor Changes

Patch Changes

wrangler@4.24.4

Patch Changes

wrangler@4.24.3

Patch Changes

  • #9923 c01c4ee Thanks @​gpanders! - Fix image name resolution when modifying a container application

  • #9833 3743896 Thanks @​dario-piotrowicz! - fix: ensure that container builds don't disrupt dev hotkey handling

    currently container builds run during local development (via wrangler dev or startWorker) prevent the standard hotkeys not to be recognized (most noticeably ctrl+c, preventing developers from existing the process), the changes here ensure that hotkeys are instead correctly handled as expected

  • Updated dependencies []:

    • miniflare@4.20250709.0

wrangler@4.24.2

Patch Changes

wrangler@4.24.1

Patch Changes

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.25.0

Minor Changes

Patch Changes

4.24.4

Patch Changes

4.24.3

Patch Changes

  • #9923 c01c4ee Thanks @​gpanders! - Fix image name resolution when modifying a container application

  • #9833 3743896 Thanks @​dario-piotrowicz! - fix: ensure that container builds don't disrupt dev hotkey handling

    currently container builds run during local development (via wrangler dev or startWorker) prevent the standard hotkeys not to be recognized (most noticeably ctrl+c, preventing developers from existing the process), the changes here ensure that hotkeys are instead correctly handled as expected

  • Updated dependencies []:

    • miniflare@4.20250709.0

4.24.2

Patch Changes

... (truncated)

Commits

Updates form-data from 4.0.2 to 4.0.4

Changelog

Sourced from form-data's changelog.

v4.0.4 - 2025-07-16

Commits

  • [meta] add auto-changelog 811f682
  • [Tests] handle predict-v8-randomness failures in node < 17 and node > 23 1d11a76
  • [Fix] Switch to using crypto random for boundary values 3d17230
  • [Tests] fix linting errors 5e34080
  • [meta] actually ensure the readme backup isn’t published 316c82b
  • [Dev Deps] update @ljharb/eslint-config 58c25d7
  • [meta] fix readme capitalization 2300ca1

v4.0.3 - 2025-06-05

Fixed

Commits

  • [eslint] use a shared config 426ba9a
  • [eslint] fix some spacing issues 2094191
  • [Refactor] use hasown 81ab41b
  • [Fix] validate boundary type in setBoundary() method 8d8e469
  • [Tests] add tests to check the behavior of getBoundary with non-strings 837b8a1
  • [Dev Deps] remove unused deps 870e4e6
  • [meta] remove local commit hooks e6e83cc
  • [Dev Deps] update eslint 4066fd6
  • [meta] fix scripts to use prepublishOnly c4bbb13
Commits
  • 41996f5 v4.0.4
  • 316c82b [meta] actually ensure the readme backup isn’t published
  • 2300ca1 [meta] fix readme capitalization
  • 811f682 [meta] add auto-changelog
  • 5e34080 [Tests] fix linting errors
  • 1d11a76 [Tests] handle predict-v8-randomness failures in node < 17 and node > 23
  • 58c25d7 [Dev Deps] update @ljharb/eslint-config
  • 3d17230 [Fix] Switch to using crypto random for boundary values
  • d8d67dc v4.0.3
  • e6e83cc [meta] remove local commit hooks
  • Additional commits viewable in compare view

Updates next from 13.5.11 to 15.4.2

Release notes

Sourced from next's releases.

v15.4.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • pages router metadata bugs with React 19 (#81733)
  • [metadata] replace for initial body icon case (#81688)
  • Ensure custom NextServer config is honored (#81681)

Credits

Huge thanks to @​huozhi, @​ijjk, and @​ztanner for helping!

v15.4.2-canary.12

Core Changes

  • Upgrade React from dffacc7b-20250717 to e9638c33-20250721: #81899
  • chore(devtools): sync todos to linear: #81901
  • Introduce 'use cache: private': #81816
  • chore(deps): update browserslist: #81851
  • Remove web-server from edge-ssr-app: #81389

Misc Changes

  • Remove experimental.strictNextHead: #81882
  • Remove some random commas: #81875
  • Turbopack: Add cache for reqwest clients: #81742
  • Update Rspack development test manifest: #81878
  • Update Rspack production test manifest: #81879

Credits

Huge thanks to @​RobPruzan, @​eps1lon, @​unstubbable, @​MidnightDesign, @​bgw, @​stephenliang, @​vercel-release-bot, and @​ijjk for helping!

v15.4.2-canary.11

Core Changes

  • [sourcemaps] Try VM for retrieving source maps first: #81869
  • [devtools] save user config inside .next/cache: #81807
  • Server: Remove unused code: #81886
  • refactor: encapsulate content type within RenderResult: #81861
  • refactor: handle null RenderResult responses gracefully: #81895

Misc Changes

  • Turbopack: fix unhelpful error message when deleting folder fails: #81718

Credits

... (truncated)

Commits

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.

@dependabot
build(deps): Bump the npm_and_yarn group across 2 directories with 5 …
5539ce9 
…updates

Bumps the npm_and_yarn group with 4 updates in the /frontend directory: [esbuild](https://github.com/evanw/esbuild), [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite), [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) and [form-data](https://github.com/form-data/form-data).
Bumps the npm_and_yarn group with 1 update in the /frontend/clinician-portal directory: [next](https://github.com/vercel/next.js).


Updates `esbuild` from 0.17.19 to 0.25.8
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2023.md)
- [Commits](evanw/esbuild@v0.17.19...v0.25.8)

Updates `vite` from 5.4.19 to 7.0.5
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v7.0.5/packages/vite)

Updates `wrangler` from 3.114.9 to 4.25.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.25.0/packages/wrangler)

Updates `form-data` from 4.0.2 to 4.0.4
- [Release notes](https://github.com/form-data/form-data/releases)
- [Changelog](https://github.com/form-data/form-data/blob/master/CHANGELOG.md)
- [Commits](form-data/form-data@v4.0.2...v4.0.4)

Updates `next` from 13.5.11 to 15.4.2
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v13.5.11...v15.4.2)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.25.8
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-version: 7.0.5
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: wrangler
  dependency-version: 4.25.0
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: form-data
  dependency-version: 4.0.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: next
  dependency-version: 15.4.2
  dependency-type: direct:production
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants