Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/preset-env (source)	^7.24.6 -> ^7.24.7
@typescript-eslint/eslint-plugin (source)	^7.11.0 -> ^7.14.1
@typescript-eslint/parser (source)	^7.11.0 -> ^7.14.1
esbuild	^0.21.5 -> ^0.22.0
eslint-plugin-jest	^28.5.0 -> ^28.6.0
prettier (source)	^3.2.5 -> ^3.3.2
ts-jest (source)	^29.1.4 -> ^29.1.5
tslib (source)	^2.6.2 -> ^2.6.3
typescript (source)	^5.4.5 -> ^5.5.2
zx	^8.1.2 -> ^8.1.3

---

Release Notes

babel/babel (@​babel/preset-env)

v7.24.7

Compare Source

🐛 Bug Fix

• babel-node
  • #​16554 Allow extra flags in babel-node (@​nicolo-ribaudo)
• babel-traverse
  • #​16522 fix: incorrect constantViolations with destructuring (@​liuxingbaoyu)
• babel-helper-transform-fixture-test-runner, babel-plugin-proposal-explicit-resource-management
  • #​16524 fix: Transform using in switch correctly (@​liuxingbaoyu)

🏠 Internal

• babel-helpers, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • #​16525 Delete unused array helpers (@​blakewilson)

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

v7.14.1

Compare Source

🩹 Fixes

• eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types

• eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens

❤️ Thank You

• Jake Bailey

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

v7.14.0

Compare Source

🚀 Features

• support TypeScript 5.5

🩹 Fixes

• eslint-plugin: [no-extraneous-class] handle abstract members

• eslint-plugin: [prefer-nullish-coalescing] handle intersected primitive types

• eslint-plugin: [no-invalid-this] support AccessorProperty

❤️ Thank You

• Brad Zacher
• cm-ayf
• Jake Bailey
• James Zhan
• Joshua Chen
• yoshi2no

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

v7.13.1

Compare Source

🩹 Fixes

• eslint-plugin: [prefer-readonly] refine report locations

• eslint-plugin: [return-await] support explicit resource management

• eslint-plugin: [no-unsafe-member-access] differentiate a types-error any from a true any

❤️ Thank You

• Kirk Waiblinger
• Yukihiro Hasegawa

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

v7.13.0

Compare Source

🚀 Features

• typescript-estree: require import = require() argument to be a string literal

• typescript-estree: forbid .body, .async, .generator on declare function

• eslint-plugin: [no-dynamic-delete] allow all string literals as index

🩹 Fixes

• ast-spec: function-call-like callee should be Expression not LeftHandSideExpression

• scope-manager: handle index signature in class

• eslint-plugin: [init-declarations] refine report locations

• eslint-plugin: [no-base-to-string] make error message more nuanced

• eslint-plugin: [no-unsafe-assignment] be more specific about error types

• eslint-plugin: [no-magic-numbers] fix implementation of the ignore option

❤️ Thank You

• Fotis Papadogeorgopoulos
• Joshua Chen
• Kirk Waiblinger
• Tobiloba Adedeji
• Vinccool96
• YeonJuan

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

v7.12.0

Compare Source

🚀 Features

• eslint-plugin: [no-useless-template-literals] rename to no-useless-template-expression (deprecate no-useless-template-literals)

• rule-tester: check for parsing errors in suggestion fixes

• rule-tester: port checkDuplicateTestCases from ESLint

• eslint-plugin: [no-floating-promises] add option 'allowForKnownSafePromises'

🩹 Fixes

• no-useless-template-expression -> no-unnecessary-template-expression

• eslint-plugin: [no-unnecessary-type-assertion] combine template literal check with const variable check

• eslint-plugin: [dot-notation] fix false positive when accessing private/protected property with optional chaining

• eslint-plugin: [explicit-member-accessibility] refine report locations

• eslint-plugin: [no-unnecessary-type-assertion] declares are always defined, so always check declares

• eslint-plugin: [prefer-literal-enum-member] allow using member it self on allowBitwiseExpressions

• eslint-plugin: [return-await] clean up in-try-catch detection and make autofixes safe

• eslint-plugin: [member-ordering] also TSMethodSignature can be get/set

❤️ Thank You

