Bump the npm group in /frontend with 3 updates

[dependabot]

Bumps the npm group in /frontend with 3 updates: esbuild, prettier and puppeteer.

Updates esbuild from 0.21.4 to 0.21.5

Release notes

Sourced from esbuild's releases.

v0.21.5

• Fix Symbol.metadata on classes without a class decorator (#3781)

  This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

• Allow unknown import attributes to be used with the copy loader (#3792)

  Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

  // This is an error with "--bundle" without also using "--external:./bagel.js"
  import tasty from "./bagel.js" with { type: "bagel" }

  Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

  However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

  // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
  import tasty from "./tasty.bagel" with { type: "bagel" }

• Support import attributes with glob-style imports (#3797)

  This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

  async function loadLocale(locale: string): Locale {
    const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    return unpackLocale(locale, data)
  }

  Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

  ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
  example.ts:2:28:
    2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
      ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  

  In addition, this change means plugins can now access the contents of with for glob-style imports.

• Support ${configDir} in tsconfig.json files (#3782)

  This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.5

• Fix Symbol.metadata on classes without a class decorator (#3781)

  This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

• Allow unknown import attributes to be used with the copy loader (#3792)

  Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

  // This is an error with "--bundle" without also using "--external:./bagel.js"
  import tasty from "./bagel.js" with { type: "bagel" }

  Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

  However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

  // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
  import tasty from "./tasty.bagel" with { type: "bagel" }

• Support import attributes with glob-style imports (#3797)

  This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

  async function loadLocale(locale: string): Locale {
    const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    return unpackLocale(locale, data)
  }

  Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

  ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
  example.ts:2:28:
    2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
      ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  

  In addition, this change means plugins can now access the contents of with for glob-style imports.

• Support ${configDir} in tsconfig.json files (#3782)

  This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Commits

• fc37c2f publish 0.21.5 to npm
• cb11924 fix Symbol.metadata errors in decorator tests
• b93a2a9 fix #3781: add metadata to all decorated classes
• 953dae9 fix #3797: import attributes and glob-style import
• 98cb2ed fix #3782: support ${configDir} in tsconfig.json
• 8e6603b run make update-compat-table
• db1b8ca fix #3792: import attributes and the copy loader
• de572d0 fix non-deterministic import attribute plugin test
• ae8d1b4 fix #3794: --supported:object-accessors=false
• See full diff in compare view

Updates prettier from 3.3.0 to 3.3.2

Release notes

Sourced from prettier's releases.

3.3.2

🔗 Changelog

3.3.1

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.3.2

diff

Fix handlebars path expressions starts with @ (#16358 by @​Princeyadav05)

{{! Input }}
<div>{{@x.y.z}}</div>
{{! Prettier 3.3.1 }}
<div>{{@​x}}</div>
{{! Prettier 3.3.2 }}
<div>{{@​x.y.z}}</div>

3.3.1

diff

Preserve empty lines in front matter (#16347 by @​fisker)

<!-- Input -->
---
foo:
  - bar1


bar2


bar3



Markdown
<!-- Prettier 3.3.0 -->

foo:

bar1
bar2
bar3


Markdown
<!-- Prettier 3.3.1 -->
</tr></table>

... (truncated)

Commits

• 1596a60 Release 3.3.2
• aebcee5 chore(deps): update dependency esbuild to v0.21.5 (#16379)
• 57aa928 chore(deps): update dependency c8 to v10 (#16380)
• c3d0b7f chore(deps): update typescript-eslint to v7.13.0 (#16376)
• 27c35db chore(deps): update dependency codemirror-graphql to v2.0.12 (#16369)
• 6de3258 chore(deps): update dependency jest to v30.0.0-alpha.5 (#16371)
• b5f983d Upgrade yarn to v4.3.0 (#16377)
• d6f37c4 chore(deps): update dependency browserslist to v4.23.1 (#16368)
• 5055b7d chore(deps): update dependency execa to v9.2.0 (#16372)
• f4608cc chore(deps): update dependency cspell to v8.8.4 (#16370)
• Additional commits viewable in compare view

Updates puppeteer from 22.10.0 to 22.11.0

Release notes

Sourced from puppeteer's releases.

puppeteer-core: v22.11.0

22.11.0 (2024-06-12)

Features

• allow creating ElementHandles from the accessibility tree snapshot (#12233) (0057f3f)
• roll to Chrome 126.0.6478.55 (r1300313) (#12572) (f5bc2b5)

Bug Fixes

• do not wait for extension page targets on connect (#12574) (5f2ee98)

puppeteer: v22.11.0

22.11.0 (2024-06-12)

Features

• roll to Chrome 126.0.6478.55 (r1300313) (#12572) (f5bc2b5)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • puppeteer-core bumped from 22.10.1 to 22.11.0

puppeteer-core: v22.10.1

22.10.1 (2024-06-11)

Bug Fixes

• add a way to run page.$$ without the isolation (#12539) (03e10a7)
• align network conditions presets with DevTools (#12542) (ee10745)
• exposed functions should only be called once (#12560) (8aac8b1)
• performance: use Runtime.getProperties for improved performance (#12561) (8b2059f)
• roll to Chrome 125.0.6422.141 (r1287751) (#12509) (c4fdd10)
• waitForSelector should work for pseudo classes (#12545) (0b2999f)
• webdriver: default values for touch events (#12554) (4d62988)
• webdriver: frame url should not be updated on navigationStarted (#12536) (7d0423b)
• webdriver: HTTPRequest redirect chain from first request (#12506) (68fd771)

puppeteer: v22.10.1

22.10.1 (2024-06-11)

Miscellaneous Chores

... (truncated)

Commits

• 74d9969 chore: release main (#12573)
• 5f2ee98 fix: do not wait for extension page targets on connect (#12574)
• 0057f3f feat: allow creating ElementHandles from the accessibility tree snapshot (#12...
• f5bc2b5 feat: roll to Chrome 126.0.6478.55 (r1300313) (#12572)
• defda09 chore: release main (#12507)
• dfefbd1 build(deps): bump chromium-bidi to 0.5.23 (#12569)
• aa54e97 chore(deps): Bump braces from 3.0.2 to 3.0.3 in /website (#12568)
• 0ee705e chore(build): update TypeScript to 5.4 (#12567)
• 03e10a7 fix: add a way to run page.$$ without the isolation (#12539)
• 9745173 chore(deps-dev): Bump the dev-dependencies group across 1 directory with 4 up...
• Additional commits viewable in compare view

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