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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update deps-dev #187

Merged
merged 1 commit into from
Oct 1, 2024
Merged

chore(deps): update deps-dev #187

merged 1 commit into from
Oct 1, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 30, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^20.16.3 -> ^20.16.10 age adoption passing confidence
@vitest/coverage-v8 (source) ^2.0.5 -> ^2.1.1 age adoption passing confidence
esbuild ^0.23.1 -> ^0.24.0 age adoption passing confidence
eslint (source) ^8.57.0 -> ^8.57.1 age adoption passing confidence
eslint-plugin-import ^2.29.1 -> ^2.30.0 age adoption passing confidence
eslint-plugin-n ^17.10.2 -> ^17.10.3 age adoption passing confidence
eslint-plugin-unused-imports ^4.1.3 -> ^4.1.4 age adoption passing confidence
husky ^9.1.5 -> ^9.1.6 age adoption passing confidence
lint-staged ^15.2.9 -> ^15.2.10 age adoption passing confidence
vitest (source) ^2.0.5 -> ^2.1.1 age adoption passing confidence

Release Notes

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

v2.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.0

Compare Source

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.

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
evanw/esbuild (esbuild)

v0.24.0

Compare Source

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.

eslint/eslint (eslint)

v8.57.1

Compare Source

import-js/eslint-plugin-import (eslint-plugin-import)

v2.30.0

Compare Source

Added
Fixed
Changed
  • [Docs] no-extraneous-dependencies: Make glob pattern description more explicit ([#​2944], thanks [@​mulztob])
  • [no-unused-modules]: add console message to help debug [#​2866]
  • [Refactor] ExportMap: make procedures static instead of monkeypatching exportmap ([#​2982], thanks [@​soryy708])
  • [Refactor] ExportMap: separate ExportMap instance from its builder logic ([#​2985], thanks [@​soryy708])
  • [Docs] order: Add a quick note on how unbound imports and --fix ([#​2640], thanks [@​minervabot])
  • [Tests] appveyor -> GHA (run tests on Windows in both pwsh and WSL + Ubuntu) ([#​2987], thanks [@​joeyguerra])
  • [actions] migrate OSX tests to GHA ([ljharb#37], thanks [@​aks-])
  • [Refactor] exportMapBuilder: avoid hoisting ([#​2989], thanks [@​soryy708])
  • [Refactor] ExportMap: extract "builder" logic to separate files ([#​2991], thanks [@​soryy708])
  • [Docs] [order]: update the description of the pathGroupsExcludedImportTypes option ([#​3036], thanks [@​liby])
  • [readme] Clarify how to install the plugin ([#​2993], thanks [@​jwbth])
eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.10.3

Compare Source

🩹 Fixes
  • Use our data set to work out if a module is a node module (#​338) (6a1b2c5)
📚 Documentation
sweepline/eslint-plugin-unused-imports (eslint-plugin-unused-imports)

v4.1.4

Compare Source

typicode/husky (husky)

v9.1.6

Compare Source

Configuration

📅 Schedule: Branch creation - "on the 1st day of the month" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 added the dependencies Pull requests that update a dependency file label Sep 30, 2024
@trim21 trim21 merged commit bc1ac3f into master Oct 1, 2024
2 checks passed
@trim21 trim21 deleted the renovate/deps-dev branch October 1, 2024 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@trim21 trim21

Labels
dependencies Pull requests that update a dependency file size/XL
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@trim21