chore(deps-dev): bump the development group with 5 updates #205

dependabot · 2024-07-01T15:00:24Z

Bumps the development group with 5 updates:

Package	From	To
@vitest/coverage-istanbul	`1.4.0`	`1.6.0`
esbuild	`0.20.2`	`0.22.0`
rimraf	`5.0.5`	`5.0.7`
vitest	`1.4.0`	`1.6.0`
vitest-when	`0.3.1`	`0.4.0`

Updates @vitest/coverage-istanbul from 1.4.0 to 1.6.0

Release notes

Sourced from @vitest/coverage-istanbul's releases.

v1.6.0

   🚀 Features

Support standalone mode - by @sheremet-va in vitest-dev/vitest#5565 (bdce0)

Custom "snapshotEnvironment" option - by @sheremet-va in vitest-dev/vitest#5449 (30f72)

benchmark: Support comparing benchmark result - by @hi-ogawa and @sheremet-va in vitest-dev/vitest#5398 (f8d3d)

browser: Allow injecting scripts - by @sheremet-va in vitest-dev/vitest#5656 (21e58)

reporter: Support includeConsoleOutput and addFileAttribute in junit - by @hi-ogawa in vitest-dev/vitest#5659 (2f913)

ui: Sort items by file name - by @btea in vitest-dev/vitest#5652 (1f726)

   🐞 Bug Fixes

Keep order of arguments for .each in custom task collectors - by @sheremet-va in vitest-dev/vitest#5640 (7d57c)

Call resolveId('vitest') after buildStart - by @hi-ogawa in vitest-dev/vitest#5646 (f5faf)

Hash the name of the file when caching - by @sheremet-va in vitest-dev/vitest#5654 (c9e68)

Don't panic on empty files in node_modules - by @sheremet-va (40c29)

Use toJSON for error serialization - by @hi-ogawa in vitest-dev/vitest#5526 (19a21)

coverage:

Exclude *.test-d.* by default - by @MindfulPol in vitest-dev/vitest#5634 (bfe8a)

Apply vite-node's wrapper only to executed files - by @AriPerkkio in vitest-dev/vitest#5642 (c9883)

vm:

Support network imports - by @sheremet-va in vitest-dev/vitest#5610 (103a6)

   🏎 Performance

Improve performance of forks pool - by @sheremet-va in vitest-dev/vitest#5592 (d8304)

Unnecessary rpc call when coverage is disabled - by @AriPerkkio in vitest-dev/vitest#5658 (c5712)

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

Use package.json name for a workspace project if not provided - by @sheremet-va in vitest-dev/vitest#5608 (48fba)

Backport jest iterable equality within object - by @sukovanej in vitest-dev/vitest#5621 (30e5d)

browser: Support benchmark - by @hi-ogawa in vitest-dev/vitest#5622 (becab)

reporter: Use default error formatter for JUnit - by @hi-ogawa in vitest-dev/vitest#5629 (20060)

    View changes on GitHub

v1.5.2

   🐞 Bug Fixes

Check for null before storing in weakmap - by @sheremet-va (ce368)

    View changes on GitHub

v1.5.1

   🚀 Features

... (truncated)

Commits

6b29f3d chore: release v1.6.0
a52964b chore: release v1.5.3
81f57f4 chore: release v1.5.2
1be4510 chore: release v1.5.1
80265b4 fix(coverage): thresholds to compare files relative to root (#5574)
ea3c16e fix(coverage): prevent crash when cleanOnRerun is disabled (#5540)
9e7a01c chore: release v1.5.0
See full diff in compare view

Updates esbuild from 0.20.2 to 0.22.0

Release notes

Sourced from esbuild's releases.

v0.22.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.
Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).
Drop support for older platforms (#3802)

This release drops support for the following operating systems:

Windows 7

Windows 8

Windows Server 2008

Windows Server 2012

This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version
In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).
Update await using behavior to match TypeScript

TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

Allow es2024 as a target environment

The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)

With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

