Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dev dependencies #161

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 13, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@faker-js/faker (source) 9.3.0 -> 9.4.0 age adoption passing confidence
@headlessui/tailwindcss (source) 0.2.1 -> 0.2.2 age adoption passing confidence
@next/env (source) 15.1.3 -> 15.1.6 age adoption passing confidence
@playwright/test (source) 1.49.1 -> 1.50.1 age adoption passing confidence
@types/node (source) 22.10.5 -> 22.13.1 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) 8.19.0 -> 8.23.0 age adoption passing confidence
@typescript-eslint/parser (source) 8.19.0 -> 8.23.0 age adoption passing confidence
@vitest/coverage-v8 (source) 2.1.8 -> 2.1.9 age adoption passing confidence
eslint-config-next (source) 15.1.3 -> 15.1.6 age adoption passing confidence
eslint-plugin-tailwindcss 3.17.5 -> 3.18.0 age adoption passing confidence
lint-staged 15.3.0 -> 15.4.3 age adoption passing confidence
postcss (source) 8.4.49 -> 8.5.1 age adoption passing confidence
turbo (source) 2.3.3 -> 2.4.0 age adoption passing confidence
typescript (source) 5.7.2 -> 5.7.3 age adoption passing confidence

Release Notes

faker-js/faker (@​faker-js/faker)

v9.4.0

Compare Source

Features
Changed Locales
Bug Fixes
tailwindlabs/headlessui (@​headlessui/tailwindcss)

v0.2.2

