Update all dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@sentry/browser (source)	7.44.2 -> 7.45.0					devDependencies	minor
@sentry/cli (source)	2.15.2 -> 2.16.0					devDependencies	minor
@sentry/tracing (source)	7.44.2 -> 7.45.0					devDependencies	minor
actions/checkout	24cb908 -> 8f4b7f8					action	digest
esbuild	0.17.12 -> 0.17.13					devDependencies	patch

---

Release Notes

getsentry/sentry-javascript

v7.45.0

Compare Source

• build(cdn): Ensure ES5 bundles do not use non-ES5 code (#​7550)
• feat(core): Add trace function (#​7556)
• feat(hub): Make scope always defined on the hub (#​7551)
• feat(replay): Add replay_id to transaction DSC (#​7571)
• feat(replay): Capture fetch body size for replay events (#​7524)
• feat(sveltekit): Add performance monitoring for client load (#​7537)
• feat(sveltekit): Add performance monitoring for server load (#​7536)
• feat(sveltekit): Add performance monitoring to Sveltekit server handle (#​7532)
• feat(sveltekit): Add SvelteKit routing instrumentation (#​7565)
• fix(browser): Ensure keepalive flag is correctly set for parallel requests (#​7553)
• fix(core): Ensure ignoreErrors only applies to error events (#​7573)
• fix(node): Consider tracing error handler for process exit (#​7558)
• fix(otel): Make sure we use correct hub on finish (#​7577)
• fix(react): Handle case where error.cause already defined (#​7557)

getsentry/sentry-cli

v2.16.0

Compare Source

Various fixes & improvements

• ref(crons): Prefer DSN based auth (#​1545) by @​kamilogorek
• fix(inject): Improve fixup_js_file (#​1533) by @​loewenheim
• feat(inject): Handle relative and absoule sourcemap URLs (#​1530) by @​loewenheim
• ref(monitors): Prefer slugs over guids (#​1540) by @​evanpurkhiser
• feat(auth): Support DSN auth for the API client (#​1536) by @​evanpurkhiser
• ref(crons): monitors command is not legacy atm (#​1538) by @​evanpurkhiser
• fix(help): Consistent wording for API keys (#​1539) by @​evanpurkhiser

evanw/esbuild

v0.17.13

Compare Source

• Work around an issue with NODE_PATH and Go's WebAssembly internals (#​3001)

  Go's WebAssembly implementation returns EINVAL instead of ENOTDIR when using the readdir syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encountering ENOTDIR causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacy NODE_PATH feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by converting EINVAL into ENOTDIR for the readdir syscall.

• Fix a minification bug with CSS @layer rules that have parsing errors (#​3016)

  CSS at-rules require either a {} block or a semicolon at the end. Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically cssnano can generate @layer rules with parsing errors, and empty @layer rules cannot be removed because they have side effects (@layer didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard @layer rules with parsing errors when minifying (the rule @layer c has a parsing error):

  /* Original input */
  @​layer a {
    @​layer b {
      @​layer c
    }
  }
  
  /* Old output (with --minify) */
  @​layer a.b;
  
  /* New output (with --minify) */
  @​layer a.b.c;

• Unterminated strings in CSS are no longer an error

  The CSS specification provides rules for handling parsing errors. One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example:

  p {
    color: green;
    font-family: 'Courier New Times
    color: red;
    color: green;
  }

  ...would be treated the same as:

  p { color: green; color: green; }

  ...because the second declaration (from font-family to the semicolon after color: red) is invalid and is dropped.

  Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output:

  /* esbuild's new non-minified output: */
  p {
    color: green;
    font-family: 'Courier New Times
    color: red;
    color: green;
  }

  /* esbuild's new minified output: */
  p{font-family:'Courier New Times
  color: red;color:green}

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.