• Abraham Guo
• Han Yeong-woo
• Joshua Chen
• Kim Sang Du
• Kirk Waiblinger
• YeonJuan

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

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

v7.14.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

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

v7.14.0

Compare Source

🚀 Features

• support TypeScript 5.5

❤️ Thank You

• Brad Zacher
• cm-ayf
• Jake Bailey
• James Zhan
• Joshua Chen
• yoshi2no

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

v7.13.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

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

v7.13.0

Compare Source

🚀 Features

• parser, typescript-estree: export withoutProjectParserOptions utility

❤️ Thank You

• Fotis Papadogeorgopoulos
• Joshua Chen
• Kirk Waiblinger
• Tobiloba Adedeji
• Vinccool96
• YeonJuan

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

v7.12.0

Compare Source

🩹 Fixes

• types: correct typing ParserOptions

❤️ Thank You

• Abraham Guo
• Han Yeong-woo
• Joshua Chen
• Kim Sang Du
• Kirk Waiblinger
• YeonJuan

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

evanw/esbuild (esbuild)

v0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.

• Omit packages from bundles by default when targeting node (#​1874, #​2830, #​2846, #​2915, #​3145, #​3294, #​3323, #​3582, #​3809, #​3815)

  This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

  With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

  The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

• Drop support for older platforms (#​3802)

  This release drops support for the following operating systems:

  • Windows 7
  • Windows 8
  • Windows Server 2008
  • Windows Server 2012

  This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

  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.21). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild.exe --version
  

  In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).

• Update await using behavior to match TypeScript

  TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

• Allow es2024 as a target environment

  The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

