search

zimicjs / zimic

TypeScript-first HTTP request mocking
https://npmjs.com/package/zimic
MIT License
9 stars 2 forks source link

chore: bump the npm group across 1 directory with 28 updates #408

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps the npm group with 28 updates in the / directory:

Package From To
@commitlint/cli 19.4.1 19.5.0
@commitlint/config-conventional 19.4.1 19.5.0
concurrently 8.2.2 9.0.1
husky 9.1.5 9.1.6
turbo 2.1.1 2.1.2
@vitest/browser 2.0.5 2.1.1
@vitest/coverage-istanbul 2.0.5 2.1.1
execa 9.3.1 9.4.0
playwright 1.47.0 1.47.2
typescript 5.5.4 5.6.2
vitest 2.0.5 2.1.1
@typescript-eslint/eslint-plugin 8.4.0 8.6.0
@typescript-eslint/parser 8.4.0 8.6.0
eslint 8.57.0 8.57.1
eslint-config-turbo 2.1.1 2.1.2
@types/node 22.5.4 22.5.5
tsup 8.2.4 8.3.0
msw 2.4.3 2.4.9
openapi-typescript 7.4.0 7.4.1
tsx 4.19.0 4.19.1
@swc/core 1.7.23 1.7.26
fastify 4.28.1 5.0.0
@tanstack/react-query 5.55.0 5.56.2
next 14.2.8 14.2.13
@playwright/test 1.47.0 1.47.2
@types/react 18.3.5 18.3.8
postcss 8.4.45 8.4.47
tailwindcss 3.4.10 3.4.12

Updates @commitlint/cli from 19.4.1 to 19.5.0

Release notes

Sourced from @​commitlint/cli's releases.

v19.5.0

19.5.0 (2024-09-11)

Features

Chore

New Contributors

Full Changelog: https://github.com/conventional-changelog/commitlint/compare/v19.4.1...v19.5.0

Changelog

Sourced from @​commitlint/cli's changelog.

19.5.0 (2024-09-11)

Features

Commits


Updates @commitlint/config-conventional from 19.4.1 to 19.5.0

Release notes

Sourced from @​commitlint/config-conventional's releases.

v19.5.0

19.5.0 (2024-09-11)

Features

Chore

New Contributors

Full Changelog: https://github.com/conventional-changelog/commitlint/compare/v19.4.1...v19.5.0

Changelog

Sourced from @​commitlint/config-conventional's changelog.

19.5.0 (2024-09-11)

Note: Version bump only for package @​commitlint/config-conventional

Commits


Updates concurrently from 8.2.2 to 9.0.1

Release notes

Sourced from concurrently's releases.

v9.0.1

What's Changed

Full Changelog: https://github.com/open-cli-tools/concurrently/compare/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

Full Changelog: https://github.com/open-cli-tools/concurrently/compare/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 husky from 9.1.5 to 9.1.6

Release notes

Sourced from husky's releases.

v9.1.6

What's Changed

New Contributors

Full Changelog: https://github.com/typicode/husky/compare/v9.1.5...v9.1.6

Commits


Updates turbo from 2.1.1 to 2.1.2

Release notes

Sourced from turbo's releases.

Turborepo v2.1.2

What's Changed

Docs

@​turbo/telemetry

Examples

Changelog

New Contributors

Full Changelog: https://github.com/vercel/turborepo/compare/v2.1.1...v2.1.2

Turborepo v2.1.2-canary.1

What's Changed

Docs

Changelog

... (truncated)

