fix(deps): update npm non-major dependencies #429

renovate · 2024-12-20T23:26:07Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@eslint/js (source)	`9.17.0` -> `9.20.0`
@mjackson/file-storage (source)	`^0.3.0` -> `^0.6.0`
@mjackson/form-data-parser (source)	`^0.5.0` -> `^0.7.0`
@mjackson/multipart-parser (source)	`^0.7.0` -> `^0.8.0`
@playwright/test (source)	`1.49.1` -> `1.50.1`
@radix-ui/react-avatar (source)	`1.1.2` -> `1.1.3`
@radix-ui/react-dropdown-menu (source)	`2.1.4` -> `2.1.6`
@radix-ui/react-slot (source)	`1.1.1` -> `1.1.2`
@radix-ui/react-switch (source)	`1.1.2` -> `1.1.3`
@radix-ui/react-toggle (source)	`1.1.1` -> `1.1.2`
@radix-ui/react-toggle-group (source)	`1.1.1` -> `1.1.2`
@radix-ui/react-tooltip (source)	`1.1.6` -> `1.1.8`
@react-router/dev (source)	`7.0.2` -> `7.1.5`
@react-router/express (source)	`7.0.2` -> `7.1.5`
@react-router/fs-routes (source)	`7.0.2` -> `7.1.5`
@react-router/node (source)	`7.0.2` -> `7.1.5`
better-sqlite3	`11.7.0` -> `11.8.1`
compression	`1.7.5` -> `1.8.0`
drizzle-kit (source)	`0.30.1` -> `0.30.4`
drizzle-orm (source)	`^0.38.0` -> `^0.39.0`
eslint (source)	`9.17.0` -> `9.20.1`
eslint-plugin-prettier	`5.2.1` -> `5.2.3`
eslint-plugin-react	`7.37.2` -> `7.37.4`
globals	`15.14.0` -> `15.15.0`
isbot (source)	`5.1.18` -> `5.1.22`
knip (source)	`5.41.1` -> `5.44.1`
lucide-react (source)	`^0.469.0` -> `^0.475.0`
postcss (source)	`8.4.49` -> `8.5.2`
prettier (source)	`3.4.2` -> `3.5.1`
react-day-picker (source)	`9.4.4` -> `9.5.1`
react-router (source)	`7.0.2` -> `7.1.5`
react-router-devtools (source)	`1.0.5` -> `1.1.4`
remix-auth-oauth2	`3.2.0` -> `3.2.2`
remix-utils	`8.0.0` -> `8.1.0`
slate-react	`0.112.0` -> `0.112.1`
tailwind-merge	`2.5.5` -> `2.6.0`
typescript (source)	`5.7.2` -> `5.7.3`
typescript-eslint (source)	`8.18.1` -> `8.24.0`
vite (source)	`5.4.11` -> `5.4.14`
vitest (source)	`2.1.8` -> `2.1.9`
zod (source)	`3.24.1` -> `3.24.2`
zod-form-data (source)	`2.0.4` -> `2.0.5`

Release Notes

eslint/eslint (@eslint/js)

mjackson/remix-the-web (@mjackson/file-storage)

`v0.6.1`

