chore(deps-dev): bump the development group across 1 directory with 4 updates #215

dependabot · 2024-10-01T14:04:52Z

Bumps the development group with 3 updates in the / directory: @vitest/coverage-istanbul, concurrently and esbuild.

Updates @vitest/coverage-istanbul from 2.0.5 to 2.1.1

Release notes

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

v2.1.1

🐞 Bug Fixes

browser:

Make example test callbacks async - by @aqandrew in vitest-dev/vitest#6484 (16aa7)

Optimize vitest-browser-vue correctly - by @sheremet-va in vitest-dev/vitest#6490 (5cbb0)

workspace:

Resolve glob pattern once to avoid name collision - by @sheremet-va in vitest-dev/vitest#6489 (36b5a)

View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:
test('renders blog posts', async () => {
  const screen = page.render(<Blog />)
await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()
const [firstPost] = screen.getByRole('listitem').all()
await firstPost.getByRole('button', { name: 'Delete' }).click()
expect(screen.getByRole('listitem').all()).toHaveLength(3)
})
You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

workspace:

Correctly resolve workspace globs and file paths - by @sheremet-va in vitest-dev/vitest#6316 (afdcb)

This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)

For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.

This change doesn't affect non-glob usage.

🚀 Features

api:

Make spec into a class instead of a tuple - by @sheremet-va in vitest-dev/vitest#6355 (874a1)

browser:

Move page.config to server.config, add more docs - by @sheremet-va in vitest-dev/vitest#6252 (af2b8)

Make iframe scalable, improve documentation - by @sheremet-va in vitest-dev/vitest#6257 (74ca1)

Introduce built-in locators - by @sheremet-va in vitest-dev/vitest#6084 (3347f)

Support v8 coverage - by @AriPerkkio in vitest-dev/vitest#6273 (34199)

Support userEvent.upload in playwright provider - by @sheremet-va in vitest-dev/vitest#6442 (cf148)

Support --inspect - by @AriPerkkio in vitest-dev/vitest#6433 (0499a)

Support --inspect-brk - by @AriPerkkio in vitest-dev/vitest#6434 (7ab0f)

... (truncated)

Commits

