Bump the minor group across 1 directory with 20 updates

[dependabot]

Bumps the minor group with 20 updates in the / directory:

Package	From	To
@zip.js/zip.js	2.7.54	2.8.34
dexie	4.0.11	4.4.4
dexie-export-import	4.1.4	4.4.0
linkedom	0.18.10	0.18.13
@eslint/eslintrc	3.2.0	3.3.6
@playwright/test	1.49.1	1.62.0
@types/dom-webcodecs	0.1.13	0.1.18
@types/zip.js	2.0.33	2.6.81
@vitest/eslint-plugin	1.1.21	1.6.24
ajv	8.17.1	8.20.0
esbuild	0.25.1	0.28.1
eslint-plugin-import	2.31.0	2.32.0
eslint-plugin-no-unsanitized	4.1.2	4.1.5
eslint-plugin-unused-imports	4.1.4	4.4.1
fake-indexeddb	6.0.0	6.2.5
handlebars	4.7.8	4.7.9
license-report	6.7.1	6.8.5
prettier	3.4.2	3.9.6
ts-json-schema-generator	2.3.0	2.9.0
typescript-eslint	8.18.2	8.65.0

Updates @zip.js/zip.js from 2.7.54 to 2.8.34

Release notes

Sourced from @​zip.js/zip.js's releases.

v2.8.34

Bug fixes

• Fixed zip global export name mangled away in minified UMD builds (e.g. dist/zip.min.js)

v2.8.33

Performance

• Updated the JavaScript zlib streams module.

v2.8.32

New Features

• Added createBlobTempStream, a ready-made createTempStream factory that spills the data of buffered entries into a Blob instead of keeping it in memory. Memory is bounded in Chromium browsers; in other engines and non-browser runtimes the Blob is held in memory, so createOPFSTempStream or a file-backed implementation is preferable there.
• Added createSyncAccessHandleTempStream, an OPFS-backed createTempStream factory built on FileSystemSyncAccessHandle. It offers the same options and bounded-memory profile as createOPFSTempStream but writes roughly 2.5× faster in Chromium and Firefox and reads back several times faster in Firefox and Safari, making disk-backed staging nearly as fast as the in-memory default (worker-only variant).

Bug Fixes

• Codec worker now copies chunks that do not own their underlying buffer before transferring them, preventing data corruption when a chunk's ArrayBuffer is shared or externally owned.

v2.8.31

New features

• Accept a non-constructable reader (a factory function, not only a Reader class) as the Reader of a ZipFileEntry/ZipDirectoryEntry; the reader is now invoked with or without new depending on whether it exposes a prototype.
• Export the ERR_ITERATOR_COMPLETED_TOO_SOON and ERR_WRITER_NOT_INITIALIZED error constants.

Bug fixes

• Add a dedicated index.d.cts so TypeScript resolves the correct types for the CommonJS entry point instead of falling back to the ESM declarations.
• Fix invalid entries in the MIME type table: drop the bogus x-font/pcf.Z and duplicate video/avif entries, correct the mis-keyed application/x-ms-installer (msi), and map image/avif to both avif and avifs.
• Align the JavaScript zlib module with the windowBits: -16 raw-stream convention.

Performance

• Build the MIME type map lazily from a compact JSON payload, so the table is only parsed when a MIME type is actually requested.
• Shrink the WebAssembly zlib module by ~8 KB (~16%) by merging the deflate64 path into the inflate code and generating the deflate trees at runtime.
• Reduce bundle size by mangling internal property names and shipping inline worker payloads deflate-compressed.

v2.8.30

New features

• Add the strictness option ("strict" | "balanced" | "tolerant", default "balanced") and maxAppendedDataSize option to ZipReader, controlling how appended data, prepended stubs, and ambiguous end-of-central-directory records are handled. checkAmbiguity: true is now an alias for "strict".
• Add createOPFSTempStream() and the createTempStream writer option to spill large buffered entries to the OPFS instead of memory, with an optional dispose() hook released on every exit path.
• Add FS#exportFileSystemHandle() and ZipDirectoryEntry#exportFileSystemHandle() to write an entry tree out to a FileSystemDirectoryHandle.

Security: End-of-central-directory selection