Fix regression when using LocalFileStorage together with form-data-parser (see #53)

`v0.6.0`

BREAKING CHANGE: LocalFileStorage now uses 2 characters for shard directory names instead of 8.
Buffer contents of files stored in MemoryFileStorage.
Add storage.list(options) for listing files in storage.

The following options are available:

cursor: An opaque string that allows you to paginate over the keys in storage
includeMetadata: If true, include file metadata in the result
limit: The maximum number of files to return
prefix: Only return keys that start with this string

For example, to list all files under keys that start with user123/:

let result = await storage.list({ prefix: 'user123/' });
console.log(result.files);
// [
//   { key: "user123/..." },
//   { key: "user123/..." },
//   ...
// ]

result.files will be an array of { key: string } objects. To include metadata about each file, use includeMetadata: true.

let result = await storage.list({ prefix: 'user123/', includeMetadata: true });
console.log(result.files);
// [
//   {
//     key: "user123/...",
//     lastModified: 1737955705270,
//     name: "hello.txt",
//     size: 16,
//     type: "text/plain"
//   },
//   ...
// ]

Pagination is done via an opaque cursor property in the list result object. If it is not undefined, there are more files to list. You can list them by passing the cursor back in the options object on the next call. For example, to list all items in storage, you could do something like this:

let result = await storage.list();
console.log(result.files);

while (result.cursor !== undefined) {
  result = await storage.list({ cursor: result.cursor });
  console.log(result.files);
}

Use the limit option to limit how many results you get back in the files array.

`v0.5.0`

Add storage.put(key, file) method as a convenience around storage.set(key, file) + storage.get(key), which is a very common pattern when you need immediate access to the file you just put in storage

// before
await storage.set(key, file);
let newFile = await storage.get(key)!;

// after
let newFile = await storage.put(key, file);

`v0.4.1`

Fix missing types for file-storage/local in npm package

`v0.4.0`

Fixes race conditions with concurrent calls to set
Shards storage directories for more scalable file systems

mjackson/remix-the-web (@mjackson/form-data-parser)

`v0.7.0`

BREAKING CHANGE: Override parseFormData signature so the upload handler is always last in the argument list. parserOptions are now an optional 2nd arg.

import { parseFormData } from '@&#8203;mjackson/form-data-parser';

// before
await parseFormData(
  request,
  (fileUpload) => {
    // ...
  },
  { maxFileSize },
);

// after
await parseFormData(request, { maxFileSize }, (fileUpload) => {
  // ...
});

Upgrade multipart-parser to v0.8 to fix an issue where errors would crash the process when maxFileSize was exceeded (see #28)
Add an example of how to use form-data-parser together with file-storage to handle multipart uploads on Node.js
Expand FileUploadHandler interface to support returning Blob from the upload handler, which is the superclass of File

`v0.6.0`

Allow upload handlers to run in parallel. Fixes #44

mjackson/remix-the-web (@mjackson/multipart-parser)

`v0.8.2`

Add Promise<void> to MultipartPartHandler return type

`v0.8.1`

Fix bad publish that left a workspace:^ version identifier in package.json

`v0.8.0`

This release improves error handling and simplifies some of the internals of the parser.

BREAKING CHANGE: Change parseMultipartRequest and parseMultipart interfaces from for await...of to await + callback API.

import { parseMultipartRequest } from '@&#8203;mjackson/multipart-parser';

// before
for await (let part of parseMultipartRequest(request)) {
  // ...
}

// after
await parseMultipartRequest(request, (part) => {
  // ...
});

This change greatly simplifies the implementation of parseMultipartRequest/parseMultipart and fixes a subtle bug that did not properly catch parse errors when maxFileSize was exceeded (see #28).

Add MaxHeaderSizeExceededError and MaxFileSizeExceededError to make it easier to have finer-grained error handling.

import * as http from 'node:http';
import {
  MultipartParseError,
  MaxFileSizeExceededError,
  parseMultipartRequest,
} from '@&#8203;mjackson/multipart-parser/node';

const tenMb = 10 * Math.pow(2, 20);

const server = http.createServer(async (req, res) => {
  try {
    await parseMultipartRequest(req, { maxFileSize: tenMb }, (part) => {
      // ...
    });
  } catch (error) {
    if (error instanceof MaxFileSizeExceededError) {
      res.writeHead(413);
      res.end(error.message);
    } else if (error instanceof MultipartParseError) {
      res.writeHead(400);
      res.end('Invalid multipart request');
    } else {
      console.error(error);
      res.writeHead(500);
      res.end('Internal Server Error');
    }
  }
});

`v0.7.3`

Add support for environments that do not support ReadableStream.prototype[Symbol.asyncIterator] (i.e. Safari), see #46

microsoft/playwright (@playwright/test)

`v1.50.1`

Compare Source

`v1.50.0`

Compare Source

Test runner

New option timeout allows specifying a maximum run time for an individual test step. A timed-out step will fail the execution of the test.

test('some test', async ({ page }) => {
  await test.step('a step', async () => {
    // This step can time out separately from the test
  }, { timeout: 1000 });
});

New method test.step.skip() to disable execution of a test step.

test('some test', async ({ page }) => {
  await test.step('before running step', async () => {
    // Normal step
  });

  await test.step.skip('not yet ready', async () => {
    // This step is skipped
  });

  await test.step('after running step', async () => {
    // This step still runs even though the previous one was skipped
  });
});

Expanded expect(locator).toMatchAriaSnapshot() to allow storing of aria snapshots in separate YAML files.
Added method expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.
Option testConfig.updateSnapshots added the configuration enum changed. changed updates only the snapshots that have changed, whereas all now updates all snapshots, regardless of whether there are any differences.
New option testConfig.updateSourceMethod defines the way source code is updated when testConfig.updateSnapshots is configured. Added overwrite and 3-way modes that write the changes into source code, on top of existing patch mode that creates a patch file.
```
npx playwright test --update-snapshots=changed --update-source-method=3way
```
Option testConfig.webServer added a gracefulShutdown field for specifying a process kill signal other than the default SIGKILL.
Exposed testStep.attachments from the reporter API to allow retrieval of all attachments created by that step.

UI updates

Updated default HTML reporter to improve display of attachments.
New button for picking elements to produce aria snapshots.
Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
Call and Network panels now display additional time information.

Breaking

expect(locator).toBeEditable() and locator.isEditable() now throw if the target element is not <input>, <select>, or a number of other editable elements.
Option testConfig.updateSnapshots now updates all snapshots when set to all, rather than only the failed/changed snapshots. Use the new enum changed to keep the old functionality of only updating the changed snapshots.

Browser Versions

Chromium 133.0.6943.16
Mozilla Firefox 134.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 132
Microsoft Edge 132

radix-ui/primitives (@radix-ui/react-avatar)

`v1.1.3`

Compare Source

remix-run/react-router (@react-router/dev)

`v7.1.5`

Compare Source

Patch Changes

Updated dependencies:
- [email protected]
- @react-router/[email protected]
- @react-router/[email protected]

`v7.1.4`

Compare Source

Patch Changes

Properly resolve Windows file paths to scan for Vite's dependency optimization when using the unstable_optimizeDeps future flag. (#12637)
Fix prerendering when using a custom server - previously we ended up trying to import the users custom server when we actually want to import the virtual server build module (#12759)
Updated dependencies:
- [email protected]
- @react-router/[email protected]
- @react-router/[email protected]

`v7.1.3`

Compare Source

Patch Changes

Fix reveal and routes CLI commands (#12745)
Updated dependencies:
- [email protected]
- @react-router/[email protected]
- @react-router/[email protected]

`v7.1.2`

Compare Source

Patch Changes

Fix default external conditions in Vite v6. This fixes resolution issues with certain npm packages. (#12644)
Fix mismatch in prerendering html/data files when path is missing a leading slash (#12684)
Use module-sync server condition when enabled in the runtime. This fixes React context mismatches (e.g. useHref() may be used only in the context of a <Router> component.) during development on Node 22.10.0+ when using libraries that have a peer dependency on React Router. (#12729)
Fix react-refresh source maps (#12686)
Updated dependencies:
- [email protected]
- @react-router/[email protected]
- @react-router/[email protected]

`v7.1.1`

Compare Source

Patch Changes

Fix for a crash when optional args are passed to the CLI (5b1ca202f)
Updated dependencies:
- [email protected]
- @react-router/[email protected]
- @react-router/[email protected]

`v7.1.0`

Compare Source

Minor Changes

Add support for Vite v6 (#12469)

Patch Changes

Properly initialize NODE_ENV if not already set for compatibility with React 19 (#12578)
Remove the leftover/unused abortDelay prop from ServerRouter and update the default entry.server.tsx to use the new streamTimeout value for Single Fetch (#12478)
- The abortDelay functionality was removed in v7 as it was coupled to the defer implementation from Remix v2, but this removal of this prop was missed
- If you were still using this prop in your entry.server file, it's likely your app is not aborting streams as you would expect and you will need to adopt the new streamTimeout value introduced with Single Fetch
Updated dependencies:
- [email protected]
- @react-router/[email protected]
- @react-router/[email protected]