fix(deps): update devdependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@commitlint/cli (source)	^17.4.2 -> ^17.4.3
@commitlint/config-conventional (source)	^17.4.2 -> ^17.4.3
@sanity/pkg-utils	^2.2.3 -> ^2.2.5
@types/node (source)	^18.11.18 -> ^18.13.0
@typescript-eslint/eslint-plugin	^5.50.0 -> ^5.52.0
@typescript-eslint/parser	^5.50.0 -> ^5.52.0
esbuild	^0.17.5 -> ^0.17.8
eslint (source)	^8.33.0 -> ^8.34.0
jest (source)	^29.4.1 -> ^29.4.2
lint-staged	^13.1.0 -> ^13.1.2
prettier (source)	^2.8.3 -> ^2.8.4

---

Release Notes

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

v17.4.3

Compare Source

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

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

v17.4.3

Compare Source

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

sanity-io/pkg-utils

v2.2.5

Compare Source

Bug Fixes

• deps: update dependencies (non-major) (#​58) (470b773)

v2.2.4

Compare Source

Bug Fixes

• deps: update dependencies (non-major) (#​54) (b57cb36)

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

v5.52.0

Compare Source

Bug Fixes

• eslint-plugin: [no-import-type-side-effects] correctly ignore zero-specifier imports (#​6444) (d5a6688)
• eslint-plugin: [no-unnecessary-condition] account for optional chaining on potentially void values (#​6432) (e1d9c67), closes #​5255
• eslint-plugin: [no-unnecessary-condition] fix false positive when checking indexed access types (#​6452) (d569924)
• eslint-plugin: fix key-spacing when type starts on next line (#​6412) (3eb2eed)

Features

• eslint-plugin: [block-spacing] extending base rule for TS related blocks (#​6195) (b2db3f5)
• eslint-plugin: [explicit-function-return-type] add allowFunctionsWithoutTypeParameters option (#​6105) (113640e)
• eslint-plugin: [explicit-function-return-type] add allowIIFEs option (#​6237) (a1b3f7b)

v5.51.0

Compare Source

Bug Fixes

• eslint-plugin: [sort-type-constituents] fixed behavior change (#​6384) (5bf7f7f), closes #​6339
• eslint-plugin: do not use .at(), Node 14 does not support it (#​6402) (077ed1b)

Features

• eslint-plugin: [naming-convention] improve performance by removing unnecessary selectors (#​6376) (3647a1c)
• eslint-plugin: [no-floating-promises] error on logical expression (#​6356) (f330e06)
• eslint-plugin: [no-import-type-side-effects] add rule to warn against runtime side effects with verbatimModuleSyntax (#​6394) (b14d3be)
• eslint-plugin: [strict-boolean-expressions] add allow nullable enum to strict boolean expressions (#​6096) (d4747cd)

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

v5.52.0

Compare Source

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

v5.51.0

Compare Source

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

evanw/esbuild

v0.17.8

Compare Source

• Fix a minification bug with non-ASCII identifiers (#​2910)

  This release fixes a bug with esbuild where non-ASCII identifiers followed by a keyword were incorrectly not separated by a space. This bug affected both the in and instanceof keywords. Here's an example of the fix:

  // Original code
  π in a
  
  // Old output (with --minify --charset=utf8)
  πin a;
  
  // New output (with --minify --charset=utf8)
  π in a;

• Fix a regression with esbuild's WebAssembly API in version 0.17.6 (#​2911)

  Version 0.17.6 of esbuild updated the Go toolchain to version 1.20.0. This had the unfortunate side effect of increasing the amount of stack space that esbuild uses (presumably due to some changes to Go's WebAssembly implementation) which could cause esbuild's WebAssembly-based API to crash with a stack overflow in cases where it previously didn't crash. One such case is the package grapheme-splitter which contains code that looks like this:

  if (
    (0x0300 <= code && code <= 0x036F) ||
    (0x0483 <= code && code <= 0x0487) ||
    (0x0488 <= code && code <= 0x0489) ||
    (0x0591 <= code && code <= 0x05BD) ||
    // ... many hundreds of lines later ...
  ) {
    return;
  }

  This edge case involves a chain of binary operators that results in an AST over 400 nodes deep. Normally this wouldn't be a problem because Go has growable call stacks, so the call stack would just grow to be as large as needed. However, WebAssembly byte code deliberately doesn't expose the ability to manipulate the stack pointer, so Go's WebAssembly translation is forced to use the fixed-size WebAssembly call stack. So esbuild's WebAssembly implementation is vulnerable to stack overflow in cases like these.

  It's not unreasonable for this to cause a stack overflow, and for esbuild's answer to this problem to be "don't write code like this." That's how many other AST-manipulation tools handle this problem. However, it's possible to implement AST traversal using iteration instead of recursion to work around limited call stack space. This version of esbuild implements this code transformation for esbuild's JavaScript parser and printer, so esbuild's WebAssembly implementation is now able to process the grapheme-splitter package (at least when compiled with Go 1.20.0 and run with node's WebAssembly implementation).

v0.17.7

Compare Source

• Change esbuild's parsing of TypeScript instantiation expressions to match TypeScript 4.8+ (#​2907)

  This release updates esbuild's implementation of instantiation expression erasure to match microsoft/TypeScript#​49353. The new rules are as follows (copied from TypeScript's PR description):

  When a potential type argument list is followed by

  • a line break,
  • an ( token,
  • a template literal string, or
  • any token except < or > that isn't the start of an expression,

  we consider that construct to be a type argument list. Otherwise we consider the construct to be a < relational expression followed by a > relational expression.

• Ignore sideEffects: false for imported CSS files (#​1370, #​1458, #​2905)

  This release ignores the sideEffects annotation in package.json for CSS files that are imported into JS files using esbuild's css loader. This means that these CSS files are no longer be tree-shaken.

  Importing CSS into JS causes esbuild to automatically create a CSS entry point next to the JS entry point containing the bundled CSS. Previously packages that specified some form of "sideEffects": false could potentially cause esbuild to consider one or more of the JS files on the import path to the CSS file to be side-effect free, which would result in esbuild removing that CSS file from the bundle. This was problematic because the removal of that CSS is outwardly observable, since all CSS is global, so it was incorrect for previous versions of esbuild to tree-shake CSS files imported into JS files.

• Add constant folding for certain additional equality cases (#​2394, #​2895)

  This release adds constant folding for expressions similar to the following:

  // Original input
  console.log(
    null === 'foo',
    null === undefined,
    null == undefined,
    false === 0,
    false == 0,
    1 === true,
    1 == true,
  )
  
  // Old output
  console.log(
    null === "foo",
    null === void 0,
    null == void 0,
    false === 0,
    false == 0,
    1 === true,
    1 == true
  );
  
  // New output
  console.log(
    false,
    false,
    true,
    false,
    true,
    false,
    true
  );

v0.17.6

Compare Source

• Fix a CSS parser crash on invalid CSS (#​2892)

  Previously the following invalid CSS caused esbuild's parser to crash:

  @​media screen

  The crash was caused by trying to construct a helpful error message assuming that there was an opening { token, which is not the case here. This release fixes the crash.

• Inline TypeScript enums that are referenced before their declaration

  Previously esbuild inlined enums within a TypeScript file from top to bottom, which meant that references to TypeScript enum members were only inlined within the same file if they came after the enum declaration. With this release, esbuild will now inline enums even when they are referenced before they are declared:

  // Original input
  export const foo = () => Foo.FOO
  const enum Foo { FOO = 0 }
  
  // Old output (with --tree-shaking=true)
  export const foo = () => Foo.FOO;
  var Foo = /* @​__PURE__ */ ((Foo2) => {
    Foo2[Foo2["FOO"] = 0] = "FOO";
    return Foo2;
  })(Foo || {});
  
  // New output (with --tree-shaking=true)
  export const foo = () => 0 /* FOO */;

  This makes esbuild's TypeScript output smaller and faster when processing code that does this. I noticed this issue when I ran the TypeScript compiler's source code through esbuild's bundler. Now that the TypeScript compiler is going to be bundled with esbuild in the upcoming TypeScript 5.0 release, improvements like this will also improve the TypeScript compiler itself!

• Fix esbuild installation on Arch Linux (#​2785, #​2812, #​2865)

  Someone made an unofficial esbuild package for Linux that adds the ESBUILD_BINARY_PATH=/usr/bin/esbuild environment variable to the user's default environment. This breaks all npm installations of esbuild for users with this unofficial Linux package installed, which has affected many people. Most (all?) people who encounter this problem haven't even installed this unofficial package themselves; instead it was installed for them as a dependency of another Linux package. The problematic change to add the ESBUILD_BINARY_PATH environment variable was reverted in the latest version of this unofficial package. However, old versions of this unofficial package are still there and will be around forever. With this release, ESBUILD_BINARY_PATH is now ignored by esbuild's install script when it's set to the value /usr/bin/esbuild. This should unbreak using npm to install esbuild in these problematic Linux environments.

  Note: The ESBUILD_BINARY_PATH variable is an undocumented way to override the location of esbuild's binary when esbuild's npm package is installed, which is necessary to substitute your own locally-built esbuild binary when debugging esbuild's npm package. It's only meant for very custom situations and should absolutely not be forced on others by default, especially without their knowledge. I may remove the code in esbuild's installer that reads ESBUILD_BINARY_PATH in the future to prevent these kinds of issues. It will unfortunately make debugging esbuild harder. If ESBUILD_BINARY_PATH is ever removed, it will be done in a "breaking change" release.

eslint/eslint

v8.34.0

Compare Source

Features

• 9b2fcf7 feat: array-callback-return supports Array.prototype.toSorted (#​16845) (SUZUKI Sosuke)

Bug Fixes

• 923f61d fix: false positive with assignment in no-extra-parens (#​16872) (Francesco Trotta)

Documentation

• f0a9883 docs: split rules documentation (#​16797) (Ben Perlmutter)
• 67aa37b docs: fix typo in command-line-interface.md (#​16871) (Kevin Rouchut)
• 337f7ed docs: fix width of language input (#​16849) (Tanuj Kanti)
• 71349a1 docs: Configure a Parser page (#​16803) (Ben Perlmutter)
• de7e925 docs: remove extra line numbers in example (#​16848) (jonz94)
• ad38d77 docs: Update README (GitHub Actions Bot)

Chores

• 9dbe06d chore: add type property to array-element-newline schema (#​16877) (MHO)
• a061527 chore: Remove unused functions (#​16868) (Nicholas C. Zakas)

facebook/jest

v29.4.2

Compare Source

Features

• [@jest/core] Instrument significant lifecycle events with performance.mark() (#​13859)

Fixes

• [expect, @​jest/expect] Provide type of actual as a generic argument to Matchers to allow better-typed extensions (#​13848)
• [jest-circus] Added explicit mention of test failing because done() is not being called in error message (#​13847)
• [jest-runtime] Handle CJS re-exports of node core modules from ESM (#​13856)
• [jest-transform] Downgrade write-file-atomic to v4 (#​13853)
• [jest-worker] Ignore IPC messages not intended for Jest (#​13543)

Chore & Maintenance

• [*] make sure to exclude .eslintcache from published module (#​13832)
• [docs] Cleanup incorrect links in CHANGELOG.md (#​13857)

okonet/lint-staged

v13.1.2

Compare Source

Bug Fixes

• disable stash by default when using diff option (#​1259) (142c6f2)

v13.1.1

Compare Source

Bug Fixes

• allow re-enabling --stash when using the --diff option (99390c3)

prettier/prettier

v2.8.4

Compare Source

diff

Fix leading comments in mapped types with readonly (#​13427 by @​thorn0, @​sosukesuzuki)

// Input
type Type = {
  // comment
  readonly [key in Foo];
};

// Prettier 2.8.3
type Type = {
  readonly // comment
  [key in Foo];
};

// Prettier 2.8.4
type Type = {
  // comment
  readonly [key in Foo];
};

Group params in opening block statements (#​14067 by @​jamescdavis)

This is a follow-up to #​13930 to establish wrapping consistency between opening block statements and else blocks by
grouping params in opening blocks. This causes params to break to a new line together and not be split across lines
unless the length of params exceeds the print width. This also updates the else block wrapping to behave exactly the
same as opening blocks.

{{! Input }}
{{#block param param param param param param param param param param as |blockParam|}}
  Hello
{{else block param param param param param param param param param param as |blockParam|}}
  There
{{/block}}

{{! Prettier 2.8.3 }}
{{#block
  param
  param
  param
  param
  param
  param
  param
  param
  param
  param
  as |blockParam|
}}
  Hello
{{else block param
param
param
param
param
param
param
param
param
param}}
  There
{{/block}}

{{! Prettier 2.8.4 }}
{{#block
  param param param param param param param param param param
  as |blockParam|
}}
  Hello
{{else block
  param param param param param param param param param param
  as |blockParam|
}}
  There
{{/block}}

Ignore files in .sl/ (#​14206 by @​bolinfest)

In Sapling SCM, .sl/ is the folder where it stores its state, analogous to .git/ in Git. It should be ignored in Prettier like the other SCM folders.

Recognize @satisfies in Closure-style type casts (#​14262 by @​fisker)

// Input
const a = /** @&#8203;satisfies {Record<string, string>} */ ({hello: 1337});
const b = /** @&#8203;type {Record<string, string>} */ ({hello: 1337});

// Prettier 2.8.3
const a = /** @&#8203;satisfies {Record<string, string>} */ { hello: 1337 };
const b = /** @&#8203;type {Record<string, string>} */ ({ hello: 1337 });

// Prettier 2.8.4
const a = /** @&#8203;satisfies {Record<string, string>} */ ({hello: 1337});
const b = /** @&#8203;type {Record<string, string>} */ ({hello: 1337});

Fix parens in inferred function return types with extends (#​14279 by @​fisker)

// Input
type Foo<T> = T extends ((a) => a is infer R extends string) ? R : never;

// Prettier 2.8.3 (First format)
type Foo<T> = T extends (a) => a is infer R extends string ? R : never;

// Prettier 2.8.3 (Second format)
SyntaxError: '?' expected. 

// Prettier 2.8.4
type Foo<T> = T extends ((a) => a is infer R extends string) ? R : never;

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), 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 using a preset from . View repository job log here

[github-actions]

🎉 This PR is included in version 2.2.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