699055e chore: release v2.1.1
9f1fd18 chore: release v2.1.0
b2be23e chore: release v2.1.0-beta.7
8ac7011 chore: release v2.1.0-beta.6
da52d23 fix(coverage): use project specific vitenode for uncovered files (#6044)
5932a7f feat(coverage): add --exclude-after-remap (#6309)
34199bd feat(browser): support v8 coverage (#6273)
72056b5 chore: release v2.1.0-beta.5
e662c7b fix(coverage): warn if vitest and @vitest/* versions don't match (#6317)
67b086b chore: release v2.1.0-beta.4
Additional commits viewable in compare view

Updates concurrently from 8.2.2 to 9.0.1

Release notes

Sourced from concurrently's releases.

v9.0.1

What's Changed

Don't set up more than 1 abort signal listener by @gustavohenke in open-cli-tools/concurrently#503

Full Changelog: open-cli-tools/concurrently@v9.0.0...v9.0.1

v9.0.0

💥 Breaking Changes

Dropped support for Node.js < 18.0.0. Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

The concurrently and default exports are now the same - #399 It's reasonable to expect that import { concurrently } from 'concurrently' would work the same as import concurrently from 'concurrently', however this has not been the case. The former used to be an unconfigured version of concurrently, lacking all features that you'd get from the CLI, which was seen as a "footgun". Both are now the same function.

If you'd like to access the unconfigured function, use import { createConcurrently } from 'concurrently' instead.

✨ New Features

Exponential back-off support for process restarting - #265, #462 Use --restart-after exponential. Restarts happen at 2^N seconds.

Add prefix padding via new --pad-prefix flag - #166, #417, #495

Specify teardown commands via new --teardown flag - #472, #500

Expand node:<script> commands to node --run <script> - #475

[API only] Inter-Process Communication (ipc) - #498

[API only] Make it possible to use no colors at all - #466

[API only] Add a state field to Command - #455

🐛 Bug Fixes

Fix importing concurrently in ESM package - #454, #456, #494

Make sure concurrently doesn't resolve when manually restarting commands through API - #463, #464

Abort commands not running when max processes < N - #433, #452, #460

Fix warning coming from spawn-command when running in Node 22 - #407, #477, #479, #492

Make --raw and --hide compatible - #394, #486

Ensure prefix is written when logging without a trailing LF - #467

Other Changes

--help no longer shows examples due to there being too many. Refer to https://github.com/open-cli-tools/concurrently/tree/v9.0.0/docs instead, or to the node_modules/concurrently/docs directory in your project.

Improve examples of --passthrough-arguments - #490

Replace date-fns with hand-rolled date formatting - #436, #443 This should make installing concurrently faster.

New Contributors

@odeadglaz made their first contribution in open-cli-tools/concurrently#464

@mitchhentgesspotify made their first contribution in open-cli-tools/concurrently#474

@mark-monteiro made their first contribution in open-cli-tools/concurrently#480

@PoQuatre made their first contribution in open-cli-tools/concurrently#486

Full Changelog: open-cli-tools/concurrently@v8.2.2...v9.0.0

Commits

79b3290 9.0.1
041520b Don't set up more than 1 abort signal listener (#503)
a7a5894 9.0.0
758ee7f tests: update smoke tests lockfile
710ee55 Replace date-fns for hand-rolled date formatting
fe7b69c deps: update @types/node to 18.x.x too
fd2d140 Bump minimum Node version to 18
37f98b2 deps: update several dev dependencies
1b5df3a deps: update everything eslint
7fc4803 Make it possible to use no colors at all through API
Additional commits viewable in compare view

Updates esbuild from 0.23.0 to 0.24.0

Release notes

Sourced from esbuild's releases.

v0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.
Drop support for older platforms (#3902)

This release drops support for the following operating system:

macOS 10.15 Catalina

This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

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.23). That might look something like this:
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

Work around more issues with Deno 1.31+ (#3917)

This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

This fix was contributed by @Joshix-1.
v0.23.1
Allow using the node: import prefix with es* targets (#3821)

The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
// Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.
Drop support for older platforms (#3902)

This release drops support for the following operating system:

macOS 10.15 Catalina

This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

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.23). That might look something like this:
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

Work around more issues with Deno 1.31+ (#3917)

This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

This fix was contributed by @Joshix-1.
0.23.1
Allow using the node: import prefix with es* targets (#3821)

The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
// Original code
import fs from 'node:fs'
fs.open

... (truncated)

Commits

d34e79e publish 0.24.0 to npm
045a87f fix #3887: omit dead export warning for default
6e049b8 fix #3913: useDefineForClassFields and decorators
9c26f98 lower decorators for useDefineForClassFields #3913
46fdb68 fix #3898: incorrect cyclic tsconfig.json warning
b500443 fix #3917: running esbuild cli with deno
b125e62 run make update-compat-table
112b9aa fix #3915: stack overflow with yarn + tsconfig
ed5a555 wasm: catch and rethrow stack overflows (#3915)
11d3196 fix #3902: update go 1.22.5 => 1.23.1
Additional commits viewable in compare view

Updates vitest from 2.0.5 to 2.1.1

Release notes

Sourced from vitest's releases.

v2.1.1

🐞 Bug Fixes

browser:

Make example test callbacks async - by @aqandrew in vitest-dev/vitest#6484 (16aa7)

Optimize vitest-browser-vue correctly - by @sheremet-va in vitest-dev/vitest#6490 (5cbb0)

workspace:

Resolve glob pattern once to avoid name collision - by @sheremet-va in vitest-dev/vitest#6489 (36b5a)

View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:
test('renders blog posts', async () => {
  const screen = page.render(<Blog />)
await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()
const [firstPost] = screen.getByRole('listitem').all()
await firstPost.getByRole('button', { name: 'Delete' }).click()
expect(screen.getByRole('listitem').all()).toHaveLength(3)
})
You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

workspace:

Correctly resolve workspace globs and file paths - by @sheremet-va in vitest-dev/vitest#6316 (afdcb)

This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)

For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.

This change doesn't affect non-glob usage.

🚀 Features

api:

Make spec into a class instead of a tuple - by @sheremet-va in vitest-dev/vitest#6355 (874a1)

browser:

Move page.config to server.config, add more docs - by @sheremet-va in vitest-dev/vitest#6252 (af2b8)

Make iframe scalable, improve documentation - by @sheremet-va in vitest-dev/vitest#6257 (74ca1)

Introduce built-in locators - by @sheremet-va in vitest-dev/vitest#6084 (3347f)

Support v8 coverage - by @AriPerkkio in vitest-dev/vitest#6273 (34199)

Support userEvent.upload in playwright provider - by @sheremet-va in vitest-dev/vitest#6442 (cf148)

Support --inspect - by @AriPerkkio in vitest-dev/vitest#6433 (0499a)

Support --inspect-brk - by @AriPerkkio in vitest-dev/vitest#6434 (7ab0f)

... (truncated)

Commits

699055e chore: release v2.1.1
36b5ace fix(workspace): resolve glob pattern once to avoid name collision (#6489)
16aa76c fix(browser): make example test callbacks async (#6484)
9f1fd18 chore: release v2.1.0
94a186e fix(ui): render project name consistently (#6329)
ac698b1 fix: expect.getState().testPath always returns correct path (#6472)
b2be23e chore: release v2.1.0-beta.7
0b44722 fix: ignore importer when resolving Vitest (#6469)
97773e2 chore: fix edge case in license files bundling (#6460)
7ab0f4a feat(browser): support --inspect-brk (#6434)
Additional commits viewable 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

… updates Bumps the development group with 3 updates in the / directory: [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul), [concurrently](https://github.com/open-cli-tools/concurrently) and [esbuild](https://github.com/evanw/esbuild). Updates `@vitest/coverage-istanbul` from 2.0.5 to 2.1.1 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.1/packages/coverage-istanbul) Updates `concurrently` from 8.2.2 to 9.0.1 - [Release notes](https://github.com/open-cli-tools/concurrently/releases) - [Commits](open-cli-tools/concurrently@v8.2.2...v9.0.1) Updates `esbuild` from 0.23.0 to 0.24.0 - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md) - [Commits](evanw/esbuild@v0.23.0...v0.24.0) Updates `vitest` from 2.0.5 to 2.1.1 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.1/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-istanbul" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development - dependency-name: concurrently dependency-type: direct:development update-type: version-update:semver-major dependency-group: development - dependency-name: esbuild dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2024-11-01T14:51:29Z

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 Oct 1, 2024

dependabot bot closed this Nov 1, 2024

dependabot bot deleted the dependabot/npm_and_yarn/development-349872957f branch November 1, 2024 14:51

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps-dev): bump the development group across 1 directory with 4 updates #215

chore(deps-dev): bump the development group across 1 directory with 4 updates #215

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

edited

Loading

dependabot bot commented on behalf of github Nov 1, 2024

chore(deps-dev): bump the development group across 1 directory with 4 updates #215

chore(deps-dev): bump the development group across 1 directory with 4 updates #215

Conversation

dependabot bot commented on behalf of github Oct 1, 2024 • edited Loading

v2.1.1

🐞 Bug Fixes

View changes on GitHub

v2.1.0

Potential Breaking Change

🚀 Features

v9.0.1

What's Changed

v9.0.0

💥 Breaking Changes

✨ New Features

🐛 Bug Fixes

Other Changes

New Contributors

v0.24.0

v0.23.1

0.24.0

0.23.1

v2.1.1

🐞 Bug Fixes

View changes on GitHub

v2.1.0

Potential Breaking Change

🚀 Features

dependabot bot commented on behalf of github Nov 1, 2024

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

edited

Loading