• Select the last end-anchored record that points to a central directory instead of the first signature scanned from the end; refuse genuine comment-cloak polyglots with ERR_AMBIGUOUS_ARCHIVE.
• Rank record reachability so empty or saturated bytes at the end of a comment can no longer forge a second record; genuine empty and zip64 archives still open.
• Prefer the reconciled central-directory offset over a stale one, so an identical-layout append remnant exposes the appended directory rather than the previous one.
• Apply the reachability check to the fallback scan, so a stray signature in appended data no longer hijacks recovery under tolerant. Security
• Bound the reachability probes to prevent a comment stuffed with unreachable records from amplifying into thousands of (potentially remote) reads on random-access readers such as HttpRangeReader.

... (truncated)

Commits

• 438e241 bump up version
• 089677f update doc
• ae37f1a exclude benchmarks folder
• 54704af fix zip global export name mangled away in minified UMD builds
• e8555ae add web worker test
• 9d3e16b bump up version
• eb0a28f bump up version
• be47350 update doc
• 430b26a update built files
• 6746a0e update zlib js module
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​zip.js/zip.js since your current version.

Updates dexie from 4.0.11 to 4.4.4

Release notes

Sourced from dexie's releases.

Dexie v4.4.4

This is a maintenance release that resolves a bug in useLiveQuery caching and includes a TypeScript typing enhancement.

Related Package Releases

Package	Version
dexie	4.4.4
dexie-cloud-addon	4.4.13 (no change)
dexie-react-hooks	4.4.0 (no change)
y-dexie	4.4.0 (no change)

Bug Fixes

dexie@4.4.4

