chore(deps): update all non-major dev dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@commitlint/cli (source)	19.5.0 -> 19.6.1
@commitlint/config-conventional (source)	19.5.0 -> 19.6.0
@types/chai (source)	5.0.0 -> 5.0.1
@types/mocha (source)	10.0.9 -> 10.0.10
@types/node (source)	18.19.57 -> 18.19.70
c8	10.1.2 -> 10.1.3
chai (source)	5.1.1 -> 5.1.2
esbuild	0.24.0 -> 0.24.2
husky	9.1.6 -> 9.1.7
lerna (source)	8.1.8 -> 8.1.9
lint-staged	15.2.10 -> 15.3.0
mocha (source)	10.7.3 -> 10.8.2
npm-run-all2	6.2.4 -> 6.2.6
prettier (source)	3.3.3 -> 3.4.2
typescript (source)	5.6.3 -> 5.7.2

---

Release Notes

conventional-changelog/commitlint (@​commitlint/cli)

v19.6.1

Compare Source

Note: Version bump only for package @​commitlint/cli

v19.6.0

Compare Source

Note: Version bump only for package @​commitlint/cli

conventional-changelog/commitlint (@​commitlint/config-conventional)

v19.6.0

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

bcoe/c8 (c8)

v10.1.3

Compare Source

Bug Fixes

• deps: update bcoe/v8-coverage addressing v8 issue (#​552) (b32a563)

chaijs/chai (chai)

v5.1.2

Compare Source

What's Changed

• Fix secret name in publish action by @​koddsson in https://github.com/chaijs/chai/pull/1614
• Publish npm packages with provenance by @​koddsson in https://github.com/chaijs/chai/pull/1615
• build(deps-dev): bump braces from 3.0.2 to 3.0.3 by @​dependabot in https://github.com/chaijs/chai/pull/1625
• chore: bump loupe and deep-eql by @​43081j in https://github.com/chaijs/chai/pull/1635
• build(deps-dev): bump @​75lb/deep-merge from 1.1.1 to 1.1.2 by @​dependabot in https://github.com/chaijs/chai/pull/1636
• build(deps): bump rollup from 4.9.1 to 4.22.4 by @​dependabot in https://github.com/chaijs/chai/pull/1637
• chore: update deep dependencies by @​43081j in https://github.com/chaijs/chai/pull/1641
• chore: upgrade loupe by @​43081j in https://github.com/chaijs/chai/pull/1646
• Support big int in approximently by @​koddsson in https://github.com/chaijs/chai/pull/1606

Full Changelog: chaijs/chai@v5.1.1...v5.1.2

evanw/esbuild (esbuild)

v0.24.2

Compare Source

• 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

Compare Source

• 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' } },
  ))

  Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.

