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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	^22.10.1 -> ^22.10.2
@types/react (source)	^18.3.12 -> ^18.3.18
@types/react-dom (source)	^18.3.1 -> ^18.3.5
crossws	^0.2.4 -> ^0.3.1
esbuild	^0.24.0 -> ^0.24.2
eslint (source)	^9.16.0 -> ^9.17.0
express (source)	^4.21.1 -> ^4.21.2
jiti	^2.4.1 -> ^2.4.2
mitata	^1.0.20 -> ^1.0.21
pnpm (source)	9.14.4 -> 9.15.1
prettier (source)	^3.4.1 -> ^3.4.2
unbuild	3.0.0-rc.11 -> 3.0.1
undocs	^0.2.26 -> ^0.2.30
zod (source)	^3.23.8 -> ^3.24.1

---

Release Notes

unjs/crossws (crossws)

v0.3.1

Compare Source

compare changes

🩹 Fixes

• types: AdapterOptions type (#​80)

🏡 Chore

• release: V0.3.0 (4a5e168)
• Update deps (567c9fe)
• Update changelog (1f5411a)

❤️ Contributors

• Pooya Parsa (@​pi0)
• Hayatosc (@​hayatosc)

v0.3.0

Compare Source

compare changes

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. ⚠️

eslint/eslint (eslint)

v9.17.0

Compare Source

expressjs/express (express)

v4.21.2

Compare Source

unjs/jiti (jiti)

v2.4.2

Compare Source

compare changes

🩹 Fixes

• cache: Add +map suffix to fs entries when sourceMaps enabled (#​352)
• Use native require cache of loaded entries only (#​348)

🏡 Chore

• Update deps (7b7ffef)

✅ Tests

• Simplify snapshot tests (#​351)

❤️ Contributors

• Pooya Parsa (@​pi0)

evanwashere/mitata (mitata)

v1.0.21

Compare Source

pnpm/pnpm (pnpm)

v9.15.1

Compare Source

v9.15.0

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>;

unjs/unbuild (unbuild)

v3.0.1

Compare Source

compare changes

🩹 Fixes

• rollup: De-default default export from stub (#​455)

🏡 Chore

• Update changeloge.md (577b841)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Pooya Parsa (@​pi0)

v3.0.0

Compare Source

See github release notes.

unjs/undocs (undocs)

v0.2.30

Compare Source

compare changes

🩹 Fixes

• Update automd (7ee37d2)
• Fallback in case of any errors with automd transform (b36931c)

🏡 Chore

• Update deps (0191858)
• Update automd (9357a7b)
• Update @​nuxt/fonts (0403792)

❤️ Contributors

• Pooya Parsa (@​pi0)

v0.2.29

Compare Source

compare changes

🚀 Enhancements

• Add support for deno as package manager (#​147)

🏡 Chore

• release: V0.2.28 (0f6e735)
• Update jiti and c12 (0fcfb22)

❤️ Contributors

• Pooya Parsa (@​pi0)
• Bartek Iwańczuk biwanczuk@gmail.com

v0.2.28

Compare Source

compare changes

🩹 Fixes

• Update page title with spa navigation (2984c92)

💅 Refactors

• Make code blocks simpler (d8bf888)
• Use Inter as main font family (3e515f6)

❤️ Contributors

• Pooya Parsa (@​pi0)

v0.2.27

Compare Source

compare changes

🩹 Fixes

• Disable jsdoc transform due to issues (62ede86)

🏡 Chore

• release: V0.2.26 (2d80666)
• Update deps (d146591)

❤️ Contributors

• Pooya Parsa (@​pi0)

colinhacks/zod (zod)

v3.24.1

Compare Source

Commits:

• 0c6cbbd Undeprecate .nonempty()
• 4e219d6 Bump min TS version to 5.0
• 65adeea v3.24.1

v3.24.0

Compare Source

Implement @standard-schema/spec

This is the first version of Zod to implement the Standard Schema spec. This is a new community effort among several validation library authors to implement a common interface, with the goal of simplifying the process of integrating schema validators with the rest of the ecosystem. Read more about the project and goals here.

z.string().jwt()

Thanks to @​Mokshit06 and @​Cognition-Labs for this contribution!

To verify that a string is a valid 3-part JWT.

z.string().jwt();

⚠️ This does not verify your JWT cryptographically! It merely ensures its in the proper format. Use a library like jsonwebtoken to verify the JWT signature, parse the token, and read the claims.

To constrain the JWT to a specific algorithm:

z.string().jwt({ alg: "RS256" });

z.string().base64url()

Thank you to @​marvinruder!

To complement the JWT validation, Zod 3.24 implements a standalone .base64url() string validation API. (The three elements of JWTs are base64url-encoded JSON strings.)

z.string().base64url()

This functionality is available along the standard z.string().base64() validator added in Zod 3.23.

z.string().cidr()

Thanks to @​wataryooou for their work on this!

A validator for CIDR notation for specifying IP address ranges, e.g. 192.24.12.0/22.

z.string().cidr()

To specify an IP version:

z.string().cidr({ version: "v4" })
z.string().cidr({ version: "v6" })

---

View the full diff from 3.23.8: colinhacks/zod@v3.23.8...v3.24.0

• 294f54f Update README_ZH.md about Discriminated unions (#​3493)
• 1247caf Add Kubb as X-to-Zod community tool (#​3508)
• 62b7842 Update default branch
• c6bc80d Fix issue #​3582 : ULID should be case insensitive (#​3593)
• a5b9dc3 docs: add zod-schema-faker to ecosystem (#​3605)
• 9818d0e Add zod-sockets (#​3609)
• 7173d0b Add drizzle-zod library to X to Zod README.md section (#​3648)
• c5a4edc Add 'schemql' in Powered by Zod (#​3800)
• 85916b3 docs: add zod-form-renderer to form integration docs (#​3697)
• 51f1dc3 docs: add unplugin-environment in powered by zod (#​3778)
• 8e74db3 fix: ipv6 regex validation (#​3513)
• 1f4f0da refactor: rename ip version types (#​3755)
• f487d74 Remove faulty ip test case
• 48f1c47 docs: Remove invalid semicolon in ERROR_HANDLING.md (#​3857)
• 1d0a4b9 fix: bigint coerce crash (#​3822)
• 14dceaa Add API library (#​3814)
• f82f817 feat: z.string.cidr() - support CIDR notation (#​3820)
• 71a0c33 docs: add info on unqualified local datetime strings (#​3760)
• b85686a Add support for base64url strings (#​3712)
• 6407bed Allow creation of discriminated unions with a readonly array of options (#​3535)
• 3755146 Remove createParams cascade from .array() (#​3530)
• 963386d Fix lint
• 69a1798 Implement Standard Schema spec (#​3850)
• c1dd537 Adds frrm package to documentation (#​3818)
• b68c05f feat: Add JWT string validator (#​3893)

---

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.