chore(deps): update non-major

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sanity/pkg-utils	^4.1.0 -> ^4.2.4
@typescript-eslint/eslint-plugin (source)	^6.19.1 -> ^6.21.0
@typescript-eslint/parser (source)	^6.19.1 -> ^6.21.0
esbuild	^0.19.12 -> ^0.20.1
prettier (source)	^3.2.4 -> ^3.2.5
prettier-plugin-packagejson	^2.4.9 -> ^2.4.11

---

Release Notes

sanity-io/pkg-utils (@​sanity/pkg-utils)

v4.2.4

Compare Source

Bug Fixes

• deps: update dependency @​microsoft/api-extractor to ^7.40.2 (#​504) (e66b744)
• deps: update dependency @​microsoft/api-extractor to ^7.40.3 (#​508) (df20db0)
• deps: update dependency @​sanity/browserslist-config to ^1.0.2 (d58beee)
• deps: update dependency esbuild to ^0.20.1 (#​509) (f062233)

v4.2.3

Compare Source

Bug Fixes

• deps: update dependency prettier-plugin-packagejson to ^2.4.11 (#​497) (e938910)

v4.2.2

Compare Source

Bug Fixes

• deps: update dependency astro to ^4.3.6 (#​485) (3c9cc66)
• deps: update dependency browserslist to ^4.23.0 (#​492) (22078df)
• deps: update dependency rollup to ^4.11.0 (#​493) (c01619f)

v4.2.0

Compare Source

Features

• improve treeshaking (#​463) (91831a3)

v4.1.5

Compare Source

Bug Fixes

• deps: update dependency @​microsoft/api-extractor to ^7.40.1 (#​470) (566c8b9)

v4.1.4

Compare Source

Bug Fixes

• deps: update dependency @​microsoft/api-extractor to ^7.40.0 (#​464) (f2af378)
• deps: update dependency @​sanity/browserslist-config to ^1.0.1 (#​468) (95d28f2)
• deps: update dependency chokidar to ^3.6.0 (#​465) (ec07deb)

v4.1.3

Compare Source

Bug Fixes

• deps: update dependency @​microsoft/api-extractor to ^7.39.5 (#​459) (7cbb1ec)

v4.1.2

Compare Source

Bug Fixes

• deps: update dependency prettier-plugin-packagejson to ^2.4.10 (#​446) (269ca72)

v4.1.1

Compare Source

Bug Fixes

• deps: update dependency browserslist to ^4.22.3 (#​438) (82de0e7)
• deps: update dependency esbuild to ^0.20.0 (#​439) (679c7c9)

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

v6.21.0

Compare Source

🚀 Features

• export plugin metadata

• allow parserOptions.project: false

• eslint-plugin: add rule prefer-find

🩹 Fixes

• eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression

• eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values

• eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions

• eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option

• eslint-plugin: [class-literal-property-style] allow getter when same key setter exists

• eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before as keyword

❤️ Thank You

• auvred
• Brad Zacher
• Kirk Waiblinger
• Pete Gonzalez
• YeonJuan

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

v6.20.0

Compare Source

🚀 Features

• eslint-plugin: [member-ordering] allow easy reuse of the default ordering

🩹 Fixes

• eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result

• eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable

• eslint-plugin: [no-useless-template-literals] report Infinity & NaN

• eslint-plugin: [prefer-readonly] disable checking accessors

❤️ Thank You

• Alex Parloti
• auvred
• James Browning
• StyleShit
• YeonJuan

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

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

v6.21.0

Compare Source

🚀 Features

• allow parserOptions.project: false

❤️ Thank You

• auvred
• Brad Zacher
• Kirk Waiblinger
• Pete Gonzalez
• YeonJuan

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

v6.20.0

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.

evanw/esbuild (esbuild)

v0.20.1

Compare Source

• Fix a bug with the CSS nesting transform (#​3648)

  This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:

  /* Original code */
  .foo {
    &:after,
    & .bar {
      color: red;
    }
  }
  
  /* Old output (with --supported:nesting=false) */
  .foo .bar,
  .foo .bar {
    color: red;
  }
  
  /* New output (with --supported:nesting=false) */
  .foo:after,
  .foo .bar {
    color: red;
  }

• Constant folding for JavaScript inequality operators (#​3645)

  This release introduces constant folding for the < > <= >= operators. The minifier will now replace these operators with true or false when both sides are compile-time numeric or string constants:

  // Original code
  console.log(1 < 2, '🍕' > '🧀')
  
  // Old output (with --minify)
  console.log(1<2,"🍕">"🧀");
  
  // New output (with --minify)
  console.log(!0,!1);

• Better handling of __proto__ edge cases (#​3651)

  JavaScript object literal syntax contains a special case where a non-computed property with a key of __proto__ sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:

  // Original code
  function foo(__proto__) {
    return { __proto__: __proto__ } // Note: sets the prototype
  }
  function bar(__proto__, proto) {
    {
      let __proto__ = proto
      return { __proto__ } // Note: doesn't set the prototype
    }
  }
  
  // Old output
  function foo(__proto__) {
    return { __proto__ }; // Note: no longer sets the prototype (WRONG)
  }
  function bar(__proto__, proto) {
    {
      let __proto__2 = proto;
      return { __proto__: __proto__2 }; // Note: now sets the prototype (WRONG)
    }
  }
  
  // New output
  function foo(__proto__) {
    return { __proto__: __proto__ }; // Note: sets the prototype (correct)
  }
  function bar(__proto__, proto) {
    {
      let __proto__2 = proto;
      return { ["__proto__"]: __proto__2 }; // Note: doesn't set the prototype (correct)
    }
  }

• Fix cross-platform non-determinism with CSS color space transformations (#​3650)

  The Go compiler takes advantage of "fused multiply and add" (FMA) instructions on certain processors which do the operation x*y + z without intermediate rounding. This causes esbuild's CSS color space math to differ on different processors (currently ppc64le and s390x), which breaks esbuild's guarantee of deterministic output. To avoid this, esbuild's color space math now inserts a float64() cast around every single math operation. This tells the Go compiler not to use the FMA optimization.

• Fix a crash when resolving a path from a directory that doesn't exist (#​3634)

  This release fixes a regression where esbuild could crash when resolving an absolute path if the source directory for the path resolution operation doesn't exist. While this situation doesn't normally come up, it could come up when running esbuild concurrently with another operation that mutates the file system as esbuild is doing a build (such as using git to switch branches). The underlying problem was a regression that was introduced in version 0.18.0.

v0.20.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.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

• Work around API deprecations in Deno 1.40.x (#​3609, #​3611)

  Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

  Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

• Reorder implicit file extensions within node_modules (#​3341, #​3608)

  In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

  With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

  Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

prettier/prettier (prettier)

v3.2.5

Compare Source

diff

Support Angular inline styles as single template literal (#​15968 by @​sosukesuzuki)

Angular v17 supports single string inline styles.

// Input
@​Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.4
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.5
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `
    h1 {
      color: blue;
    }
  `,
})
export class AppComponent {}

Unexpected embedded formatting for Angular template (#​15969 by @​JounQin)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";

@​Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.4
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.5
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

Use "json" parser for tsconfig.json by default (#​16012 by @​sosukesuzuki)

In v2.3.0, we introduced "jsonc" parser which adds trialing comma by default.

When adding a new parser we also define how it will be used based on the linguist-languages data.

tsconfig.json is a special file used by TypeScript, it uses .json file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing .json file extension.

We decide to treat it as a JSON file for now to avoid the extra configuration step.

To keep using the "jsonc" parser for your tsconfig.json files, add the following to your .pretterrc file

{
  "overrides": [
    {
      "files": ["tsconfig.json", "jsconfig.json"],
      "options": {
        "parser": "jsonc"
      }
    }
  ]
}

matzkoh/prettier-plugin-packagejson (prettier-plugin-packagejson)

v2.4.11

Compare Source

Bug Fixes

• .js to .cjs for compatibility with { "type": "module" } (ac3a006)

v2.4.10

Compare Source

Bug Fixes

• deps: update dependency sort-package-json to v2.7.0 (0d520e3)

---

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 curated preset maintained by . View repository job log here

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/[email protected]	filesystem Transitive: environment, eval, network, shell, unsafe	+264	313 MB	sanity-io
npm/@typescript-eslint/[email protected]	Transitive: environment, eval, filesystem, shell, unsafe	+114	15 MB	jameshenry
npm/@typescript-eslint/[email protected]	Transitive: environment, eval, filesystem, shell, unsafe	+109	11.9 MB	jameshenry
npm/[email protected]	environment, filesystem, network, shell	+23	224 MB	evanw
npm/[email protected]	Transitive: environment, filesystem, unsafe	+30	9.05 MB	matzkoh
npm/[email protected]	environment, filesystem, unsafe	0	8.39 MB	prettier-bot

🚮 Removed packages: npm/@sanity/[email protected], npm/@typescript-eslint/[email protected], npm/@typescript-eslint/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