rspack chore(deps): update npm dev dependencies (major)

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	`^18.11.18` -> `^22.0.0`
@types/node (source)	`20.12.7` -> `22.2.0`
@types/rimraf	`3.0.2` -> `4.0.5`
chalk	`^4.1.0` -> `^5.0.0`
coffee-loader	`^1.0.0` -> `^5.0.0`
copy-webpack-plugin	`5.1.2` -> `12.0.2`
css-loader	`^6.11.0` -> `^7.0.0`
execa	`^5.0.0` -> `^9.0.0`
glob	`^10.3.10` -> `^11.0.0`
internal-ip	`6.2.0` -> `8.0.0`
prettier-2 (source)	`2.8.8` -> `3.3.3`
rimraf	`3.0.2` -> `6.0.1`
style-loader	`^3.3.3` -> `^4.0.0`
zod-validation-error	`1.3.1` -> `3.3.1`
zx	`7.2.3` -> `8.1.4`

Release Notes

chalk/chalk (chalk)

`v5.3.0`

Compare Source

Add sideEffects field to package.json 5aafc0a
Add support for Gitea Actions (#603) 29b8569

`v5.2.0`

Compare Source

Improve Deno compatibility (#579) 7443e9f
Detect true-color support for GitHub Actions (#579) 7443e9f
Detect true-color support for Kitty terminal (#579) 7443e9f
Fix test for Azure DevOps environment (#579) 7443e9f

`v5.1.2`

Compare Source

Fix exported styles names (#569) a34bcf6

`v5.1.1`

Compare Source

Improved the names of exports introduced in 5.1.0 (#567) 6e0df05
- We of course preserved the old names.

`v5.1.0`

Compare Source

Expose style names (#566) d7d7571

`v5.0.1`

Compare Source

Add main field to package.json for backwards compatibility with some developer tools 85f7e96

`v5.0.0`

Compare Source

Breaking

This package is now pure ESM. Please read this.
- If you use TypeScript, you need to use TypeScript 4.7 or later. Why.
- If you use a bundler, make sure it supports ESM and that you have correctly configured it for ESM.
- The Chalk issue tracker is not a support channel for your favorite build/bundler tool.
- It's totally fine to stay on Chalk v4. It's been stable for years.
Require Node.js 12.20 fa16f4e
Move some properties off the default export to individual named exports:
- chalk.Instance → Chalk
- chalk.supportsColor → supportsColor
- chalk.stderr → chalkStderr
- chalk.stderr.supportsColor → supportsColorStderr
Remove .keyword(), .hsl(), .hsv(), .hwb(), and .ansi() coloring methods (#433) 4cf2e40
- These were not commonly used and added a lot of bloat to Chalk. You can achieve the same by using the color-convert package.
The tagged template literal support moved into a separate package: chalk-template (#524) c987c61

-import chalk from 'chalk';
+import chalkTemplate from 'chalk-template';

-chalk`2 + 3 = {bold ${2 + 3}}`;
+chalkTemplate`2 + 3 = {bold ${2 + 3}}`;

Improvements

Bundle dependencies 04fdbd6
- This means Chalk no longer has any dependencies 🎉
The install size is less than half of v4.
Add overline style (#433) 4cf2e40
Preserve function prototype methods (#434) 0fba91b

webpack-contrib/coffee-loader (coffee-loader)

`v5.0.0`

Compare Source

⚠ BREAKING CHANGES

minimum supported Node.js version is 18.12.0 (#174) (1d4adfd)

`v4.0.0`

Compare Source

⚠ BREAKING CHANGES

minimum supported Node.js version is 14.15.0

`v3.0.0`

Compare Source

⚠ BREAKING CHANGES

minimum supported Node.js version is 12.13.0

`v2.0.0`

Compare Source

⚠ BREAKING CHANGES

minimum supported webpack version is 5

1.0.1 (2020-10-09)

Chore

update schema-utils

1.0.0 (2020-05-22)

BREAKING CHANGES

minimum required Node.js version is 10.13.0
minimum required webpack version is 4.0.0
minimum required coffeescript version is 2.0.0
default value for the sourceMap option based on the value of the compiler.devtool option

Features

respect the compiler.devtool value for the sourceMap option
developer can override CoffeeScript options

Bug Fixes

fix error reporting

webpack-contrib/copy-webpack-plugin (copy-webpack-plugin)

`v12.0.0`

Compare Source

⚠ BREAKING CHANGES

update globby to 14.0.0
minimum supported Node.js version is 18.12.0 (#759) (a5b7d06)

`v11.0.0`

Compare Source

⚠ BREAKING CHANGES

minimum supported Node.js version is 14.15.0

build

drop node v12 (#691) (675c676)

10.2.4 (2022-01-31)

Bug Fixes

types (#666) (a1c2308)

10.2.3 (2022-01-29)

Bug Fixes

async to support (fd095fb)

10.2.2 (2022-01-28)

Bug Fixes

types (#664) (f58470e)

10.2.1 (2022-01-20)

Bug Fixes

types (#661) (324aecb)

`v10.2.0`

Compare Source

Features

removed cjs wrapper and generated types in commonjs format (export = and namespaces used in types), now you can directly use exported types (#654) (5901006)

`v10.1.0`

Compare Source

Features

added types (#650) (1aa5b2d)

Bug Fixes

expand lint-staged (#649) (f8aad69)

`v10.0.0`

Compare Source

⚠ BREAKING CHANGES

minimum supported Node.js version is 12.20.0
update globby to 12.0.2 version

`v9.1.0`

Compare Source

Features

output helpful descriptions and links on errors (#625) (396bed6)

Bug Fixes

compatibility with Node.js 17 (20af0c7)

9.0.1 (2021-06-25)

Chore

update serialize-javascript

`v9.0.0`

Compare Source

⚠ BREAKING CHANGES

minimum supported Node.js version is 12.13.0

8.1.1 (2021-04-06)

Bug Fixes

stage for processing assets (#600) (#601) (d8fa32a)

`v8.1.0`

Compare Source

Features

added the transformAll option (#596) (dde71f0)

`v8.0.0`

Compare Source

⚠ BREAKING CHANGES

logic for some placeholders was changed:
- [hash] and [fullhash] works as in webpack (i.e. it is hash of build, not content hash of file), to migrate change [name].[hash].[ext] to [name].[contenthash][ext]
- [ext] doesn't require . (dot) before, i.e. change [name].[ext] to [name][ext]
- [<hashType>:contenthash:<digestType>:<length>] and [<hashType>:hash:<digestType>:<length>] is not supported anymore, you can use output.hashDigest, output.hashDigestLength and output.hashFunction options to setup it
- [N] was removed in favor of using the to option as a function
- [folder] was removed
- [emoji] was removed

Features

added priority option (#590) (ea610bc)

`v7.0.0`

Compare Source

⚠ BREAKING CHANGES

minimum supported webpack version is 5
the flatten option was removed in favor [name].[ext] value for the to option,
the transformPath option was removed in favor Function type of the to option, look at examples
the cacheTransform option was removed in favor Object type of the transform option, look at examples
migration on the compilation.hooks.processAssets hook
empty filtered paths throw an error, you can disable this behaviour using the noErrorOnMissing option

`v6.4.1`

Compare Source

6.4.1 (2020-12-16)

Bug Fixes

compatibility with webpack 4 file system (#570) (720026a)

`v6.4.0`

Compare Source

Features

added the info option (db53937)
added type Function for the to option (#563) (9bc5416)

6.3.2 (2020-11-19)

Bug Fixes

watching directories (#558) (7b58fd9)

6.3.1 (2020-11-13)

Bug Fixes

watching (#555) (b996923)

`v6.3.0`

Compare Source

Features

added the sourceFilename info (original source filename) to assets info (#542) (db2e3bf)
persistent cache between compilations (webpack@5 only) (#541) (c892451)

6.2.1 (2020-10-09)

Chore

update schema-utils

`v6.2.0`

Compare Source

Features

use webpack input filesystem (only webpack@5) (#531) (6f2f455)

6.1.1 (2020-09-18)

Chore

updated serialize-javascript

`v6.1.0`

Compare Source

Features

added filter option (#524) (1496f85)
added the copied flag to asset info (09b1dc9)
added the immutable flag to asset info with hash in name (#525) (a1989d5)
webpack@5: improve stats output for copied files

6.0.4 (2020-08-29)

Bug Fixes

compatibility with webpack@5 (#522) (714af2f)

6.0.3 (2020-06-30)

Bug Fixes

do not execute on a child compiler (42f27c7)

6.0.2 (2020-06-03)

Bug Fixes

security problem
compatibility with 10.13 version of Node.js

6.0.1 (2020-05-16)

Bug Fixes

concurrency writing assets (#484) (bfc712d)
escaping special characters in the context option (0e62695)

`v6.0.0`

Compare Source

⚠ BREAKING CHANGES

minimum supported Node.js version is 10.13,
the plugin now accepts an object, you should change new CopyPlugin(patterns, options) to new CopyPlugin({ patterns, options })
migrate on compilation.additionalAssets hook
the ignore option (which accepted micromatch syntax) was removed in favor globOptions.ignore (which accepts fast-glob pattern-syntax)
the test option was removed in favor the transformPath option
the cache option was renamed to the cacheTransform option, cacheTransform option should have only directory and keys properties when it is an object
global context and ignore options were removed in favor patten.context and pattern.globOptions.ignore options
the missing file error is now an error, before it was a warning
the from option now can only be a string, if you use { from: { glob: 'directory/**', dot: false } } changed it to { from: 'directory/**', globOptions: { dot: false } }
the copyUnmodified was removed without replacements
the 2 version of webpack-dev-server is not supported anymore
the logLevel was removed in favor the infrastructureLogging.level option, please read the documentation

Features

implement the concurrency option (#466) (c176d7d)
implement the directory option for the cacheTransform option (29254e3)
implement the noErrorOnMissing option (#475) (e3803ce)
migrate on webpack built-in logger (#446) (5af02bc)

Bug Fixes

asset size (197b0d8)
persist assets between rebuilds (57f3e61)

5.1.1 (2019-12-12)

Bug Fixes

allow to setup empty array (#425) (3b79595)

webpack-contrib/css-loader (css-loader)

`v7.1.0`

Compare Source

Features

added the getJSON option to output CSS modules mapping (#1577) (af834b4)

`v7.0.0`

Compare Source

⚠ BREAKING CHANGES

The modules.namedExport option is true by default if you enable the esModule option

Migration guide:

Before:

import style from "./style.css";

console.log(style.myClass);

After:

import * as style from "./style.css";

console.log(style.myClass);

The modules.exportLocalsConvention has the value as-is when the modules.namedExport option is true and you don't specify a value
Minimum supported webpack version is 5.27.0
Minimum supported Node.js version is 18.12.0

Features

The modules.namedExports option works fine with any modules.exportLocalsConvention values (f96a110)
Added dashed variants for the modules.exportLocalsConvention options (40e1668)

sindresorhus/execa (execa)

`v9.3.0`

Compare Source

Features

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

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

Minimal supported Node.js version is now 18.19.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',

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 8am on wednesday" in timezone Asia/Shanghai, 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](https://togithub.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View the [repository job log](https://developer.mend.io/github/web-infra-dev/rspack).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yMDAuMCIsInVwZGF0ZWRJblZlciI6IjM4LjIwLjEiLCJ0YXJnZXRCcmFuY2giOiJtYWluIn0=-->

Feb 20 '24 16:02 renovate[bot]

Need to fix or ignore some of these breaking changes

Feb 21 '24 05:02 Boshen

rimraf:

v4 to v5 There is no default export anymore. Import the functions directly using, e.g., import { rimrafSync } from 'rimraf.

Feb 27 '24 08:02 Boshen

invalid rimraf options

Feb 27 '24 11:02 Boshen

execa and internal-ip are esm only.

copy-webpack-plugin and sass-loader breaks.

Feb 29 '24 08:02 Boshen

Deploy Preview for rspack ready!

Name	Link
Latest commit	42c598ee4e2dd15a5f22ad296f967c85219c5000
Latest deploy log	https://app.netlify.com/sites/rspack/deploys/66c55de6b168d100089ce0b7
Deploy Preview	https://deploy-preview-5728--rspack.netlify.app
Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

May 15 '24 04:05 netlify[bot]

chore(deps): update npm dev dependencies (major)

Release Notes

Breaking

Improvements

⚠ BREAKING CHANGES

⚠ BREAKING CHANGES

⚠ BREAKING CHANGES

⚠ BREAKING CHANGES

1.0.1 (2020-10-09)

Chore

1.0.0 (2020-05-22)

BREAKING CHANGES

Features

Bug Fixes

⚠ BREAKING CHANGES

⚠ BREAKING CHANGES

build

10.2.4 (2022-01-31)

Bug Fixes

10.2.3 (2022-01-29)

Bug Fixes

10.2.2 (2022-01-28)

Bug Fixes

10.2.1 (2022-01-20)

Bug Fixes

Features

Features

Bug Fixes

⚠ BREAKING CHANGES

Features

Bug Fixes

9.0.1 (2021-06-25)

Chore

⚠ BREAKING CHANGES

8.1.1 (2021-04-06)

Bug Fixes

Features

⚠ BREAKING CHANGES

Features

⚠ BREAKING CHANGES

6.4.1 (2020-12-16)

Bug Fixes

Features

6.3.2 (2020-11-19)

Bug Fixes

6.3.1 (2020-11-13)

Bug Fixes

Features

6.2.1 (2020-10-09)

Chore

Features

6.1.1 (2020-09-18)

Chore

Features

6.0.4 (2020-08-29)

Bug Fixes

6.0.3 (2020-06-30)

Bug Fixes

6.0.2 (2020-06-03)

Bug Fixes

6.0.1 (2020-05-16)

Bug Fixes

⚠ BREAKING CHANGES

Features

Bug Fixes

5.1.1 (2019-12-12)

Bug Fixes

Features

⚠ BREAKING CHANGES

Features

Features

Deprecations

Features

Types

Bug fixes

Features (types)

Bug fixes (types)

Bug fixes (types)

Breaking changes

✅ Deploy Preview for rspack ready!

Deploy Preview for rspack ready!