search

dvdkouril / chromospace

🧬🚀 visualizing chromatin in space
https://chromospace.org/
MIT License
1 stars 0 forks source link

build(deps-dev): bump the dev-dependencies group across 1 directory with 5 updates #36

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 4 months ago

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

Package From To
@biomejs/biome 1.8.2 1.8.3
@types/node 20.14.8 20.14.10
typescript 5.5.2 5.5.3
vite 5.3.1 5.3.3
vitest 1.6.0 2.0.3

Updates @biomejs/biome from 1.8.2 to 1.8.3

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.3

CLI

Bug fixes

  • Fix #3104 by suppressing node warnings when using biome migrate. Contributed by @​SuperchupuDev

  • Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @​Sec-ant

Parser

Bug fixes

Formatter

Bug fixes

Linter

New features

Bug fixes

  • useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @​Conaclos
  • Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @​ematipico
  • The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @​Sec-ant

Enhancements

  • Enhance tailwind sorting lint rule #1274 with variant support.

    Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order. Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class. Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight). Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant. Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last. Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

    Contributed by @​lutaok

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.8.3 (2024-06-27)

CLI

Bug fixes

  • Fix #3104 by suppressing node warnings when using biome migrate. Contributed by @​SuperchupuDev

  • Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @​Sec-ant

Parser

Bug fixes

Formatter

Bug fixes

Linter

New features

Enhancements

Bug fixes

  • useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @​Conaclos
  • Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @​ematipico
  • The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @​Sec-ant

Enhancements

  • Enhance tailwind sorting lint rule #1274 with variant support.

    Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order. Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class. Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight). Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant. Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last. Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

... (truncated)

Commits


Updates @types/node from 20.14.8 to 20.14.10

Commits


Updates typescript from 5.5.2 to 5.5.3

Release notes

Sourced from typescript's releases.

TypeScript 5.5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Commits


Updates vite from 5.3.1 to 5.3.3

Changelog

Sourced from vite's changelog.

5.3.3 (2024-07-03)

5.3.2 (2024-06-27)

Commits
  • 22b2994 release: v5.3.3
  • 012490c fix(deps): update all non-major dependencies (#17590)
  • 14c3d49 fix(proxy): replace changeOrigin changes in 5.3.0 with new rewriteWsOrigin op...
  • 055f1c1 fix(lib): remove pure CSS dynamic import (#17601)
  • dafff4a fix: lazily evaluate __vite__mapDeps files (#17602)
  • 3af02bd release: v5.3.2
  • 24c799b fix(typescript): correctly expand ${configDir} in tsconfig.json (#17576)
  • a33a97f chore(deps): update all non-major dependencies (#17553)
  • 2d6672f chore(deps): update es-module-lexer to 1.5.4 (#17555)
  • 7c06ef0 refactor(optimizer): use early continues (#17551)
  • Additional commits viewable in compare view


Updates vitest from 1.6.0 to 2.0.3

Release notes

Sourced from vitest's releases.

v2.0.3

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v2.0.2

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v2.0.1

   🐞 Bug Fixes

    View changes on GitHub

v2.0.0

... (truncated)

Commits
  • 81b8d67 chore: release v2.0.3
  • 09dc75c chore(deps): update dependency @​edge-runtime/vm to v4 (#6047)
  • f851982 fix: --inspect-brk stop on Windows (#6110)
  • 99a12ae chore: release v2.0.2
  • 80a43d5 fix(browser): inline pretty-format and replace picocolors with tinyrainbow (#...
  • 7012f8c docs: add env documentation (#6063)
  • 16eb6c8 chore: release v2.0.1
  • 4b03e72 fix(browser): correctly inherit browser config in a workspace (#6054)
  • 4d5597d fix(vitest): print only running files, not every file (#6052)
  • 1b150a3 chore: release v2.0.0
  • 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
dependabot[bot] commented 3 months ago

Looks like these dependencies are updatable in another way, so this is no longer needed.