• Publish binaries for OpenBSD on 64-bit ARM (#​3665, #​3674)

  With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

  This was contributed by @​ikmckenz.

• Publish binaries for WASI (WebAssembly System Interface) preview 1 (#​3300, #​3779)

  The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a .wasm file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).

  Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.

  This release publishes esbuild precompiled for WASI preview 1 to the @esbuild/wasi-preview1 package on npm (specifically the file @esbuild/wasi-preview1/esbuild.wasm). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.

• Warn about onResolve plugins not setting a path (#​3790)

  Plugins that return values from onResolve without resolving the path (i.e. without setting either path or external: true) will now cause a warning. This is because esbuild only uses return values from onResolve if it successfully resolves the path, and it's not good for invalid input to be silently ignored.

• Add a new Go API for running the CLI with plugins (#​3539)

  With esbuild's Go API, you can now call cli.RunWithPlugins(args, plugins) to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.

  This was contributed by @​edewit.

jest-community/eslint-plugin-jest (eslint-plugin-jest)

v28.6.0

Compare Source

Features

• prefer-jest-mocked: add new rule (#​1599) (4b6a4f2)
• valid-expect: supporting automatically fixing adding async in some cases (#​1579) (5b9b47e)

prettier/prettier (prettier)

v3.3.2

Compare Source

diff

Fix handlebars path expressions starts with @ (#​16358 by @​Princeyadav05)

{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>

v3.3.1

Compare Source

diff

Preserve empty lines in front matter (#​16347 by @​fisker)

<!-- Input -->
---
foo:
  - bar1

  - bar2

  - bar3
---
Markdown

<!-- Prettier 3.3.0 -->

---
foo:
  - bar1
  - bar2
  - bar3
---

Markdown

<!-- Prettier 3.3.1 -->
---
foo:
  - bar1

  - bar2

  - bar3
---

Markdown

Preserve explicit language in front matter (#​16348 by @​fisker)

<!-- Input -->
---yaml
title: Hello
slug: home
---

<!-- Prettier 3.3.0 -->
---
title: Hello
slug: home
---

<!-- Prettier 3.3.1 -->
---yaml
title: Hello
slug: home
---

Avoid line breaks in import attributes (#​16349 by @​fisker)

// Input
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

// Prettier 3.3.0
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type:
  "json" };

// Prettier 3.3.1
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

v3.3.0

Compare Source

diff

🔗 Release Notes

kulshekhar/ts-jest (ts-jest)

v29.1.5

Compare Source

Bug Fixes

• build(deps-dev): bump braces (5560334), (59026b4), (0d9e359)

Microsoft/tslib (tslib)

v2.6.3

Compare Source

What's Changed

• 'await using' normative changes by @​rbuckton in https://github.com/microsoft/tslib/pull/258

Full Changelog: microsoft/tslib@v2.6.2...v2.6.3

Microsoft/TypeScript (typescript)

v5.5.2

Compare Source

google/zx (zx)

v8.1.3

Compare Source

Nothing special today. We just keep improving the implementation.

Features

• ESM support is now available for Node.js v12 (previously was cjs only):
  ^{#​824, #​827, #​828}

import {$} from 'zx'

• zx/cli exports its inners to allow more advanced usage.
  Imagine, your own CLI tool that uses zx as a base:
  ^#​828

#!/usr/bin/env node

import './index.mjs'
import {main} from 'zx/cli'

main()

• Provide intermediate store configuration for fine-grained control of memory usage.
  ^{#​650, #​849}

const getFixedSizeArray = (size) => {
  const arr = []
  return new Proxy(arr, {
    get: (target, prop) =>
      prop === 'push' && arr.length >= size
        ? () => {}
        : target[prop],
  })
}
const store = {
  stdout: getFixedSizeArray(1),
  stderr: getFixedSizeArray(1),
  stdall: getFixedSizeArray(0),
}

const p = await $({ store })`echo foo`

p.stdout.trim() //  'foo'
p.toString()    // ''

• Introduced sync methods for ps:
  ^#​840

import { ps } from 'zx'

const list1 = await ps()
const list2 = await tree()

// new methods
const list3 = ps.sync()
const list4 = tree.sync()

Chore

• $.log accepts kind: 'custom' #​834
• Describe $.verbose and $.quiet modes internals #​835
• Mention quotePowerShell in docs #​851
• Finally fixed the annoying flaky problem of the process end detection in Bun #​839, coderef
• Suppress async_hooks.createHook warning on bun #​848
• Remove node-abort-controller in favor of built-in node-fetch polyfill #​842
• Add missing global types #​853

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Europe/Berlin, 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.

[github-actions]

Metrics report

At head commit 9083341 and base commit 93a2b78 at 2024-06-30T22:10:02.659Z

Size

No changes

All size metrics

Export	Size original	Size minified	Size minified and Brotli compressed
tailwind-merge esm	71.96 kB 0%	20.75 kB 0%	5.80 kB 0%
› createTailwindMerge	12.44 kB 0%	3.65 kB 0%	1.37 kB 0%
› extendTailwindMerge	71.47 kB 0%	20.32 kB 0%	5.63 kB 0%
› fromTheme	0.15 kB 0%	0.08 kB 0%	0.08 kB 0%
› getDefaultConfig	57.49 kB 0%	16.20 kB 0%	4.17 kB 0%
› mergeConfigs	1.32 kB 0%	0.40 kB 0%	0.20 kB 0%
› twJoin	1.06 kB 0%	0.26 kB 0%	0.16 kB 0%
› twMerge	69.96 kB 0%	19.86 kB 0%	5.46 kB 0%
› validators	3.21 kB 0%	1.54 kB 0%	0.66 kB 0%
tailwind-merge cjs	72.22 kB 0%	23.81 kB 0%	6.11 kB 0%
tailwind-merge/es5 esm	74.72 kB 0%	21.70 kB 0%	6.00 kB 0%
› createTailwindMerge	14.02 kB 0%	4.17 kB 0%	1.53 kB 0%
› extendTailwindMerge	74.04 kB 0%	21.28 kB 0%	5.87 kB 0%
› fromTheme	0.19 kB 0%	0.10 kB 0%	0.09 kB 0%
› getDefaultConfig	58.06 kB 0%	16.46 kB 0%	4.18 kB 0%
› mergeConfigs	1.52 kB 0%	0.43 kB 0%	0.22 kB 0%
› twJoin	1.06 kB 0%	0.25 kB 0%	0.15 kB 0%
› twMerge	72.10 kB 0%	20.65 kB 0%	5.66 kB 0%
› validators	3.37 kB 0%	1.53 kB 0%	0.66 kB 0%
tailwind-merge/es5 cjs	74.98 kB 0%	24.79 kB 0%	6.31 kB 0%

[github-actions]

This was addressed in release v2.4.0.