This was contributed by @ikmckenz.

Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)

The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a .wasm file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.22.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.
Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).
Drop support for older platforms (#3802)

This release drops support for the following operating systems:

Windows 7

Windows 8

Windows Server 2008

Windows Server 2012

This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version
In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).
Update await using behavior to match TypeScript

TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

Allow es2024 as a target environment

The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)

With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

This was contributed by @ikmckenz.

Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)

... (truncated)

Commits

80c6e6e publish 0.22.0 to npm
196dcad fix #1874: node defaults to --packages=external
3f57db8 release notes for #3539
91663db Provide API to create a custom esbuild CLI with plugins (#3539)
e01c0e0 also mention #3665 in release notes
65711b3 release notes for #3674
63eb814 Add OpenBSD arm64 (#3674)
b722000 fix #3300, fix #3779: add @esbuild/wasi-preview1
6679ec8 fix: verbose analyse output improperly trimmed (#3785)
94f09ea fix #3790: warn about incorrect onResolve plugin
Additional commits viewable in compare view

Updates rimraf from 5.0.5 to 5.0.7

Commits

fb974ad 5.0.7
8ba2442 engines: need 14.18, where 'node:path' shows up
39340d1 update deps
e729f76 5.0.6
4472c0e DOC: add that it is cross platform
46b425f Improve readability of README
a3b93ed update deps, format codes
d2fa213 update devDeps
f3b2bf1 Upgrade GitHub Actions
81c631e remove FUNDING.yml (coming from .github repo now)
See full diff in compare view

Updates vitest from 1.4.0 to 1.6.0

Release notes

Sourced from vitest's releases.

v1.6.0

   🚀 Features

Support standalone mode - by @sheremet-va in vitest-dev/vitest#5565 (bdce0)

Custom "snapshotEnvironment" option - by @sheremet-va in vitest-dev/vitest#5449 (30f72)

benchmark: Support comparing benchmark result - by @hi-ogawa and @sheremet-va in vitest-dev/vitest#5398 (f8d3d)

browser: Allow injecting scripts - by @sheremet-va in vitest-dev/vitest#5656 (21e58)

reporter: Support includeConsoleOutput and addFileAttribute in junit - by @hi-ogawa in vitest-dev/vitest#5659 (2f913)

ui: Sort items by file name - by @btea in vitest-dev/vitest#5652 (1f726)

   🐞 Bug Fixes

Keep order of arguments for .each in custom task collectors - by @sheremet-va in vitest-dev/vitest#5640 (7d57c)

Call resolveId('vitest') after buildStart - by @hi-ogawa in vitest-dev/vitest#5646 (f5faf)

Hash the name of the file when caching - by @sheremet-va in vitest-dev/vitest#5654 (c9e68)

Don't panic on empty files in node_modules - by @sheremet-va (40c29)

Use toJSON for error serialization - by @hi-ogawa in vitest-dev/vitest#5526 (19a21)

coverage:

Exclude *.test-d.* by default - by @MindfulPol in vitest-dev/vitest#5634 (bfe8a)

Apply vite-node's wrapper only to executed files - by @AriPerkkio in vitest-dev/vitest#5642 (c9883)

vm:

Support network imports - by @sheremet-va in vitest-dev/vitest#5610 (103a6)

   🏎 Performance

Improve performance of forks pool - by @sheremet-va in vitest-dev/vitest#5592 (d8304)

Unnecessary rpc call when coverage is disabled - by @AriPerkkio in vitest-dev/vitest#5658 (c5712)

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

Use package.json name for a workspace project if not provided - by @sheremet-va in vitest-dev/vitest#5608 (48fba)

Backport jest iterable equality within object - by @sukovanej in vitest-dev/vitest#5621 (30e5d)

browser: Support benchmark - by @hi-ogawa in vitest-dev/vitest#5622 (becab)

reporter: Use default error formatter for JUnit - by @hi-ogawa in vitest-dev/vitest#5629 (20060)

    View changes on GitHub

v1.5.2

   🐞 Bug Fixes

Check for null before storing in weakmap - by @sheremet-va (ce368)

    View changes on GitHub

v1.5.1

   🚀 Features

... (truncated)

Commits

6b29f3d chore: release v1.6.0
f8d3d22 feat(benchmark): support comparing benchmark result (#5398)
21e58bd feat(browser): allow injecting scripts (#5656)
30f728b feat: custom "snapshotEnvironment" option (#5449)
2f91322 feat(reporter): support includeConsoleOutput and addFileAttribute in juni...
c571276 perf: unnecessary rpc call when coverage is disabled (#5658)
bdce0a2 feat: support standalone mode (#5565)
40c299f fix: don't panic on empty files in node_modules
c9e68ce fix: hash the name of the file when caching (#5654)
f5faf42 fix: call resolveId('vitest') after buildStart (#5646)
Additional commits viewable in compare view

Updates vitest-when from 0.3.1 to 0.4.0

Commits

2978911 chore(release): 0.4.0
9ac6268 feat(debug): add debug utility (#11)
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the development group with 5 updates: | Package | From | To | | --- | --- | --- | | [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul) | `1.4.0` | `1.6.0` | | [esbuild](https://github.com/evanw/esbuild) | `0.20.2` | `0.22.0` | | [rimraf](https://github.com/isaacs/rimraf) | `5.0.5` | `5.0.7` | | [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `1.4.0` | `1.6.0` | | [vitest-when](https://github.com/mcous/vitest-when) | `0.3.1` | `0.4.0` | Updates `@vitest/coverage-istanbul` from 1.4.0 to 1.6.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.0/packages/coverage-istanbul) Updates `esbuild` from 0.20.2 to 0.22.0 - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md) - [Commits](evanw/esbuild@v0.20.2...v0.22.0) Updates `rimraf` from 5.0.5 to 5.0.7 - [Changelog](https://github.com/isaacs/rimraf/blob/main/CHANGELOG.md) - [Commits](isaacs/rimraf@v5.0.5...v5.0.7) Updates `vitest` from 1.4.0 to 1.6.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.0/packages/vitest) Updates `vitest-when` from 0.3.1 to 0.4.0 - [Commits](mcous/vitest-when@v0.3.1...v0.4.0) --- updated-dependencies: - dependency-name: "@vitest/coverage-istanbul" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development - dependency-name: esbuild dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development - dependency-name: rimraf dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development - dependency-name: vitest-when dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2024-07-06T14:08:19Z

Looks like these dependencies are updatable in another way, so this is no longer needed.

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jul 1, 2024

dependabot bot closed this Jul 6, 2024

dependabot bot deleted the dependabot/npm_and_yarn/development-cb6110b07a branch July 6, 2024 14:08

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps-dev): bump the development group with 5 updates #205

chore(deps-dev): bump the development group with 5 updates #205

Uh oh!

dependabot bot commented on behalf of github Jul 1, 2024 •

edited

Loading

Uh oh!

dependabot bot commented on behalf of github Jul 6, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chore(deps-dev): bump the development group with 5 updates #205

chore(deps-dev): bump the development group with 5 updates #205

Uh oh!

Conversation

dependabot bot commented on behalf of github Jul 1, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v1.6.0

🚀 Features

🐞 Bug Fixes

🏎 Performance

View changes on GitHub

v1.5.3

🐞 Bug Fixes

View changes on GitHub

v1.5.2

🐞 Bug Fixes

View changes on GitHub

v1.5.1

🚀 Features

v0.22.0

0.22.0

v1.6.0

🚀 Features

🐞 Bug Fixes

🏎 Performance

View changes on GitHub

v1.5.3

🐞 Bug Fixes

View changes on GitHub

v1.5.2

🐞 Bug Fixes

View changes on GitHub

v1.5.1

🚀 Features

Uh oh!

dependabot bot commented on behalf of github Jul 6, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

dependabot bot commented on behalf of github Jul 1, 2024 •

edited

Loading