chore(deps): update dev dependencies #54

renovate · 2024-08-05T01:15:12Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@playwright/test (source)	`1.45.3` -> `1.46.0`
@prisma/nextjs-monorepo-workaround-plugin (source)	`5.17.0` -> `5.18.0`
@types/node (source)	`20.14.13` -> `20.14.15`
@typescript-eslint/eslint-plugin (source)	`7.17.0` -> `7.18.0`
@typescript-eslint/parser (source)	`7.17.0` -> `7.18.0`
@vitest/coverage-v8 (source)	`2.0.4` -> `2.0.5`
autoprefixer	`10.4.19` -> `10.4.20`
husky	`9.1.3` -> `9.1.4`
lint-staged	`15.2.7` -> `15.2.8`
postcss (source)	`8.4.40` -> `8.4.41`
prisma (source)	`5.17.0` -> `5.18.0`
tailwindcss (source)	`3.4.7` -> `3.4.9`
turbo (source)	`2.0.9` -> `2.0.12`
vitest (source)	`2.0.4` -> `2.0.5`

Release Notes

microsoft/playwright (@playwright/test)

`v1.46.0`

Compare Source

prisma/prisma (@prisma/nextjs-monorepo-workaround-plugin)

`v5.18.0`

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

Native support for UUIDv7

Previous to this release, the Prisma Schema function uuid() did not accept any arguments and created a UUIDv4 ID. While sufficient in many cases, UUIDv4 has a few drawbacks, namely that it is not temporally sortable.

UUIDv7 attempts to resolve this issue, making it easy to temporally sort your database rows by ID!

To support this, we’ve updated the uuid() function in Prisma Schema to accept an optional, integer argument. Right now, the only valid values are 4 and 7, with 4 being the default.

model User {
  id   String @&#8203;id @&#8203;default(uuid()) // defaults to 4
  name String
}

model User {
  id   String @&#8203;id @&#8203;default(uuid(4)) // same as above, but explicit
  name String
}

model User {
  id   String @&#8203;id @&#8203;default(uuid(7)) // will use UUIDv7 instead of UUIDv4
  name String
}

Bug squashing

We’ve squashed a number of bugs this release, special thanks to everyone who helped us! A few select highlights are:

Fixes and improvements

typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)

`v7.18.0`

Compare Source

🩹 Fixes

eslint-plugin: [no-unnecessary-type-assertion] prevent runtime error when asserting a variable declared in default TS lib
eslint-plugin: [unbound-method] report on destructuring in function parameters
eslint-plugin: [no-duplicate-type-constituents] shouldn't report on error types
eslint-plugin: [strict-boolean-expressions] support branded booleans

❤️ Thank You

auvred
Oliver Salzburg
Vinccool96
Yukihiro Hasegawa

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@typescript-eslint/parser)

`v7.18.0`

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

vitest-dev/vitest (@vitest/coverage-v8)

`v2.0.5`

Compare Source

🚀 Features

Introduce experimental reported tasks - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6149 (13d85)
- This is part of the experimental API and doesn't follow semver. We are hoping to stabilize it for 2.1. If you are working with custom reporters, give this a go!

🐞 Bug Fixes

Show a difference between string characters if both values are strings - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6191 (29176)
testNamePattern adds leading space - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6186 (073a5)
browser:
- Don't bundle afterEach cleanup hooks in node entrypoint - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6192 (e6fbc)
- UserEvent.setup initiates a separate state for userEvent instance - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6088 (883f3)
- Correctly import optimized module in vi.importActual - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6219 (804ff)
- Passing options to hover/unhover - by @MNeverOff in https://github.com/vitest-dev/vitest/issues/6175 (d4c00)
- Improve unique CSS selector generation - by @zacharyvoase and Zack Voase in https://github.com/vitest-dev/vitest/issues/6243 (e7acd)
vitest:
- Remove nuxt from auto inline deps - by @sheremet-va (93882)
- Improve defineProject and defineWorkspace types - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6198 (8cd82)
- Correctly resolve mocked node:* imports in __mocks__ folder - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6204 (a48be)
web-worker:
- Expose globals on self - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6170 (12bb5)

View changes on GitHub

postcss/autoprefixer (autoprefixer)

`v10.4.20`

Compare Source

Fixed fit-content prefix for Firefox.

typicode/husky (husky)

`v9.1.4`

Compare Source

lint-staged/lint-staged (lint-staged)

`v15.2.8`

Compare Source

Patch Changes

f0480f0 Thanks @iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

postcss/postcss (postcss)