chore(deps): update all non-major dependencies (2.x)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@typescript-eslint/eslint-plugin	5.60.0 -> 5.60.1
@typescript-eslint/parser	5.60.0 -> 5.60.1
caniuse-lite	^1.0.30001507 -> ^1.0.30001508
esbuild	0.18.8 -> 0.18.10
lerna (source)	7.0.2 -> 7.1.0
rollup (source)	3.25.2 -> 3.25.3

---

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.60.1

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.60.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

browserslist/caniuse-lite (caniuse-lite)

v1.0.30001508

Compare Source

evanw/esbuild (esbuild)

v0.18.10

Compare Source

• Fix a tree-shaking bug that removed side effects (#​3195)

  This fixes a regression in version 0.18.4 where combining --minify-syntax with --keep-names could cause expressions with side effects after a function declaration to be considered side-effect free for tree shaking purposes. The reason was because --keep-names generates an expression statement containing a call to a helper function after the function declaration with a special flag that makes the function call able to be tree shaken, and then --minify-syntax could potentially merge that expression statement with following expressions without clearing the flag. This release fixes the bug by clearing the flag when merging expression statements together.

• Fix an incorrect warning about CSS nesting (#​3197)

  A warning is currently generated when transforming nested CSS to a browser that doesn't support :is() because transformed nested CSS may need to use that feature to represent nesting. This was previously always triggered when an at-rule was encountered in a declaration context. Typically the only case you would encounter this is when using CSS nesting within a selector rule. However, there is a case where that's not true: when using a margin at-rule such as @top-left within @page. This release avoids incorrectly generating a warning in this case by checking that the at-rule is within a selector rule before generating a warning.

v0.18.9

Compare Source

• Fix await using declarations inside async generator functions

  I forgot about the new await using declarations when implementing lowering for async generator functions in the previous release. This change fixes the transformation of await using declarations when they are inside lowered async generator functions:

  // Original code
  async function* foo() {
    await using x = await y
  }
  
  // Old output (with --supported:async-generator=false)
  function foo() {
    return __asyncGenerator(this, null, function* () {
      await using x = yield new __await(y);
    });
  }
  
  // New output (with --supported:async-generator=false)
  function foo() {
    return __asyncGenerator(this, null, function* () {
      var _stack = [];
      try {
        const x = __using(_stack, yield new __await(y), true);
      } catch (_) {
        var _error = _, _hasError = true;
      } finally {
        var _promise = __callDispose(_stack, _error, _hasError);
        _promise && (yield new __await(_promise));
      }
    });
  }

• Insert some prefixed CSS properties when appropriate (#​3122)

  With this release, esbuild will now insert prefixed CSS properties in certain cases when the target setting includes browsers that require a certain prefix. This is currently done for the following properties:

  • appearance: *; => -webkit-appearance: *; -moz-appearance: *;
  • backdrop-filter: *; => -webkit-backdrop-filter: *;
  • background-clip: text => -webkit-background-clip: text;
  • box-decoration-break: *; => -webkit-box-decoration-break: *;
  • clip-path: *; => -webkit-clip-path: *;
  • font-kerning: *; => -webkit-font-kerning: *;
  • hyphens: *; => -webkit-hyphens: *;
  • initial-letter: *; => -webkit-initial-letter: *;
  • mask-image: *; => -webkit-mask-image: *;
  • mask-origin: *; => -webkit-mask-origin: *;
  • mask-position: *; => -webkit-mask-position: *;
  • mask-repeat: *; => -webkit-mask-repeat: *;
  • mask-size: *; => -webkit-mask-size: *;
  • position: sticky; => position: -webkit-sticky;
  • print-color-adjust: *; => -webkit-print-color-adjust: *;
  • tab-size: *; => -moz-tab-size: *; -o-tab-size: *;
  • text-decoration-color: *; => -webkit-text-decoration-color: *; -moz-text-decoration-color: *;
  • text-decoration-line: *; => -webkit-text-decoration-line: *; -moz-text-decoration-line: *;
  • text-decoration-skip: *; => -webkit-text-decoration-skip: *;
  • text-emphasis-color: *; => -webkit-text-emphasis-color: *;
  • text-emphasis-position: *; => -webkit-text-emphasis-position: *;
  • text-emphasis-style: *; => -webkit-text-emphasis-style: *;
  • text-orientation: *; => -webkit-text-orientation: *;
  • text-size-adjust: *; => -webkit-text-size-adjust: *; -ms-text-size-adjust: *;
  • user-select: *; => -webkit-user-select: *; -moz-user-select: *; -ms-user-select: *;

  Here is an example:

  /* Original code */
  div {
    mask-image: url(x.png);
  }
  
  /* Old output (with --target=chrome99) */
  div {
    mask-image: url(x.png);
  }
  
  /* New output (with --target=chrome99) */
  div {
    -webkit-mask-image: url(x.png);
    mask-image: url(x.png);
  }

  Browser compatibility data was sourced from the tables on https://caniuse.com. Support for more CSS properties can be added in the future as appropriate.

• Fix an obscure identifier minification bug (#​2809)

  Function declarations in nested scopes behave differently depending on whether or not "use strict" is present. To avoid generating code that behaves differently depending on whether strict mode is enabled or not, esbuild transforms nested function declarations into variable declarations. However, there was a bug where the generated variable name was not being recorded as declared internally, which meant that it wasn't being renamed correctly by the minifier and could cause a name collision. This bug has been fixed:

  // Original code
  const n = ''
  for (let i of [0,1]) {
    function f () {}
  }
  
  // Old output (with --minify-identifiers --format=esm)
  const f = "";
  for (let o of [0, 1]) {
    let n = function() {
    };
    var f = n;
  }
  
  // New output (with --minify-identifiers --format=esm)
  const f = "";
  for (let o of [0, 1]) {
    let n = function() {
    };
    var t = n;
  }

• Fix a bug in esbuild's compatibility table script (#​3179)

  Setting esbuild's target to a specific JavaScript engine tells esbuild to use the JavaScript syntax feature compatibility data from https://kangax.github.io/compat-table/es6/ for that engine to determine which syntax features to allow. However, esbuild's script that builds this internal compatibility table had a bug that incorrectly ignores tests for engines that still have outstanding implementation bugs which were never fixed. This change fixes this bug with the script.

  The only case where this changed the information in esbuild's internal compatibility table is that the hermes target is marked as no longer supporting destructuring. This is because there is a failing destructuring-related test for Hermes on https://kangax.github.io/compat-table/es6/. If you want to use destructuring with Hermes anyway, you can pass --supported:destructuring=true to esbuild to override the hermes target and force esbuild to accept this syntax.

  This fix was contributed by @​ArrayZoneYour.

lerna/lerna (lerna)

v7.1.0

Compare Source

Features

• core: export detectProjects utility function (#​3740) (641fecb)
• repair: add migration to remove unused "lerna" field from lerna.json (#​3734) (4fb0427)
• version: add --changelog-entry-additional-markdown option (#​3751) (63671df)

7.0.2 (2023-06-15)

Note: Version bump only for package lerna

7.0.1 (2023-06-13)

Note: Version bump only for package lerna

rollup/rollup (rollup)

v3.25.3

Compare Source

2023-06-26

Bug Fixes

• Fix error when inlining dynamic imports that contain unused reexported variables (#​5047)

Pull Requests

• #​5047: Do not add tree-shaken variables to namespaces when inlining dynamic imports (@​lukastaegert)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.