Commits
  • c41ca0a publish 2.1.2 to registry
  • 76e8a6d fix(affected): include dependents in affected filter (#9137)
  • 33bef9e chore(@​turbo/telemetry): remove unused jest deps (#9135)
  • bb8f81e chore(config): move all uses of clap(env) to config (#9113)
  • b7a00d3 feat(turborepo): web ui (#8895)
  • bd2bffa chore(config): leverage proc macros (#9111)
  • 2adeac9 release(turborepo): 2.1.2-canary.1 (#9131)
  • 8cffabe docs(crates/turborepo): add capnp to build dependencies (#9127)
  • c84638a perf(tui): only rerender if a non-tick event has been received (#9121)
  • 785682b chore: remove turbopack top level crates (#9119)
  • Additional commits viewable in compare view


Updates @vitest/browser from 2.0.5 to 2.1.1

Release notes

Sourced from @​vitest/browser's releases.

v2.1.1

   🐞 Bug Fixes

    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

... (truncated)

Commits
  • 699055e chore: release v2.1.1
  • 5cbb0bb fix(browser): optimize vitest-browser-vue correctly (#6490)
  • 9f1fd18 chore: release v2.1.0
  • 0b4da69 fix: userEvent works consistently between providers (#6480)
  • 9560ab7 fix(browser): define mocker as a dependency (#6476)
  • b2be23e chore: release v2.1.0-beta.7
  • 7ab0f4a feat(browser): support --inspect-brk (#6434)
  • 8d883cf fix(browser): exclude missed packages from optimization, print help message (...
  • c321a3f chore: replace fast-glob with tinyglobby (#6274)
  • b992b34 fix: print unexpected error message if peer dependencies have a different ver...
  • Additional commits viewable in compare view


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

    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

... (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 execa from 9.3.1 to 9.4.0

Release notes

Sourced from execa's releases.

v9.4.0

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

Documentation

Commits


Updates playwright from 1.47.0 to 1.47.2

Release notes

Sourced from playwright's releases.

v1.47.2

Highlights

microsoft/playwright#32699 [REGRESSION]: fix(codegen): use content_frame property in python/.NET microsoft/playwright#32706 [REGRESSION]: page.pause() does not pause test timeout after 1.47 microsoft/playwright#32661 - fix(trace-viewer): time delta between local and remote actions

Browser Versions

  • Chromium 129.0.6668.29
  • Mozilla Firefox 130.0
  • WebKit 18.0

This version was also tested against the following stable channels:

  • Google Chrome 128
  • Microsoft Edge 128

v1.47.1

Highlights

microsoft/playwright#32480 - [REGRESSION]: tsconfig.json's compilerOptions.paths no longer working in 1.47 microsoft/playwright#32552 - [REGRESSION]: broken UI in Trace Viewer while showing network response body

Browser Versions

  • Chromium 129.0.6668.29
  • Mozilla Firefox 130.0
  • WebKit 18.0

This version was also tested against the following stable channels:

  • Google Chrome 128
  • Microsoft Edge 128
Commits
  • d93029f chore: mark v1.47.2 (#32729)
  • 0c6217a cherry-pick(#32699): fix(codegen): use content_frame property in python
  • f96b487 cherry-pick(#32714): fix(test runner): page.pause() should enable debug mode ...
  • 937424f cherry-pick(#32661): fix(trace-viewer): time delta between local and … (#32663)
  • 3d2ffd0 chore: mark v1.47.1 (#32617)
  • dba1319 cherry-pick(#32589): docs: release note fixes for 1.47
  • 90f959a cherry-pick(#32553): fix(trace-viewer): fix ui issue on network request details
  • 13e6e48 cherry-pick(#32491): fix(test runner): allow directory imports with path mapp...
  • 8762407 cherry-pick(#32492): Revert "fix(test runner): align with typescript … (#32560)
  • f9145b1 cherry-pick(#32516): chore: allow query as string in Python/.NET
  • Additional commits viewable in compare view


Updates typescript from 5.5.4 to 5.6.2

Release notes

Sourced from typescript's releases.

TypeScript 5.6

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.6 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.6 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Commits
  • a7e3374 Bump version to 5.6.2 and LKG
  • 2063357 🤖 Pick PR #59708 (LEGO: Pull request from lego/hb_537...) into release-5.6 (#...
  • 4fe7e41 🤖 Pick PR #59670 (fix(59649): ts Move to a new file d...) into release-5.6 (#...
  • 1a03e53 🤖 Pick PR #59761 (this can be nullish) into release-5.6 (#59762)
  • 6212132 Update LKG
  • bbb5faf 🤖 Pick PR #59542 (Fixing delay caused in vscode due t...) into release-5.6 (#...
  • e6914a5 Bump version to 5.6.1-rc and LKG
  • 34121c4 Update LKG
  • 2a30c2a Merge remote-tracking branch 'origin/main' into release-5.6
  • 936a79b Expose TypeChecker. getAwaitedType to public (#59268)
  • 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

    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

dependabot[bot] commented 1 month ago

Superseded by #409.