search

HowTheyVote / howtheyvote

HowTheyVote.eu allows anyone to easily find out how Members of the European Parliament vote in plenary.
https://howtheyvote.eu
GNU Affero General Public License v3.0
44 stars 2 forks source link

Bump the dev-dependencies group across 1 directory with 6 updates #1047

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 3 weeks ago

Bumps the dev-dependencies group with 6 updates in the /frontend directory:

Package From To
@biomejs/biome 1.8.3 1.9.4
@types/node 22.5.2 22.8.6
esbuild 0.23.1 0.24.0
jsdom 25.0.0 25.0.1
tsx 4.19.0 4.19.2
typescript 5.5.4 5.6.3

Updates @biomejs/biome from 1.8.3 to 1.9.4

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.9.4

Analyzer

Bug fixes

  • Improved the message for unused suppression comments. Contributed by @​dyc3

  • Fix #4228, where the rule a11y/noInteractiveElementToNoninteractiveRole incorrectly reports a role for non-interactive elements. Contributed by @​eryue0220

  • noSuspiciousSemicolonInJsx now catches suspicious semicolons in React fragments. Contributed by @​vasucp1207

CLI

Enhancements

  • The --summary reporter now reports parsing diagnostics too. Contributed by @​ematipico

  • Improved performance of GritQL queries by roughly 25-30%. Contributed by @​arendjr

Configuration

Bug fixes

  • Fix an issue where the JSON schema marked lint rules options as mandatory. Contributed by @​ematipico

Formatter

Bug fixes

  • Fix #4121. Respect line width when printing multiline strings. Contributed by @​ah-yu

Linter

New features

Bug Fixes

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.9.4 (2024-10-17)

Analyzer

Bug fixes

  • Implement GraphQL suppression action. Contributed by @​vohoanglong0107

  • Improved the message for unused suppression comments. Contributed by @​dyc3

  • Fix #4228, where the rule a11y/noInteractiveElementToNoninteractiveRole incorrectly reports a role for non-interactive elements. Contributed by @​eryue0220

  • noSuspiciousSemicolonInJsx now catches suspicious semicolons in React fragments. Contributed by @​vasucp1207

  • The syntax rule noTypeOnlyImportAttributes now ignores .cts files (#4361).

    Since TypeScript 5.3, type-only imports can be associated to an import attribute in CommonJS-enabled files. See the TypeScript docs.

    The following code is no longer reported as a syntax error:

    import type { TypeFromRequire } from "pkg" with {
    "resolution-mode": "require"
};

    Note that this is only allowed in files ending with the cts extension.

    Contributed by @​Conaclos

CLI

Enhancements

  • The --summary reporter now reports parsing diagnostics too. Contributed by @​ematipico

  • Improved performance of GritQL queries by roughly 25-30%. Contributed by @​arendjr

Configuration

Bug fixes

  • Fix an issue where the JSON schema marked lint rules options as mandatory. Contributed by @​ematipico

Editors

Formatter

Bug fixes

... (truncated)

Commits


Updates @types/node from 22.5.2 to 22.8.6

Commits


Updates esbuild from 0.23.1 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.

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.

Commits


Updates jsdom from 25.0.0 to 25.0.1

Release notes

Sourced from jsdom's releases.

Version 25.0.1

  • Updated dependencies, notably tough-cookie, which no longer prints a deprecation warning.
Changelog

Sourced from jsdom's changelog.

25.0.1

  • Updated dependencies, notably tough-cookie, which no longer prints a deprecation warning.
Commits


Updates tsx from 4.19.0 to 4.19.2

Release notes

Sourced from tsx's releases.

v4.19.2

4.19.2 (2024-10-26)

Bug Fixes

  • generate sourcesContent when Node.js debugger is enabled (#670) (7c47074)

This release is also available on:

v4.19.1

4.19.1 (2024-09-12)

Bug Fixes

This release is also available on:

Commits
  • 7c47074 fix: generate sourcesContent when Node.js debugger is enabled (#670)
  • 315d5f4 docs(watch): document --include flag
  • 375e39a test: refactor enforce-timeout
  • 524cb77 docs(cjs): add compilation caveats
  • 7f8a051 chore(deps): update dependency node to v20.18.0 (#660)
  • 97e8de0 chore: upgrade pnpm
  • 95d2b0f chore: remove commit hooks
  • 0161078 docs: add prisma as a premium sponsor
  • 09f9532 chore(docs): fix typo (#655)
  • 0329bfc fix(cjs): patch module.path for accurate cache ID
  • Additional commits viewable in compare view


Updates typescript from 5.5.4 to 5.6.3

Release notes

Sourced from typescript's releases.

TypeScript 5.6.3

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

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

... (truncated)

Commits
  • d48a5cf Bump version to 5.6.3 and LKG
  • fefa70a 🤖 Pick PR #60083 (Don't issue implicit any when obtai...) into release-5.6 (#...
  • ff71692 [release-5.6] Remove tsbuildInfo specification error now that we need it for ...
  • 1f44dcf 🤖 Pick PR #60157 (fix automatic type acquisition) into release-5.6 (#60169)
  • 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 (#...
  • 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
tillprochaska commented 3 weeks ago

For future reference: Updates to the default Biome formatter configuration make the tests fail

Edit: Actually I think this is because Biome can now format CSS files (which it previously didn’t)