Compare Source

  • Support installing with Tailwind CSS v4 (#​3634)
vercel/next.js (@​next/env)

v15.1.6

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • fix: don't memory-leak promises passed to waitUntil (#​75041)
  • backport: fix prerender issue with intercepting routes + generateStaticParams (#​75170)
Credits

Huge thanks to @​lubieowoce and @​ztanner for helping!

v15.1.5

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • Fix missing revalidate with notFound() (#​75009)
  • fix: when metadatabase is set we should not warn (#​74840)
  • Fix @​vercel/og license SPDX expression (#​74745)
  • fix: ts language server rule metadata should allow null (#​74704)
  • fix: eslint rule of using img in metadata routes (#​74864)
  • Fix presentation when onerror receives an event without error (#​74643)
  • fix fetch lock not being consistently released #​74623 (#​75028)
Credits

Huge thanks to @​ijjk, @​huozhi, @​matmannion and @​ztanner for helping!

v15.1.4

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • backport: force module format for virtual client-proxy (#​74608)
  • Fix prerender tags when notFound is called (#​74607)
  • Use provided waitUntil for pending revalidates (#​74604)
  • Feature: next/image: add support for images.qualities in next.config (#​74588)
  • Chore: docs: add missing search: '' on remotePatterns (#​74587)
  • Chore: docs: update version history of next/image (#​73923) (#​74570)
  • Chore: next/image: improve imgopt api bypass detection for unsupported images (#​74569)
Credits

Huge thanks to @​ and @​ for helping!

microsoft/playwright (@​playwright/test)

v1.50.1

Compare Source

v1.50.0

Compare Source

Test runner

  • New option timeout allows specifying a maximum run time for an individual test step. A timed-out step will fail the execution of the test.

    test('some test', async ({ page }) => {
      await test.step('a step', async () => {
        // This step can time out separately from the test
      }, { timeout: 1000 });
    });
  • New method test.step.skip() to disable execution of a test step.

    test('some test', async ({ page }) => {
      await test.step('before running step', async () => {
        // Normal step
      });
    
      await test.step.skip('not yet ready', async () => {
        // This step is skipped
      });
    
      await test.step('after running step', async () => {
        // This step still runs even though the previous one was skipped
      });
    });
  • Expanded expect(locator).toMatchAriaSnapshot() to allow storing of aria snapshots in separate YAML files.

  • Added method expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.

  • Option testConfig.updateSnapshots added the configuration enum changed. changed updates only the snapshots that have changed, whereas all now updates all snapshots, regardless of whether there are any differences.

  • New option testConfig.updateSourceMethod defines the way source code is updated when testConfig.updateSnapshots is configured. Added overwrite and 3-way modes that write the changes into source code, on top of existing patch mode that creates a patch file.

    npx playwright test --update-snapshots=changed --update-source-method=3way
  • Option testConfig.webServer added a gracefulShutdown field for specifying a process kill signal other than the default SIGKILL.

  • Exposed testStep.attachments from the reporter API to allow retrieval of all attachments created by that step.

UI updates

  • Updated default HTML reporter to improve display of attachments.
  • New button for picking elements to produce aria snapshots.
  • Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
  • Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
  • Call and Network panels now display additional time information.

Breaking

Browser Versions

  • Chromium 133.0.6943.16
  • Mozilla Firefox 134.0
  • WebKit 18.2

This version was also tested against the following stable channels:

  • Google Chrome 132
  • Microsoft Edge 132
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.23.0

Compare Source

🚀 Features
  • eslint-plugin: [no-unnecessary-boolean-literal-compare] enforce strictNullChecks (#​10712)
🩹 Fixes
  • eslint-plugin: [no-shadow] ignore declare variables in definition files shadowing global variables (#​10710)
  • eslint-plugin: [no-restricted-imports] support regex option (#​10699)
  • eslint-plugin: [dot-notation] handle noPropertyAccessFromIndexSignature true (#​10644)
  • eslint-plugin: [prefer-nullish-coalescing] fix missing return (#​10732)
  • bump ts-api-utils to ^2.0.1 (#​10761)
  • eslint-plugin: [no-unnecessary-template-expression] allow interpolating type parameter in type context (#​10739)
  • eslint-plugin: [switch-exhaustiveness-check] suggest with qualified name (#​10697)
  • eslint-plugin: [no-unnecessary-type-assertion] should report readonly class properties with a literal initializer (#​10618)
❤️ Thank You

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

v8.22.0

Compare Source

🩹 Fixes
  • eslint-plugin: [no-unnecessary-template-expression] handle template literal type (#​10612)
  • eslint-plugin: [prefer-readonly] autofixer doesn't add type to property that is mutated in the constructor (#​10552)
  • eslint-plugin: [no-extraneous-class] handle accessor keyword (#​10678)
  • eslint-plugin: [no-shadow] don't report unnecessarily on valid ways of using module augmentation (#​10616)
  • eslint-plugin: [no-duplicate-type-constituents] handle nested types (#​10638)
  • eslint-plugin: [prefer-nullish-coalescing] doesn't report on ternary but on equivalent || (#​10517)
❤️ Thank You

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

v8.21.0

Compare Source

🩹 Fixes
  • eslint-plugin: [no-duplicate-enum-values] handle template literal (#​10675)
  • eslint-plugin: [no-base-to-string] don't crash for recursive array or tuple types (#​10633)
  • eslint-plugin: [no-for-in-array] report on any type which may be an array or array-like (#​10535)
  • eslint-plugin: check JSX spread elements for misused spread usage (#​10653)
  • eslint-plugin: [no-unnecessary-type-arguments] handle type args on jsx (#​10630)
❤️ Thank You

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

v8.20.0

Compare Source

🚀 Features
  • eslint-plugin: [consistent-type-assertions] add arrayLiteralTypeAssertions options (#​10565)
  • eslint-plugin: [no-deprecated] add allow options (#​10585)
  • eslint-plugin: [no-misused-spread] add new rule (#​10551)
🩹 Fixes
  • eslint-plugin: [no-unnecessary-condition] don't flag optional chaining for union types with an unconstrained type parameters (#​10602)
  • eslint-plugin: [no-shadow] ignore ordering of type declarations (#​10593)
❤️ Thank You

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

v8.19.1

Compare Source

🩹 Fixes
  • eslint-plugin: [no-unnecessary-type-assertion] handle literal types (#​10523)
  • eslint-plugin: [no-deprecated] doesn't report on shorthand property in an object expression (#​10550)
  • eslint-plugin: [strict-boolean-expressions] remove remaining (unsafe) autofixes (#​10548)
  • eslint-plugin: [no-shadow] report correctly on parameters of functions declared with the declare keyword (#​10543)
  • eslint-plugin: [no-base-to-string] check array generic type (#​10437)
❤️ Thank You
  • Kirk Waiblinger
  • mdm317
  • Ronen Amiel
  • Yukihiro Hasegawa @​y-hsgw

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

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

v8.23.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.

v8.22.0

Compare Source

🚀 Features
  • parser: add standalone isolatedDeclarations option (#​10499)
❤️ Thank You
  • Josh Goldberg ✨

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

v8.21.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.

v8.20.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.

v8.19.1

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.1.9

Compare Source

   🚨 Breaking Changes
   🚀 Features

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/dev-dependencies branch 9 times, most recently from 4436cf2 to 17803a4 Compare January 17, 2025 16:32
@renovate renovate bot force-pushed the renovate/dev-dependencies branch 6 times, most recently from c98d774 to a5055ef Compare January 26, 2025 17:45
@renovate renovate bot force-pushed the renovate/dev-dependencies branch 5 times, most recently from 9655f30 to d4b3009 Compare February 3, 2025 18:08
@renovate renovate bot force-pushed the renovate/dev-dependencies branch 4 times, most recently from be185f6 to 17fb78f Compare February 7, 2025 11:52
@renovate renovate bot force-pushed the renovate/dev-dependencies branch from 17fb78f to 3fa5ca5 Compare February 7, 2025 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants