chore(deps): update all dev dependencies (major) #1142

renovate · 2024-05-29T11:54:35Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update
@types/jest (source)	`^29.2.3` → `^30.0.0`	devDependencies	major
@types/node (source)	`^18.11.9` → `^24.0.0`	devDependencies	major
cross-env	`^7.0.3` → `^10.0.0`	devDependencies	major
duct	`0.13.7` → `1.0.0`	dev-dependencies	major
execa	`7.2.0` → `9.6.1`	devDependencies	major
jest (source)	`^29.3.1` → `^30.0.0`	devDependencies	major
p-retry	`^6.2.0` → `^7.0.0`	devDependencies	major
which	`^3.0.1` → `^6.0.0`	devDependencies	major
zod (source)	`^3.19.1` → `^4.0.0`	devDependencies	major

Release Notes

kentcdodds/cross-env (cross-env)

`v10.1.0`

Compare Source

Features

add support for default value syntax (152ae6a)

For example:

"dev:server": "cross-env wrangler dev --port ${PORT:-8787}",

If PORT is already set, use that value, otherwise fallback to 8787.

Learn more about Shell Parameter Expansion

`v10.0.0`

Compare Source

TL;DR: You should probably not have to change anything if:

You're using a modern maintained version of Node.js (v20+ is tested)
You're only using the CLI (most of you are as that's the intended purpose)

In this release (which should have been v8 except I had some issues with automated releases 🙈), I've updated all the things and modernized the package. This happened in #261

Was this needed? Not really, but I just thought it'd be fun to modernize this package.

Here's the highlights of what was done.

Replace Jest with Vitest for testing
Convert all source files from .js to .ts with proper TypeScript types
Use zshy for ESM-only builds (removes CJS support)
Adopt @epic-web/config for TypeScript, ESLint, and Prettier
Update to Node.js >=20 requirement
Remove kcd-scripts dependency
Add comprehensive e2e tests with GitHub Actions matrix testing
Update GitHub workflow with caching and cross-platform testing
Modernize documentation and remove outdated sections
Update all dependencies to latest versions
Add proper TypeScript declarations and exports

The tool maintains its original functionality while being completely modernized with the latest tooling and best practices

BREAKING CHANGES

This is a major rewrite that changes the module format from CommonJS to ESM-only. The package now requires Node.js >=20 and only exports ESM modules (not relevant in most cases).

oconnor663/duct.rs (duct)

sindresorhus/execa (execa)

`v9.6.1`

Compare Source

