chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@biomejs/biome (source)	1.9.1 -> 1.9.2
esbuild	^0.17.1 || ^0.18.0 || ^0.19.0 || ^0.20.0 || ^0.21.0 || ^0.22.0 || ^0.23.0 -> ^0.17.1 || ^0.18.0 || ^0.19.0 || ^0.20.0 || ^0.21.0 || ^0.22.0 || ^0.23.0 || ^0.24.0
esbuild	0.23.1 -> 0.24.0
nodemon (source)	3.1.4 -> 3.1.7
pino-loki	2.3.0 -> 2.3.1

---

Release Notes

biomejs/biome (@​biomejs/biome)

v1.9.2

Compare Source

CLI

New features

• Added support for custom GritQL definitions, including:

  • Pattern and predicate definitions: https://docs.grit.io/guides/patterns
  • Function definitions: https://docs.grit.io/language/functions#function-definitions

  Contributed by @​arendjr

Bug fixes

• Fix #​3917, where the fixed files were incorrectly computed. Contributed by @​ematipico
• Fixed an issue that caused GritQL contains queries to report false positives when the matched
  node appeared inside a sibling node. Contributed by @​arendjr

Editors

Bug fixes

• Fix #​3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered.
  Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

• Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @​ematipico

• Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

  This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

  Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

  Contributed by @​ematipico

Linter

New features

• Add nursery/noMissingVarFunction. Contributed by @​michellocana
• Add [nursery/useComponentExportOnlyModules]((https://biomejs.dev/linter/rules/use-component-export-only-modules). Use this rule in React projects to enforce a code styling that fits React Refresh. Contributed by @​GunseiKPaseri

Bug fixes

• noLabelWithoutControl now accept JSX expression as label value (#​3875). Contributed by @​Conaclos

• useFilenamingConvention no longer suggests names with a disallowed case (#​3952). Contributed by @​Conaclos

• useFilenamingConvention now recognizes file names starting with ASCII digits as lowercase (#​3952).

  Thus, 2024-09-17-filename, 2024_09_17_filename and 20240917FileName are in kebab-case, snake_case, and camelCase respectively.

  Contributed by @​Conaclos

• useFilenamingConvention now applies the configured formats to the file extensions (#​3650). Contributed by @​Conaclos

Parser

Bug fixes

• useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @​Conaclos

• The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @​Conaclos

evanw/esbuild (esbuild)

v0.24.0

Compare Source

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.

remy/nodemon (nodemon)

v3.1.7

Compare Source

v3.1.6

Compare Source

Bug Fixes

• watch nested paths (11fcaaa), closes #​2216

v3.1.5

Compare Source

Julien-R44/pino-loki (pino-loki)

v2.3.1: Move from got to native fetch

Compare Source

What's Changed

• refactor: replaced Got HTTP client with native fetch by @​TedCha in https://github.com/Julien-R44/pino-loki/pull/34

New Contributors

• @​TedCha made their first contribution in https://github.com/Julien-R44/pino-loki/pull/34

Full Changelog: Julien-R44/pino-loki@v2.3.0...v2.3.1

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (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 was generated by Mend Renovate. View the repository job log.