maint(deps): bump the example-deps group in /packages/honeycomb-opentelemetry-web/examples/hello-world-web with 3 updates

[dependabot]

Bumps the example-deps group in /packages/honeycomb-opentelemetry-web/examples/hello-world-web with 3 updates: @opentelemetry/context-zone, chokidar and esbuild.

Updates @opentelemetry/context-zone from 1.28.0 to 1.30.0

Release notes

Sourced from @​opentelemetry/context-zone's releases.

v1.30.0

1.30.0

🚀 (Enhancement)

• feat(sdk-metrics): PeriodicExportingMetricReader now flushes pending tasks at shutdown #5242

🐛 (Bug Fix)

• fix(sdk-trace-base): do not load OTEL_ env vars on module load, but when needed #5233
• fix(instrumentation-xhr, instrumentation-fetch): content length attributes no longer get removed with ignoreNetworkEvents: true being set #5229

v1.29.0

1.29.0

🚀 (Enhancement)

• feat(sdk-metrics): Add support for aggregation cardinality limit with a default limit of 2000. This limit can be customized via views #5128

Changelog

Sourced from @​opentelemetry/context-zone's changelog.

1.30.0

🚀 (Enhancement)

• feat(sdk-metrics): PeriodicExportingMetricReader now flushes pending tasks at shutdown #5242

🐛 (Bug Fix)

• fix(sdk-trace-base): do not load OTEL_ env vars on module load, but when needed #5233
• fix(instrumentation-xhr, instrumentation-fetch): content length attributes no longer get removed with ignoreNetworkEvents: true being set #5229

1.29.0

🚀 (Enhancement)

• feat(sdk-metrics): Add support for aggregation cardinality limit with a default limit of 2000. This limit can be customized via views #5128

Commits

• 616d27a chore: prepare next release (#5274)
• e524148 chore: removed circular dependency from BasicTracerProvider (#5279)
• 67a0e9c Update links to openmetrics to reference the v1.0.0 release (#5267)
• 0c11fc6 Fix incorrect CHANGELOG entry on main (v1.next) (#5280)
• 8ab52d5 fix(ci): adapt workflow to use supported npm versions (#5277)
• 84cce75 refactor(otlp-transformer): re-structure package to prepare for separate entr...
• 6d31a18 feat(opentelemetry-sdk-node): automatically configure metrics exporter based ...
• e03b6e7 chore: update prettier to 3.4.2 (#5261)
• e4d9c21 fix(instrumentation-fetch, instrumentation-xml-http-request) content length a...
• bdee949 doc(semantic-conventions): clarify suggested usage of unstable semconv (#5256)
• Additional commits viewable in compare view

Updates chokidar from 4.0.1 to 4.0.3

Release notes

Sourced from chokidar's releases.

4.0.3

What's Changed

• Fix typescript type of emitted args by @​43081j in paulmillr/chokidar#1397

Full Changelog: paulmillr/chokidar@4.0.2...4.0.3

4.0.2

What's Changed

• Fix test "should detect safe-edit" on FreeBSD by @​tagattie in paulmillr/chokidar#1375
• Remove references to .map files by @​bluwy in paulmillr/chokidar#1383
• feat: strongly type event emitter methods by @​43081j in paulmillr/chokidar#1381

New Contributors

• @​bxt made their first contribution in paulmillr/chokidar#1365
• @​tagattie made their first contribution in paulmillr/chokidar#1375
• @​bluwy made their first contribution in paulmillr/chokidar#1383

Full Changelog: paulmillr/chokidar@4.0.1...4.0.2

Commits

• 1182965 Release 4.0.3.
• 9470932 Merge pull request #1397 from paulmillr/unlink-types
• 322e851 fix: separate error emit from regular events
• 3fa04b5 fix: strongly type unlink events
• 69c115a Release 4.0.2.
• 50cf698 Ignore map
• 5e6daaa Merge pull request #1381 from paulmillr/event-types
• e9cd7f6 Merge pull request #1383 from bluwy/map-ref
• 6981c5d Remove references to .map files
• 7958696 feat: strongly type event emitter methods
• Additional commits viewable in compare view

Updates esbuild from 0.24.0 to 0.24.2

Release notes

Sourced from esbuild's releases.

v0.24.2

• Fix regression with --define and import.meta (#4010, #4012, #4013)

  The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

  This fix was contributed by @​sapphi-red.

v0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

  // The following code now transforms to "return true;\n"
  console.log(esbuild.transformSync(
    `return process.env['SOME-TEST-VAR']`,
    { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
  ))

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.24.2

• Fix regression with --define and import.meta (#4010, #4012, #4013)

  The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

  This fix was contributed by @​sapphi-red.

0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

  // The following code now transforms to "return true;\n"
  console.log(esbuild.transformSync(
    `return process.env['SOME-TEST-VAR']`,
    { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },

... (truncated)

Commits

• 745abd9 publish 0.24.2 to npm
• 79fd0b0 skip nulls in source map finalization (#4011)
• 4b9322f source map: avoid null entry for 0-length parts
• 199a0d3 close #4013: credit to @​sapphi-red for the fix
• 947f99f fix #4010, fix #4012: import.meta regression
• de9598f publish 0.24.1 to npm
• 15d56ca emit null source mappings for empty chunk content
• 8d98f6f fix #3985: entryPoint metadata for copy loader
• 0db1b82 fix #3998: avoid outbase in identifier names
• 7236472 close #3974: add support for netbsd on arm64
• 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