chore(deps): bump the dependencies group with 2 updates

[dependabot]

Bumps the dependencies group with 2 updates: esbuild and puppeteer.

Updates esbuild from 0.19.12 to 0.20.1

Release notes

Sourced from esbuild's releases.

v0.20.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.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

• Work around API deprecations in Deno 1.40.x (#3609, #3611)

  Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

  Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

• Reorder implicit file extensions within node_modules (#3341, #3608)

  In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

  With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

  Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

Changelog

Sourced from esbuild's changelog.

0.20.1

• Fix a bug with the CSS nesting transform (#3648)

  This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:

  /* Original code */
  .foo {
    &:after,
    & .bar {
      color: red;
    }
  }
  /* Old output (with --supported:nesting=false) */
  .foo .bar,
  .foo .bar {
  color: red;
  }
  /* New output (with --supported:nesting=false) */
  .foo:after,
  .foo .bar {
  color: red;
  }

• Constant folding for JavaScript inequality operators (#3645)

  This release introduces constant folding for the < > <= >= operators. The minifier will now replace these operators with true or false when both sides are compile-time numeric or string constants:

  // Original code
  console.log(1 < 2, '🍕' > '🧀')
  // Old output (with --minify)
  console.log(1<2,"🍕">"🧀");
  // New output (with --minify)
  console.log(!0,!1);

• Better handling of __proto__ edge cases (#3651)

  JavaScript object literal syntax contains a special case where a non-computed property with a key of __proto__ sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:

  // Original code
  function foo(__proto__) {

... (truncated)

Commits

• 9f9e4f8 publish 0.20.1 to npm
• ac36537 fix #3651: handle __proto__ edge cases better
• 555db48 fix #3645: constant folding for \< > \<= >=
• 5650831 fix #3650: add a wrapper for float64 math
• d086889 fix some lints
• ad3d8c6 fix #3648: copy selectors before checking children
• a08f30d fix #3634: crash if resolving with bad source dir
• 2af5ccf publish 0.20.0 to npm
• 0bccf08 fix esbuild/deno-esbuild#5
• 931f87d work around api deprecations in deno 1.40.x (#3609) (#3611)
• Additional commits viewable in compare view

Updates puppeteer from 21.11.0 to 22.3.0

Release notes

Sourced from puppeteer's releases.

puppeteer-core: v22.3.0

22.3.0 (2024-02-25)

Features

• implement permissions for WebDriver BiDi (#11979) (3a467c3)

Bug Fixes

• roll to Chrome 122.0.6261.69 (r1250580) (#11991) (eb2c334)
• supress viewport errors for pages that do not support changing it (#11970) (753a954)

puppeteer: v22.3.0

22.3.0 (2024-02-25)

Miscellaneous Chores

• puppeteer: Synchronize puppeteer versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • puppeteer-core bumped from 22.2.0 to 22.3.0

puppeteer-core: v22.2.0

22.2.0 (2024-02-21)

Features

• roll to Chrome 122.0.6261.57 (r1250580) (#11958) (70ad3b2)

Bug Fixes

• deprecate isIncognito (#11962) (ceab7a9)
• roll to Chrome 121.0.6167.184 (r1233107) (#11948) (03ef7a6)
• update touchscreen tests (#11960) (013bd0b)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​puppeteer/browsers bumped from 2.0.1 to 2.1.0

... (truncated)

Commits

• 9ddfa53 chore: release main (#11972)
• 5f2e73c chore(deps): Bump the all group with 1 update (#11996)
• 72d90b8 chore(deps-dev): Bump the dev-dependencies group with 5 updates (#11995)
• eb2c334 fix: roll to Chrome 122.0.6261.69 (r1250580) (#11991)
• 3a467c3 feat: implement permissions for WebDriver BiDi (#11979)
• bba2811 chore: update devcontainer.json to Node 18 (#11986)
• 7966dd7 chore: refactor exposed function for BiDi (#11976)
• 04392d8 chore(deps-dev): Bump the dev-dependencies group with 9 updates (#11974)
• 3448a40 build: fix windows build (#11975)
• 5e942b3 chore(deps): Bump the dependencies group with 1 update (#11973)
• 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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.