• Minify empty try/catch/finally blocks (#​4003)

  With this release, esbuild will now attempt to minify empty try blocks:

  // Original code
  try {} catch { foo() } finally { bar() }
  
  // Old output (with --minify)
  try{}catch{foo()}finally{bar()}
  
  // New output (with --minify)
  bar();

  This can sometimes expose additional minification opportunities.

• Include entryPoint metadata for the copy loader (#​3985)

  Almost all entry points already include a entryPoint field in the outputs map in esbuild's build metadata. However, this wasn't the case for the copy loader as that loader is a special-case that doesn't behave like other loaders. This release adds the entryPoint field in this case.

• Source mappings may now contain null entries (#​3310, #​3878)

  With this change, sources that result in an empty source map may now emit a null source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now the null mapping "resets" the source map so that any lookups into the minified code without any mappings resolves to null (which appears as the output file in stack traces) instead of the incorrect source file.

  This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.

• Avoid using the parent directory name for determinism (#​3998)

  To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named index.js (or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all named index.js but have unique directory names).

  This is problematic when the bundle entry point is named index.js and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now use index instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild's outbase API option, which defaults to the lowest common ancestor of all user-specified entry point paths.

• Experimental support for esbuild on NetBSD (#​3974)

  With this release, esbuild now has a published binary executable for NetBSD in the @esbuild/netbsd-arm64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @​bsiegert.

  ⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️

typicode/husky (husky)

v9.1.7

Compare Source

lerna/lerna (lerna)

v8.1.9

Compare Source

Bug Fixes

• add extends property in schema (#​4075) (28c8ef2)
• core: avoid reading empty .config.json, upgrade cosmiconfig@v9.0.0 (#​4062) (960bdd9)
• update nx support to latest v20 (#​4103) (cb37f19)

lint-staged/lint-staged (lint-staged)

v15.3.0

Compare Source

Minor Changes

• #​1495 e69da9e Thanks @​iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.

• #​1493 fa0fe98 Thanks @​iiroj! - Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

  For example:

  % npx lint-staged
  ✔ Backed up original state in git stash (20addf8)
  ✔ Running tasks for staged files...
  ✔ Applying modifications from tasks...
  ✔ Cleaning up temporary files...
  

  where the backup can be seen with git show 20addf8, or git stash list:

  % git stash list
  stash@{0}: lint-staged automatic backup (20addf8)
  

v15.2.11

Compare Source

Patch Changes

• #​1484 bcfe309 Thanks @​wormsik! - Escape paths containing spaces when using the "shell" option.

• #​1487 7dd8caa Thanks @​iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

mochajs/mocha (mocha)

v10.8.2

Compare Source

🩹 Fixes

• support errors with circular dependencies in object values with --parallel (#​5212) (ba0fefe)
• test link in html reporter (#​5224) (f054acc)

📚 Documentation

• indicate 'exports' interface does not work in browsers (#​5181) (14e640e)

🧹 Chores

• fix docs builds by re-adding eleventy and ignoring gitignore again (#​5240) (881e3b0)

🤖 Automation

• deps: bump the github-actions group with 1 update (#​5132) (e536ab2)

v10.8.1

Compare Source

🩹 Fixes

• handle case of invalid package.json with no explicit config (#​5198) (f72bc17)
• Typos on mochajs.org (#​5237) (d8ca270)
• use accurate test links in HTML reporter (#​5228) (68803b6)

v10.8.0

Compare Source

🌟 Features

• highlight browser failures (#​5222) (8ff4845)

🩹 Fixes

• remove :is() from mocha.css to support older browsers (#​5225) (#​5227) (0a24b58)

📚 Documentation

• add SECURITY.md pointing to Tidelift (#​5210) (bd7e63a)
• adopt Collective Funds Guidelines 0.1 (#​5199) (2b03d86)
• update README, LICENSE and fix outdated (#​5197) (1203e0e)

🧹 Chores

• fix npm scripts on windows (#​5219) (1173da0)
• remove trailing whitespace in SECURITY.md (7563e59)

bcomnes/npm-run-all2 (npm-run-all2)

v6.2.6

Compare Source

Commits

• Prevent a throw when looking up undefined results d928f9a

v6.2.5

Compare Source

prettier/prettier (prettier)

v3.4.2

Compare Source

diff

Treat U+30A0 & U+30FB in Katakana Block as CJK (#​16796 by @​tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->

C言
語
・
C++
・
Go
・
Rust

<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust

<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン＝サーンス”).

Fix comments print on class methods with decorators (#​16891 by @​fisker)

// Input
class A {
  @​decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @​decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @​decorator
  /**
   * The method description
   *
   */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

Fix non-idempotent formatting (#​16899 by @​seiyab)

This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.

// Input
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.1 (first)
<div>
  foo
  <span>
    longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
  </span>, abc
</div>;

// Prettier 3.4.1 (second)
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.2
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

v3.4.1

Compare Source

diff

Remove unnecessary parentheses around assignment in v-on (#​16887 by @​fisker)

<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

v3.4.0

Compare Source

diff

🔗 Release Notes

microsoft/TypeScript (typescript)

v5.7.2

Compare Source

---

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 was generated by Mend Renovate. View the repository job log.