• fix: useLiveQuery fails to detect updates when mutating queried objects in-place and calling put() — In default/cloned cache mode (cache: 'cloned'), mutating queried objects in-place and subsequently calling put() on them would pollute the cache directly, preventing subsequent live-queries from detecting the change because the "before" and "after" states in the cache became identical. Live-queries now deeply clone results on read to completely isolate query results from in-place consumer mutations. (#2310). Reported in #2309 by @​laukaichung. Fixed by @​liz709 and @​dfahlander .

Other Changes

dexie@4.4.4

• fix: typescript typings - add missing table4 parameter to transaction method — Added the missing table4 parameter to the typescript type definition of Dexie.transaction(), aligning it with other table parameters. Contributed by @​renbaoshuo (#2311)

Dexie v4.4.3

This is a maintenance release with bug fixes and a configuration API improvement.

Related Package Releases

Package	Version
dexie	4.4.3
dexie-cloud-addon	4.4.13

Bug Fixes

dexie@4.4.3

• fix: delByKeyPath() creates empty intermediate objects on missing path — Dexie.delByKeyPath(obj, "foo.bar") on an object without foo would create {foo: {}} as a side effect instead of doing nothing. This caused a real-world bug in dexie-cloud-addon where clearing a dotted key from a changeSpec (e.g. claims.sub) would leave {claims: {}} in the spec, which then overwrote the inline primary key with undefined, resulting in: DataError: Evaluating the object store's key path did not yield a value. Fixed in setByKeyPath to bail out early when value is undefined and the intermediate path doesn't exist. (#2303)

• fix: Collection.sortBy() mutates frozen array in immutable cache mode — calling .sortBy() on a table when using immutable cache mode could throw TypeError: Cannot assign to read only property because Array.sort() was called on a frozen array. Fixed by sorting on a copy instead. (#2294)

dexie-cloud-addon@4.4.12

• rename: maxStringLength → largeStringThreshold — the string offloading option is renamed for clarity. The old name is kept as a backward-compatible alias. (#2290)

• fix: blob writebacks routed through BlobSavingQueue to avoid PSD context loss — after an async native fetch (blob download), Dexie's PSD zone is no longer active, causing table.mutate() to crash with Cannot read properties of undefined (reading 'table'). This surfaced as [dexie-cloud:blobResolve] Failed to resolve BlobRefs. Fixed by always routing blob writebacks through BlobSavingQueue.saveBlobs(), which opens a proper Dexie rw-transaction in a fresh JS task. Fixes lazy blob mode crash when using Dexie hooks with dexie-cloud-addon. (#2302)

• fix: eager blob downloader could starve RAM — the eager downloader triggered blobResolveMiddleware which resolved all pending blobs into memory at once. Fixed by downloading blobs in chunks with a query limit, so memory usage stays bounded regardless of how many blobs are pending. (#2302)

... (truncated)

Commits

• f151e96 chore: bump version to 4.4.4
• 0cc46ac perf(live-query): avoid redundant double deepClone on initial query cache pop...
• fb5d3b7 test(live-query): revert prettier formatting and keep only targeted test fixes
• 8c8c24d test(live-query): parameterize issue 2309 test and fix pre-existing syntax/pr...
• bb4c265 test(live-query): change actualResults to let to avoid TypeError in tests
• a6edadb fix(live-query): clone results on cache read when cache: 'cloned' is used (is...
• 9485361 Add missing table4 parameter typing to transaction method
• 30134f6 Trigger new dev build
• 9dd614d DataError after updating a user in dexie cloud when that user got an update f...
• 0919742 Trigger dev build
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for dexie since your current version.

Updates dexie-export-import from 4.1.4 to 4.4.0

Release notes

Sourced from dexie-export-import's releases.

Dexie v4.3.0

This release introduces Social Authentication for Dexie Cloud, allowing users to sign in with Google, GitHub, Microsoft, Apple, or custom OAuth2 providers as an alternative to email OTP authentication.

Related Package Releases

Package	Version
dexie	4.3.0
dexie-cloud-addon	4.3.9
dexie-react-hooks	4.2.2-beta.2

New Features

🔐 Social Authentication for Dexie Cloud

Dexie Cloud now supports OAuth 2.0 social login providers as an alternative to the existing OTP (One-Time Password) email authentication.

Supported Providers:

• Google
• GitHub
• Microsoft
• Apple
• Custom OAuth2 providers

The Dexie Cloud server acts as an OAuth broker, handling all provider interactions. The client library never receives provider tokens—only Dexie Cloud authorization codes which are exchanged for Dexie Cloud tokens.

Usage:

Social auth is enabled by default on the client but need to be configured in manager first. When db.cloud.login() is called, users will see a provider selection dialog if OAuth providers are configured on the server.

// Initiate login - shows provider selection if available
await db.cloud.login();
// Or specify a provider directly
await db.cloud.login({ provider: 'google' });

Configuration Options:

db.cloud.configure({
  databaseUrl: 'https://mydb.dexie.cloud',
// Enable/disable social auth (default: true)
socialAuth: true, // also configure in https://manager.dexie.cloud
});

⚡ Suspense Support in dexie-react-hooks (Experimental)

... (truncated)

Commits

• See full diff in compare view

Updates linkedom from 0.18.10 to 0.18.13

Commits

• fcd88e0 0.18.13
• 195f7aa brought in better spec-compliant style and getComputed
• b9ee7fd fix: reading an unset style property returns "" per CSSOM, not undefined (#328)
• 2450493 Fix #320 - Updated build status
• d001308 removed unnecessary .npmrc line + updated dev/dependencies - not htmlparser2
• dfc2fa8 0.18.12
• c78f6eb Add peerDependencies and peerDependenciesMeta for canvas (#309)
• f193f8f fix: close WebReflection/linkedom#249...
• fafb337 Fix typo in README.md (#294)
• 5174edb 0.18.11
• Additional commits viewable in compare view

Updates @eslint/eslintrc from 3.2.0 to 3.3.6

Release notes

Sourced from @​eslint/eslintrc's releases.

eslintrc: v3.3.6

3.3.6 (2026-07-10)

Bug Fixes

• update js-yaml to 4.3.0 to address security vulnerability (#235) (0c5de74)

eslintrc: v3.3.5

3.3.5 (2026-03-04)

Bug Fixes

• update dependency minimatch to ^3.1.5 (#227) (3dc2381)

eslintrc: v3.3.4

3.3.4 (2026-02-22)

Bug Fixes

• update ajv to 6.14.0 to address security vulnerabilities (#221) (9139140)
• update minimatch to 3.1.3 to address security vulnerabilities (#224) (30339d0)

eslintrc: v3.3.3

3.3.3 (2025-11-28)

Bug Fixes

• release v3.3.3 because publishing v3.3.2 failed (#211) (8aa555a)

eslintrc: v3.3.2

3.3.2 (2025-11-25)

Bug Fixes

• Remove name property from all and recommended configs (#200) (344da49)

v3.3.1

3.3.1 (2025-03-11)

Bug Fixes

• correct types field in package.json (#184) (2f4cf3f)

v3.3.0

... (truncated)

Changelog

Sourced from @​eslint/eslintrc's changelog.

3.3.6 (2026-07-10)

Bug Fixes

• update js-yaml to 4.3.0 to address security vulnerability (#235) (0c5de74)

3.3.5 (2026-03-04)

Bug Fixes

• update dependency minimatch to ^3.1.5 (#227) (3dc2381)

3.3.4 (2026-02-22)

Bug Fixes

• update ajv to 6.14.0 to address security vulnerabilities (#221) (9139140)
• update minimatch to 3.1.3 to address security vulnerabilities (#224) (30339d0)

3.3.3 (2025-11-28)

Bug Fixes

• release v3.3.3 because publishing v3.3.2 failed (#211) (8aa555a)

3.3.2 (2025-11-25)

Bug Fixes

• Remove name property from all and recommended configs (#200) (344da49)

3.3.1 (2025-03-11)

Bug Fixes

• correct types field in package.json (#184) (2f4cf3f)

3.3.0 (2025-02-21)

Features

• Add types to package (#179) (cb546be)

Commits

• b433a22 chore: release 3.3.6 🚀 (#236)
• 0c5de74 fix: update js-yaml to 4.3.0 to address security vulnerability (#235)
• 94837a4 docs: Update README sponsors
• dbae1a1 docs: Update README sponsors
• 19fe72a docs: Update README sponsors
• 92ebd17 docs: Update README sponsors
• 3ba4c8c ci: add Node.js 26 to CI (#231)
• f8d268a docs: Update README sponsors
• 6e20867 docs: Update README sponsors
• 6d722b6 docs: Update README sponsors
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​eslint/eslintrc since your current version.

Updates @playwright/test from 1.49.1 to 1.62.0

Release notes

Sourced from @​playwright/test's releases.

v1.62.0

🧱 New component testing model

Component testing moves to a stories and galleries model. A story wraps your component in one specific scenario — hard-coded props, mock data, providers — and a gallery page that you serve renders stories on demand. The new fixtures.mount() fixture navigates to the gallery, mounts a story by id, and returns a Locator scoped to the story's root element:

test('click should expand', async ({ mount }) => {
  const component = await mount('components/Expandable/Stateful');
  await component.getByRole('button').click();
  await expect(component.getByTestId('expanded')).toHaveValue('true');
});

Pass a story type as a template argument to type-check its props, and use update(props) / unmount() on the returned locator to re-render or tear down within a test.

🛑 Cancel operations with AbortSignal

Most operations and web-first assertions now accept a signal option that takes an AbortSignal, letting you cancel long-running actions, navigations, waits, and assertions:

const controller = new AbortController();
setTimeout(() => controller.abort(), 1000);
await page.getByRole('button', { name: 'Submit' }).click({ signal: controller.signal });
await expect(page.getByText('Done')).toBeVisible({ signal: controller.signal });

Providing a signal does not disable the default timeout; pass timeout: 0 to disable it.

🖼️ WebP screenshots

expect(page).toHaveScreenshot() and expect(locator).toHaveScreenshot() can now store snapshots in the WebP format — just give the snapshot a .webp name:

// Visual comparisons store the golden snapshot as lossless WebP.
await expect(page).toHaveScreenshot('homepage.webp');
// Standalone screenshots can trade quality for size with lossy WebP.
await page.screenshot({ path: 'homepage.webp', quality: 50 });

page.screenshot() and [locator.screenshot() (https://playwright.dev/docs/api/class-locator#locator-screenshot) also accept webp as a type, where quality 100 (the default) is lossless and lower values use lossy compression.

🧩 Custom test filtering with Reporter.preprocess()

New reporter.preprocess() hook runs after the configuration is resolved and before reporter.onBegin(), letting a reporter mark individual tests as skipped, excluded, fixed, or failing through a TestRun object:

</tr></table> 

... (truncated)

Commits

• e3950d9 chore: mark v1.62.0 (#41981)
• f07e0f7 cherry-pick(#41940): docs: release notes for v1.62 (#41967)
• 05a306c cherry-pick(#41964): Revert "feat(routeFromHar): add interceptAPIRequests opt...
• 2934858 fix: correct pending navigation log spacing (#41949)
• 4b0cc99 fix(test): unflake screencast backpressure test on slow macOS runner (#41951)
• bbbae6d test: fixme WebSocket locale test in Chromium 150 (#41944)
• 15c4f55 fix(mcp): identify downloads explicitly (#41933)
• f5fa967 fix(network): request.postData() returns null for empty string body override ...
• 0edafe4 fix(mcp): launch the Chrome profile that has the extension installed (#41939)
• 244a1ff feat(firefox): roll to r1538 (#41938)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​playwright/test since your current version.

Updates @types/dom-webcodecs from 0.1.13 to 0.1.18

Commits

• See full diff in compare view

Updates @types/zip.js from 2.0.33 to 2.6.81

Commits

• See full diff in compare view

Updates @vitest/eslint-plugin from 1.1.21 to 1.6.24

Release notes

Sourced from @​vitest/eslint-plugin's releases.

v1.6.24

   🐞 Bug Fixes

• valid-expect: Fix poll and element taking 1 or 2 arguments  -  by @​julienw in vitest-dev/eslint-plugin-vitest#931 (57e53)

    View changes on GitHub

v1.6.23

   🚀 Features

• prefer-expect-assertions: Add disallowHasAssertions option  -  by @​ssssota in vitest-dev/eslint-plugin-vitest#929 (5e1e1)

   🐞 Bug Fixes

• 8 warnings for unexpected node version input  -  by @​hirehamir in vitest-dev/eslint-plugin-vitest#928 (394dd)
• valid-expect: Handle static expect APIs  -  by @​w3lld1 in vitest-dev/eslint-plugin-vitest#930 (79232)

    View changes on GitHub

v1.6.22

   🐞 Bug Fixes

• Handle expect.any separately from Chai any flag  -  by @​nami8824 in vitest-dev/eslint-plugin-vitest#925 (34157)

    View changes on GitHub

v1.6.21

   🐞 Bug Fixes

• Support Chai-style expect chains  -  by @​nami8824 in vitest-dev/eslint-plugin-vitest#920 (52692)
• prefer-called-with: Map calledOnce matcher to exact once with  -  by @​nami8824 in vitest-dev/eslint-plugin-vitest#918 (8f671)

    View changes on GitHub

v1.6.20

   🐞 Bug Fixes

• hoisted-apis-on-top: Detect vitest.mock and aliased vi/vitest mock calls  -  by @​spokodev in vitest-dev/eslint-plugin-vitest#909 (8fff9)
• require-test-timeout: Treat imported bindings as explicit timeouts  -  by @​spokodev in vitest-dev/eslint-plugin-vitest#906 (bd82c)
• valid-expect: Treat .finally() as part of async assertion promise chains  -  by @​spokodev in vitest-dev/eslint-plugin-vitest#908 (7c697)

    View changes on GitHub

v1.6.19

No significant changes

    View changes on GitHub

v1.6.18

   🐞 Bug Fixes

... (truncated)

Commits

• 1a0fdaf chore: release v1.6.24
• 57e5389 fix(valid-expect): fix poll and element taking 1 or 2 arguments (#931)
• 8ce9857 chore: release v1.6.23
• 5e1e140 feat(prefer-expect-assertions): add disallowHasAssertions option (#929)
• 792320a fix(valid-expect): handle static expect APIs (#930)
• 394ddb6 fix: 8 warnings for unexpected node version input (#928)
• 61bc715 chore: release v1.6.22
• 3415709 fix: handle expect.any separately from Chai any flag (#925)
• ffe3299 chore: release v1.6.21
• af7ac0c Initial support for aroundEach and aroundAll hooks (#923)
• Additional commits viewable in compare view

Updates ajv from 8.17.1 to 8.20.0

Release notes

Sourced from ajv's releases.

v8.20.0

What's Changed

• fix: add support for node 22/24, drop node 16/21 by @​jasoniangreen in ajv-validator/ajv#2580
• fix: add ES2022.RegExp for RegExpIndicesArray by @​SignpostMarv in ajv-validator/ajv#2604

Full Changelog: ajv-validator/ajv@v8.19.0...v8.20.0

v8.19.0

What's Changed

• fix prototype pollution via format keyword using $data ref by @​epoberezkin in ajv-validator/ajv#2607

Full Changelog: ajv-validator/ajv@v8.18.0...v8.19.0

v8.18.0

What's Changed

• feat: allow tree-shaking by adding "sideEffects": false to package.json by @​josdejong in ajv-validator/ajv#2480
• fix: #2482 Infinity and NaN serialise to null by @​jasoniangreen in ajv-validator/ajv#2487
• fix: small grammatical error in managing-schemas.md by @​monteiro-renato in ajv-validator/ajv#2508
• fix: typos in schema-language.md by @​monteiro-renato in ajv-validator/ajv#2507
• fix(pattern): use configured RegExp engine with $data keyword to mitigate ReDoS attacks (CVE-2025-69873) by @​epoberezkin in ajv-validator/ajv#2586

New Contributors

• @​josdejong made their first contribution in ajv-validator/ajv#2480
• @​monteiro-renato made their first contribution in ajv-validator/ajv#2508

Full Changelog: ajv-validator/ajv@v8.17.1...v8.18.0

Commits

• 0fba0b8 8.20.0
• 9caf8d6 fix: add ES2022.RegExp for RegExpIndicesArray; fixes ajv-validator/ajv#2603 (...
• 2065350 fix: add support for node 22/24, drop node 16/21 (#2580)
• 154b58d 8.19.0
• e8d2bdc test/fix prototype pollution via $data ref with format keyword (#2607)
• 142ce84 8.18.0
• 720a23f fix(pattern): use configured RegExp engine with $data keyword to mitigate ReD...
• 82735a1 fix: typos in schema-language.md (#2507)
• b17ec32 fix: small grammatical error in managing-schemas.md (#2508)
• 69568d0 fix: #2482 Infinity and NaN serialise to null (#2487)
• Additional commits viewable in compare view

Updates esbuild from 0.25.1 to 0.28.1

Release notes

Sourced from esbuild's releases.

v0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2025

This changelog documents all esbuild versions published in the year 2025 (versions 0.25.0 through 0.27.2).

0.27.2

• Allow import path specifiers starting with #/ (#4361)

  Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

  This change was contributed by @​hybrist.

• Automatically add the -webkit-mask prefix (#4357, #4358)

  This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

  /* Original code */
  main {
    mask: url(x.png) center/5rem no-repeat
  }
  /* Old output (with --target=chrome110) */
  main {
  mask: url(x.png) center/5rem no-repeat;
  }
  /* New output (with --target=chrome110) */
  main {
  -webkit-mask: url(x.png) center/5rem no-repeat;
  mask: url(x.png) center/5rem no-repeat;
  }

  This change was contributed by @​BPJEnnova.

• Additional minification of switch statements (#4176, #4359)

  This release contains additional minification patterns for reducing switch statements. Here is an example:

  // Original code
  switch (x) {
    case 0:
      foo()
      break
    case 1:
    default:
      bar()
  }

... (truncated)

Commits

• bb9db84 publish 0.28.1 to npm
• 9ff053e security: add integrity checks to the Deno API
• 0a9bf21 enforce non-negative size in gzip parser
• e2a1a71 security: forbid \\ in local dev server requests
• 83a2cbf fix #4482: don't inline using declarations
• 308ad74 fix #4471: renaming of nested var declarations
• f013f5f fix some typos
• aafd6e4 chore: fix some minor issues in comments (#4462)
• 15300c3 follow up: cjs evaluation fixes
• 1bda0c3 fix #4461, fix #4467: esm evaluation fixes
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for esbuild since your current version.

Updates eslint-plugin-import from 2.31.0 to 2.32.0

Release notes

Sourced from eslint-plugin-import's releases.

v2.32.0

Added

• add enforce-node-protocol-usage rule and import/node-version setting (#3024, thanks [@​GoldStrikeArch] and [@​sevenc-nanashi])
• add TypeScript types (#3097, thanks [@​G-Rath])
• extensions: add `pathGroupOverrides to allow enforcement decision overrides based on specifier (#3105, thanks [@​Xunnamius])
• [order]: add sortTypesGroup option to allow intragroup sorting of type-only imports (#3104, thanks [@​Xunnamius])
• [order]: add newlines-between-types option to control intragroup sorting of type-only imports (#3127, thanks [@​Xunnamius])
• [order]: add consolidateIslands option to collapse excess spacing for aesthetically pleasing imports (#3129, thanks [@​Xunnamius])

Fixed

• [no-unused-modules]: provide more meaningful error message when no .eslintrc is present (#3116, thanks [@​michaelfaith])
• configs: added missing name attribute for eslint config inspector (#3151, thanks [@​NishargShah])
• [order]: ensure arcane imports do not cause undefined behavior (#3128, thanks [@​Xunnamius])
• [order]: resolve undefined property access issue when using named ordering (#3166, thanks [@​Xunnamius])
• enforce-node-protocol-usage: avoid a crash with some TS code (#3173, thanks [@​ljharb])
• [order]: codify invariants from docs into config schema (#3152, thanks [@​Xunnamius])

Changed

• [Docs] extensions, [order]: improve documentation (

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 976a7078e4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Raise the Node floor for license-report 6.8.5

When contributors or CI images use a Node version that package.json still allows (for example 22.0.0 through 22.22.1, or 23.x) with engine enforcement enabled, this bump produces an unsupported install tree: package-lock.json now pulls license-report/node_modules/ini@7.0.0, whose engine is ^22.22.2 || ^24.15.0 || >=26.0.0. Either raise the project engine to match that transitive dependency or pin license-report/ini to a version compatible with the advertised Node range.

Useful? React with 👍 / 👎.