Fix VerboseOption type not being properly exported (#1215) 7891c39

`v9.6.0`

Compare Source

Update dependencies d49104a

`v9.5.3`

Compare Source

Fix Node 24-specific deprecation warning (#1199) 1ac5b91

`v9.5.2`

Compare Source

Bug fixes

Fix escaping newlines inside template strings. Thanks @aarondandy! (#1176)

`v9.5.1`

Compare Source

Bug fixes

Fix odd characters being printed in verbose mode on Windows (thanks @IIIMADDINIII). (#1167)

`v9.5.0`

Compare Source

Features

When redirecting stdout or stderr to a file, allow appending instead of overwriting. (#1166)

await execa({stdout: {file: 'output.txt', append: true}})`npm run build`;

`v9.4.1`

Compare Source

Bug fixes

Fix using process.execPath with Deno. Thanks @w3cj! (#1160)

`v9.4.0`

Compare Source

Features

We've created a separate package called nano-spawn. It is similar to Execa but with fewer features, for a much smaller package size. More info.

Bug fixes

Both execaNode() and the preferLocal option modify the PATH environment variable. This release includes some minor improvements to ensure that environment variable remains small (sindresorhus/npm-run-path#20). It also handles a few related edge cases better (sindresorhus/npm-run-path#21).

Documentation

Small documentation typo fix, thanks @rrthomas! (#1153)

`v9.3.1`

Compare Source

Thanks @holic and @jimhigson for your contributions!

Bugs

Do not crash when using a custom Node.js binary without ICU support. (#1144)

Bugs (types)

Fix type of the env option. It was currently failing for Remix or Next.js users. (by @holic) (#1141)

Documentation

Fix typo in "Inputs" documentation. (by @jimhigson) (#1145)
Document how to terminate hanging subprocesses. (#1140)
Document how to add custom logging. (#1131)

`v9.3.0`

Compare Source

Features

The verbose option can now be a function to customize logging. (#1130)

`v9.2.0`

Compare Source

This release includes a new set of methods to exchange messages between the current process and a Node.js subprocess, also known as "IPC". This allows passing and returning almost any message type to/from a Node.js subprocess. Also, debugging IPC is now much easier.

Moreover, a new gracefulCancel option has also been added to terminate a subprocess gracefully.

For a deeper dive-in, please check and share the release post!

Thanks @iiroj for your contribution, @SimonSiefke and @adymorz for reporting the bugs fixed in this release, and @karlhorky for improving the documentation!

Deprecations

Passing 'ipc' to the stdio option has been deprecated. It will be removed in the next major release. Instead, the ipc: true option should be used. (#1056)

- await execa('npm', ['run', 'build'], {stdio: ['pipe', 'pipe', 'pipe', 'ipc']});
+ await execa('npm', ['run', 'build'], {ipc: true});

The execaCommand() method has been deprecated. It will be removed in the next major release. If most cases, the template string syntax should be used instead.

- import {execaCommand} from 'execa';
+ import {execa} from 'execa';

- await execaCommand('npm run build');
+ await execa`npm run build`;

const taskName = 'build';
- await execaCommand(`npm run ${taskName}`);
+ await execa`npm run ${taskName}`;

const commandArguments = ['run', 'task with space'];
await execa`npm ${commandArguments}`;

If the file and/or multiple arguments are supplied as a single string, parseCommandString(command) can split that string into an array. More info. (#1054)

- import {execaCommand} from 'execa';
+ import {execa, parseCommandString} from 'execa';

const commandString = 'npm run task';
- await execaCommand(commandString);
+ const commandArray = parseCommandString(commandString); // ['npm', 'run', 'task']
+ await execa`${commandArray}`;

// Or alternatively:
const [file, ...commandArguments] = commandArray;
await execa(file, commandArguments);

Features

Add gracefulCancel option and getCancelSignal() method to terminate a subprocess gracefully. error.isGracefullyCanceled was also added. (#1109)
Add error.isForcefullyTerminated. It is true when the subprocess was terminated by the forceKillAfterDelay option. (#1111)
New methods to simplify exchanging messages between the current process and the subprocess. More info. (#1059, #1061, #1076, #1077, #1079, #1082, #1083, #1086, #1087, #1088, #1089, #1090, #1091, #1092, #1094, #1095, #1098, #1104, #1107)
- The current process sends messages with subprocess.sendMessage(message) and receives them with subprocess.getOneMessage(). subprocess.getEachMessage() listens to multiple messages.
- The subprocess uses sendMessage(message), getOneMessage() and getEachMessage() instead. Those are the same methods, but imported directly from the 'execa' module.
The ipcInput option sends an IPC message from the current process to the subprocess as it starts. This enables passing almost any input type to a Node.js subprocess. (#1068)
The result.ipcOutput array contains all the IPC messages sent by the subprocess to the current process. This enables returning almost any output type from a Node.js subprocess. (#1067, #1071, #1075)
The error message now contains every IPC message sent by the subprocess. (#1067)
The verbose: 'full' option now logs every IPC message sent by the subprocess, for debugging. More info here and there. (#1063)

Types

Add ExecaMethod, ExecaNodeMethod and ExecaScriptMethod, ExecaSyncMethod and ExecaScriptSyncMethod types. (#1066)
Export the Message type, for IPC. (#1059)
Fix type of forceKillAfterDelay: true option. (#1116)

Bug fixes

Fix passing a {file} to both the stdin and the stdout or stderr options. (#1058)
Fix multiple minor problems with the cancelSignal option. (#1108)
Fix accidental publishing of Vim backup files. (#1074)
Fix engines.node field in package.json. Supported Node.js version is ^18.19.0 or >=20.5.0. (by @iiroj) (#1101)

`v9.1.0`

Compare Source

Features (types)

Export TemplateExpression type. (#1049)

`v9.0.2`

Compare Source

Bug fixes (types)

Do not require using --lib dom for TypeScript users (#1043, #1044)
Fix type of the reject option (#1046)

`v9.0.1`

Compare Source

Bug fixes (types)

Fix types not being importable (#1033) 3bdab60
Fix complexity bug with types (#1037) 6cc519b
Fix complexity bug with types (#1035) fee011d

`v9.0.0`

Compare Source

This major release brings many important features including:

Split the output into lines, or progressively iterate over them.
Transform or filter the input/output using simple functions.
Print the output to the terminal while still retrieving it programmatically.
Redirect the input/output from/to a file.
Advanced piping between multiple subprocesses.
Improved verbose mode, for debugging.
More detailed errors, including when terminating subprocesses.
Enhanced template string syntax.
Global/shared options.
Web streams and Transform streams support.
Convert the subprocess to a stream.
New documentation with many examples.

Please check the release post for a high-level overview! For the full list of breaking changes, features and bug fixes, please read below.

Thanks @younggglcy, @koshic, @am0o0 and @codesmith-emmy for your help!

One of the maintainers @ehmicky is looking for a remote full-time position. Specialized in Node.js back-ends and CLIs, he led Netlify Build, Plugins and Configuration for 2.5 years. Feel free to contact him on his website or on LinkedIn!

Breaking changes (not types)

Dropped support for Node.js version <18.19.0 and 20.0.0 - 20.4.0. (834e372)
When the encoding option is 'buffer', the output (result.stdout, result.stderr, result.all) is now an Uint8Array instead of a Buffer. For more information, see this blog post. (by @younggglcy) (#586)

const {stdout} = await execa('node', ['file.js'], {encoding: 'buffer'});
console.log(stdout); // This is now an Uint8Array

Renamed some of the allowed values for the encoding option. (#586, #928)

- await execa('node', ['file.js'], {encoding: null});
+ await execa('node', ['file.js'], {encoding: 'buffer'});

- await execa('node', ['file.js'], {encoding: 'utf-8'});
+ await execa('node', ['file.js'], {encoding: 'utf8'});

- await execa('node', ['file.js'], {encoding: 'UTF8'});
+ await execa('node', ['file.js'], {encoding: 'utf8'});

- await execa('node', ['file.js'], {encoding: 'utf-16le'});
+ await execa('node', ['file.js'], {encoding: 'utf16le'});

- await execa('node', ['file.js'], {encoding: 'ucs2'});
+ await execa('node', ['file.js'], {encoding: 'utf16le'});

- await execa('node', ['file.js'], {encoding: 'ucs-2'});
+ await execa('node', ['file.js'], {encoding: 'utf16le'});

- await execa('node', ['file.js'], {encoding: 'binary'});
+ await execa('node', ['file.js'], {encoding: 'latin1'});

Passing a file path to subprocess.pipeStdout(), subprocess.pipeStderr() and subprocess.pipeAll() has been removed. Instead, a {file: './path'} object should be passed to the stdout or stderr option. (#752)

- await execa('node', ['file.js']).pipeStdout('output.txt');
+ await execa('node', ['file.js'], {stdout: {file: 'output.txt'}});

- await execa('node', ['file.js']).pipeStderr('output.txt');
+ await execa('node', ['file.js'], {stderr: {file: 'output.txt'}});

- await execa('node', ['file.js']).pipeAll('output.txt');
+ await execa('node', ['file.js'], {
+	stdout: {file: 'output.txt'},
+	stderr: {file: 'output.txt'},
+});

Passing a writable stream to subprocess.pipeStdout(), subprocess.pipeStderr() and subprocess.pipeAll() has been removed. Instead, the stream should be passed to the stdout or stderr option. If the stream does not have a file descriptor, ['pipe', stream] should be passed instead. (#752)

- await execa('node', ['file.js']).pipeStdout(stream);
+ await execa('node', ['file.js'], {stdout: ['pipe', stream]});

- await execa('node', ['file.js']).pipeStderr(stream);
+ await execa('node', ['file.js'], {stderr: ['pipe', stream]});

- await execa('node', ['file.js']).pipeAll(stream);
+ await execa('node', ['file.js'], {
+	stdout: ['pipe', stream],
+	stderr: ['pipe', stream],
+});

The subprocess.pipeStdout(), subprocess.pipeStderr() and subprocess.pipeAll() methods have been renamed to subprocess.pipe(). The command and its arguments can be passed to subprocess.pipe() directly, without calling execa() a second time. The from piping option can specify 'stdout' (the default value), 'stderr' or 'all'. (#757)

- await execa('node', ['file.js']).pipeStdout(execa('node', ['other.js']));
+ await execa('node', ['file.js']).pipe('node', ['other.js']);

- await execa('node', ['file.js']).pipeStderr(execa('node', ['other.js']));
+ await execa('node', ['file.js']).pipe('node', ['other.js'], {from: 'stderr'});

- await execa('node', ['file.js']).pipeAll(execa('node', ['other.js']));
+ await execa('node', ['file.js']).pipe('node', ['other.js'], {from: 'all'});

Renamed the signal option to cancelSignal. (#880)

- await execa('node', ['file.js'], {signal: abortController.signal});
+ await execa('node', ['file.js'], {cancelSignal: abortController.signal});

Renamed error.killed to error.isTerminated. (#625)

try {
	await execa('node', ['file.js']);
} catch (error) {
- if (error.killed) {
+ if (error.isTerminated) {
		// ...
	}
}

subprocess.cancel() has been removed. Please use either subprocess.kill() or the cancelSignal option instead. (#711)

- subprocess.cancel();
+ subprocess.kill();

Renamed the forceKillAfterTimeout option to forceKillAfterDelay. Also, it is now passed to execa() instead of subprocess.kill(). (#714, #723)

- const subprocess = execa('node', ['file.js']);
- subprocess.kill('SIGTERM', {forceKillAfterTimeout: 1000});
+ const subprocess = execa('node', ['file.js'], {forceKillAfterDelay: 1000});
+ subprocess.kill('SIGTERM');

The verbose option is now a string enum instead of a boolean. false has been renamed to 'none' and true has been renamed to 'short'. (#884)

- await execa('node', ['file.js'], {verbose: false});
+ await execa('node', ['file.js'], {verbose: 'none'});

- await execa('node', ['file.js'], {verbose: true});
+ await execa('node', ['file.js'], {verbose: 'short'});

The execPath option has been renamed to nodePath. It is now a noop unless the node option is true. Also, it now works even if the preferLocal option is false. (#812, #815)

- await execa('node', ['file.js'], {execPath: './path/to/node'});
+ await execa('node', ['file.js'], {nodePath: './path/to/node'});

The default value for the serialization option is now 'advanced' instead of 'json'. In particular, when calling subprocess.send(object) with an object that contains functions or symbols, those were previously silently removed. Now this will throw an exception. (#905)

- subprocess.send({example: true, getExample() {}});
+ subprocess.send({example: true});

If subprocess.stdout, subprocess.stderr or subprocess.all is manually piped, the .pipe() call must now happen as soon as subprocess is created. Otherwise, the output at the beginning of the subprocess might be missing. (#658, #747)

const subprocess = execa('node', ['file.js']);
- setTimeout(() => {
	subprocess.stdout.pipe(process.stdout);
- }, 0);

Signals passed to subprocess.kill() and to the killSignal option cannot be lowercase anymore. (#1025)

- const subprocess = execa('node', ['file.js'], {killSignal: 'sigterm'});
+ const subprocess = execa('node', ['file.js'], {killSignal: 'SIGTERM'});

- subprocess.kill('sigterm');
+ subprocess.kill('SIGTERM');

Features

Execution

Use the template string syntax with any method (including execa()), as opposed to only $. Conversely, $ can now use the regular array syntax. (#933)
A command's template string can span multiple lines. (#843)
Share options between multiple calls, or set global options, by using execa(options). (#933, #965)
Pass a file URL (as opposed to a file path string) to execa(), execaNode(), the inputFile option, the nodePath option or the shell option. (#630, #631, #632, #635)

Text lines

Split the output into text lines by using the lines option. (#741, #929, #931, #948, #951, #957)
Subprocess is now an async iterable, iterating over the output lines while the subprocess is running. (#923)

Piping multiple subprocesses

Simpler syntax: pass the command directly to subprocess.pipe() without calling execa(). A template string can also be used. (#840, #859, #864)
Wait for both subprocesses to complete. Error handling has been improved too. (#757, #778, #834, #854)
Retrieve the result of each subprocess (not only the last one) by using result.pipedFrom and error.pipedFrom. (#834)
Pipe 1 or many subprocesses to 1 or many subprocesses. (#834)
Pipe subprocesses using other file descriptors than stdin/stdout/stderr by using the from and to piping options. (#757, #834, #903, #920)
Cancel piping subprocesses by using the unpipeSignal piping option. (#834, #852)

Input/output

Pass an array with multiple values to the stdin, stdout and stderr options. For example, stdout: ['inherit', 'pipe'] prints the output to the terminal while still returning it as result.stdout. (#643, #765, #941, #954)
Redirect the input/output from/to a file by passing a {file: './path'} object or a file URL to the stdin, stdout or stderr option. (#610, #614, #621, #671, #1004)
Transform or filter the input/output by passing a generator function to the stdin, stdout or stderr option. (#693, #697, #698, #699, #709, #736, #737, #739, #740, #746, #748, #755, #756, #780, #783, #867, #915, #916, #917, #919, #924, #926, #945, #969)
Provide some binary input by passing an Uint8Array to the input or stdin option. (834e372, #670, #1029)
Provide some progressive input by passing a sync/async iterable to the stdin option. (#604, #944)
Provide multiple inputs by combining the stdin, input and inputFile options. (#666)
Return other file descriptors than result.stdout and result.stderr by using result.stdio. (#676)
Specify different values for stdout and stderr with the following options: verbose, lines, stripFinalNewline, maxBuffer, buffer. (#966, #970, #971, #972, #973, #974)

Streams

Redirect the input/output from/to a web stream by passing a ReadableStream or WritableStream to the stdin, stdout or stderr option. (#615, #619, #645)
Transform or filter the input/output by passing a Duplex, Node.js Transform or web TransformStream to the stdin, stdout or stderr option. (#937, #938)
Convert the subprocess to a stream by using subprocess.readable(), subprocess.writable() or subprocess.duplex(). (#912, #922, #958)

Verbose mode

Print the subprocess' completion, duration and errors with the verbose: 'short' or verbose: 'full' option. (#887, #890)
Print the subprocess' output with the verbose: 'full' option. (#884, #950, #962, #990)
Prettier formatting and colors with the verbose option. (#883, #893, #894)

Debugging

Retrieve the subprocess' duration by using result.durationMs and error.durationMs. (#896)
Retrieve the subprocess' current directory by using result.cwd. Previously only error.cwd was available. Also, result.cwd and error.cwd are now normalized to absolute file paths. (#803)
Printing result.escapedCommand in a terminal is now safe. (#875)

Errors

The ExecaError and ExecaSyncError classes are now exported. (#911)
Find the subprocess failure's root cause by using error.cause. (#911)
Know whether the subprocess failed due to the maxBuffer option by using error.isMaxBuffer. (#963)
Improved error.message: error.stdout and error.stderr are now interleaved if the all option is true. Additional file descriptors are now printed too. Also, the formatting has been improved. (#676, #705, #991, #992)
Control characters in error.message are now escaped, so they don't result in visual bugs when printed in a terminal. (#879)
Improved stack trace when an error event is emitted on subprocess.stdout or subprocess.stderr. (#814)

Termination

Specify an error message or stack trace when terminating a subprocess by passing an error instance to subprocess.kill(). (#811, #836, #1023)
The forceKillAfterDelay and killSignal options now apply to terminations due not only to subprocess.kill() but also to the cancelSignal, timeout, maxBuffer and cleanup options. (#714, #728)

Node.js files

Use the nodePath and nodeOptions options with any method, as opposed to only execaNode(), by passing the node: true option. (#804, #812, #815)
When using execaNode() or the node: true option, the current Node.js version is now inherited deeply. If the subprocess spawns other subprocesses, they will all use the same Node.js version. (#812, #815, #1011)

Synchronous execution

Use the all and buffer: false options with execaSync(), as opposed to only execa(). (#953, #956)
Added the $.s alias for $.sync. (#594)

Inter-process communication

Use the ipc: true option, as opposed to the more verbose stdio: ['pipe', 'pipe', 'pipe', 'ipc'] option. (#794)

Input validation

Improved the validation of the input, timeout, cwd, detached, cancelSignal and encoding options. (#668, #715, #803, #928, #940)
Improved the validation of the arguments passed to execa() and the other exported methods. (#838, #873, #899)
Improved the validation of signals passed to subprocess.kill() and to the killSignal option. (#1025)

Bug fixes

Fixed passing undefined values as options. This now uses the option's default value. (#712)
Fixed the process crashing when the inputFile option points to a missing file. (#609)
Fixed the process crashing when the buffer option is false and subprocess.stdout errors. (#729)
Fixed the process crashing when passing 'overlapped' to the stdout or stderr option with execaSync(). (#949)
Fixed the process crashing when multiple 'error' events are emitted on the subprocess. (#790)
Fixed the [reject: false](docs/api.md#options

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.

vercel · 2024-05-29T11:54:36Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
fnm	Ready	Preview, Comment	Jan 23, 2026 5:07pm

changeset-bot · 2024-05-29T11:54:38Z

⚠️ No Changeset found

Latest commit: 275b75c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

renovate bot added the PR: Dependency Update A dependency was updated label May 29, 2024

renovate bot enabled auto-merge (squash) May 29, 2024 11:54

vercel bot deployed to Preview May 29, 2024 11:54 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from b3606fb to 7081004 Compare May 29, 2024 11:58

vercel bot deployed to Preview May 29, 2024 11:58 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 7081004 to d774b09 Compare May 29, 2024 11:58

vercel bot deployed to Preview May 29, 2024 11:58 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from d774b09 to bce1a5d Compare May 29, 2024 11:59

vercel bot deployed to Preview May 29, 2024 11:59 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from bce1a5d to 1126ce1 Compare May 29, 2024 14:56

vercel bot deployed to Preview May 29, 2024 14:56 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 1126ce1 to 9168948 Compare May 29, 2024 15:10

vercel bot deployed to Preview May 29, 2024 15:10 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 9168948 to c2c8590 Compare May 29, 2024 15:27

vercel bot deployed to Preview May 29, 2024 15:27 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from c2c8590 to 7d0d87d Compare May 29, 2024 16:04

vercel bot deployed to Preview May 29, 2024 16:05 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 7d0d87d to dbe15c9 Compare May 29, 2024 16:45

vercel bot deployed to Preview May 29, 2024 16:45 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from dbe15c9 to 7a81ece Compare May 29, 2024 16:49

vercel bot deployed to Preview May 29, 2024 16:49 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 7a81ece to 6d55414 Compare May 30, 2024 03:41

vercel bot deployed to Preview May 30, 2024 03:41 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 6d55414 to 7a956ae Compare June 1, 2024 22:18

vercel bot deployed to Preview June 1, 2024 22:18 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 7a956ae to df008e2 Compare June 4, 2024 07:13

vercel bot deployed to Preview June 4, 2024 07:14 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from df008e2 to f825e11 Compare June 4, 2024 07:16

vercel bot deployed to Preview December 15, 2025 10:07 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from dee7156 to 4af9ce9 Compare December 16, 2025 02:56

vercel bot deployed to Preview December 16, 2025 02:57 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 4af9ce9 to 6836410 Compare December 31, 2025 06:00

vercel bot deployed to Preview December 31, 2025 06:00 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 6836410 to d6e8de0 Compare December 31, 2025 20:02

vercel bot deployed to Preview December 31, 2025 20:03 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from d6e8de0 to 601a136 Compare January 1, 2026 07:04

vercel bot deployed to Preview January 1, 2026 07:04 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 601a136 to faa5efb Compare January 4, 2026 09:54

vercel bot deployed to Preview January 4, 2026 09:54 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from faa5efb to 8ec2839 Compare January 8, 2026 18:16

vercel bot deployed to Preview January 8, 2026 18:16 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 8ec2839 to c0424b4 Compare January 10, 2026 01:16

vercel bot deployed to Preview January 10, 2026 01:16 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from c0424b4 to 481a58a Compare January 10, 2026 04:24

vercel bot deployed to Preview January 10, 2026 04:24 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 481a58a to 1581da9 Compare January 10, 2026 17:52

vercel bot deployed to Preview January 10, 2026 17:52 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 1581da9 to a4165ff Compare January 13, 2026 17:44

vercel bot deployed to Preview January 13, 2026 17:44 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from a4165ff to 1a76d54 Compare January 15, 2026 18:14

vercel bot deployed to Preview January 15, 2026 18:14 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 1a76d54 to 1223522 Compare January 19, 2026 19:48

vercel bot deployed to Preview January 19, 2026 19:49 View deployment

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 1223522 to 82becca Compare January 22, 2026 21:59

vercel bot deployed to Preview January 22, 2026 21:59 View deployment

chore(deps): update all dev dependencies

275b75c

renovate bot force-pushed the renovate/major-all-dev-dependencies branch from 82becca to 275b75c Compare January 23, 2026 17:06

vercel bot deployed to Preview January 23, 2026 17:07 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update all dev dependencies (major) #1142

chore(deps): update all dev dependencies (major) #1142

renovate bot commented May 29, 2024 •

edited

Loading

Uh oh!

vercel bot commented May 29, 2024 •

edited

Loading

Uh oh!

changeset-bot bot commented May 29, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chore(deps): update all dev dependencies (major) #1142

Are you sure you want to change the base?

chore(deps): update all dev dependencies (major) #1142

Conversation

renovate bot commented May 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Features

BREAKING CHANGES

Bug fixes

Bug fixes

Features

Bug fixes

Features

Bug fixes

Documentation

Bugs

Bugs (types)

Documentation

Features

Deprecations

Features

Types

Bug fixes

Features (types)

Bug fixes (types)

Bug fixes (types)

Breaking changes (not types)

Features

Execution

Text lines

Piping multiple subprocesses

Input/output

Streams

Verbose mode

Debugging

Errors

Termination

Node.js files

Synchronous execution

Inter-process communication

Input validation

Bug fixes

Configuration

Uh oh!

vercel bot commented May 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

changeset-bot bot commented May 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented May 29, 2024 •

edited

Loading

vercel bot commented May 29, 2024 •

edited

Loading

changeset-bot bot commented May 29, 2024 •

edited

Loading