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

[dependabot]

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

Updates @opentelemetry/context-zone from 1.26.0 to 1.27.0

Release notes

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

semconv/v1.27.0

1.27.0

• Version bump only
• Note: This package will now be versioned according to the version of semantic conventions being provided.

v1.27.0

1.27.0

🚀 (Enhancement)

• feat: add processors for adding session.id attribute to spans and logs #4972

🐛 (Bug Fix)

• fix(sdk-trace-base): avoid keeping non-string status.message on Span#setStatus() #4999 @​pichlermarc
• fix(sdk-metrics): Add missing catch and handle error in promise of PeriodicExportingMetricReader #5006 @​jj22ee
• fix(opentelemetry-core): confusing log extract of composite propagator #5017 @​rv2673
• fix(propagator-aws-xray-*): move propagators back to contrib repository #4966 @​pichlermarc
  • The specification prohibits hosting these packages in the core repository
  • @opentelemetry/propagator-aws-xray is now located in open-telemetry/opentelemetry-js-contrib
  • @opentelemetry/propagator-aws-xray-lambda is now located in open-telemetry/opentelemetry-js-contrib

🏠 (Internal)

• deps: set @opentelemetry/api dependency min version to 1.3.0 in examples, experimental/packages, integration-tests and selenium-tests #4992
• refactor(sdk-metrics): replace MetricsAttributes with Attributes #5021 @​david-luna
• refactor(instrumentation-http): replace SpanAttributes and MetricsAttributes with Attributes #5023 @​david-luna
• chore(exporter-zipkin): remove usages of Span constructor #5030 @​david-luna
• test(instrumentation-http): remove usages of new Span in tests #5035 @​david-luna

Changelog

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

1.27.0

🚀 (Enhancement)

• feat: add processors for adding session.id attribute to spans and logs #4972

🐛 (Bug Fix)

• fix(sdk-trace-base): avoid keeping non-string status.message on Span#setStatus() #4999 @​pichlermarc
• fix(sdk-metrics): Add missing catch and handle error in promise of PeriodicExportingMetricReader #5006 @​jj22ee
• fix(opentelemetry-core): confusing log extract of composite propagator #5017 @​rv2673
• fix(propagator-aws-xray-*): move propagators back to contrib repository #4966 @​pichlermarc
  • The specification prohibits hosting these packages in the core repository
  • @opentelemetry/propagator-aws-xray is now located in open-telemetry/opentelemetry-js-contrib
  • @opentelemetry/propagator-aws-xray-lambda is now located in open-telemetry/opentelemetry-js-contrib

🏠 (Internal)

• deps: set @opentelemetry/api dependency min version to 1.3.0 in examples, experimental/packages, integration-tests and selenium-tests #4992
• refactor(sdk-metrics): replace MetricsAttributes with Attributes #5021 @​david-luna
• refactor(instrumentation-http): replace SpanAttributes and MetricsAttributes with Attributes #5023 @​david-luna
• chore(exporter-zipkin): remove usages of Span constructor #5030 @​david-luna
• test(instrumentation-http): remove usages of new Span in tests #5035 @​david-luna

Commits

• eb3ca4f chore: prepare next release (#5068)
• 6fee82d chore: add @​maryliag to approvers (#5083)
• 50d59ca feat(instrumentation-http)!: remove deprecated ignore options (#5085)
• 4497ee3 Added limitation in ot-shim readme (#5072)
• 006fe44 chore: move xray and xray-lambda propagators to contrib (#4966)
• 330172c fix(instrumentation-http): add server attributes after they become available ...
• 55a1fc8 fix(instrumentation-http): fix http/https ESM instr for 'import defaultExport...
• 5e17361 chore(deps): update dependency chromedriver to v130 (#5080)
• be1737f chore: add markdown lint check to default lint command (#5074)
• c208991 test: use venv in w3c trace context test script (#5071)
• Additional commits viewable in compare view

Updates chokidar from 3.6.0 to 4.0.1

Release notes

Sourced from chokidar's releases.

4.0.1

• Various fixes and improvements of typescript types

New Contributors

• @​benmccann made their first contribution in paulmillr/chokidar#1349
• @​talentlessguy made their first contribution in paulmillr/chokidar#1356

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

4.0.0

• Remove glob support
• Remove bundled fsevents
• Decrease dependency count from 13 to 1
• Rewrite in typescript. Makes emitted types more precise
• The package became hybrid common.js / ESM
• Bump minimum node.js requirement to v14+

Special thanks to @​43081j for improvements and help.

Full Changelog: paulmillr/chokidar@3.6.0...4.0.0

Commits

• 8c3479f Release 4.0.1.
• 812cf64 README
• 8f9f136 Remove changelog md
• 66a96ff Update license year
• bf65c94 improve internal types a little bit (#1363)
• 4242091 Merge pull request #1360 from paulmillr/fseventsless
• 95aa953 fix: always return promise in close() (#1359)
• bad7dce fix: remove fsevents from docs and JSDoc
• 9b15d99 Merge pull request #1356 from talentlessguy/remove-type-fromjsdoc
• f4d8ad0 fix: remove jsdoc types and improve internal types
• Additional commits viewable in compare view

Updates esbuild from 0.23.1 to 0.24.0

Release notes

Sourced from esbuild's releases.

v0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

• Drop support for older platforms (#3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

  This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

  Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#3917)

  This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

  This fix was contributed by @​Joshix-1.

Changelog

Sourced from esbuild's changelog.

0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

• Drop support for older platforms (#3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

  This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

  Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#3917)

  This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

  This fix was contributed by @​Joshix-1.

Commits

• d34e79e publish 0.24.0 to npm
• 045a87f fix #3887: omit dead export warning for default
• 6e049b8 fix #3913: useDefineForClassFields and decorators
• 9c26f98 lower decorators for useDefineForClassFields #3913
• 46fdb68 fix #3898: incorrect cyclic tsconfig.json warning
• b500443 fix #3917: running esbuild cli with deno
• b125e62 run make update-compat-table
• 112b9aa fix #3915: stack overflow with yarn + tsconfig
• ed5a555 wasm: catch and rethrow stack overflows (#3915)
• 11d3196 fix #3902: update go 1.22.5 => 1.23.1
• Additional commits viewable in compare view

Updates serve from 14.2.3 to 14.2.4

Release notes

Sourced from serve's releases.

14.2.4

Patches

• Bump serve-handler, vitest, and `typescript: #812

Commits

• dd53938 14.2.4
• 67d75e0 Bump serve-handler, vitest, and typescript (#812)
• d06104a X handle has changed (#805)
• See full diff 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