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 with 7 updates #70

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps the dev-dependencies group with 7 updates:

Package From To
@biomejs/biome 1.8.3 1.9.1
@types/node 22.5.4 22.5.5
typescript 5.5.4 5.6.2
vite 5.4.3 5.4.5
vitest 2.0.5 2.1.1
@sveltejs/kit 2.5.26 2.5.27
svelte-check 4.0.1 4.0.2

Updates @biomejs/biome from 1.8.3 to 1.9.1

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.9.1

Analyzer

CLI

Bug fixes

  • useEditorConfig now loads the editorconfig when running biome ci #3864. Contributed by @​dyc3

  • Revert #3731 to fix broken quick fixes and code actions. Contributed by @​nhedger

Linter

New Features

Bug fixes

What's Changed

Other changes

New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/cli/v1.9.1-nightly.12688b6...cli/v1.9.1

CLI v1.9.1-nightly.12688b6

Analyzer

CLI

Bug fixes

  • useEditorConfig now loads the editorconfig when running biome ci #3864. Contributed by @​dyc3

Configuration

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.9.1 (2024-09-15)

CLI

Bug fixes

  • useEditorConfig now loads the editorconfig when running biome ci #3864. Contributed by @​dyc3

Editors

Bug fixes

  • Revert #3731 to fix broken quick fixes and code actions. Contributed by @​nhedger

Linter

New Features

Bug fixes

v1.9.0 (2024-09-12)

Analyzer

CLI

New features

  • Add --graphql-linter-enabled option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @​ematipico

  • New EXPERIMENTAL search command. The search command allows you to search a Biome project using GritQL syntax.

    GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.

    While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.

    For now, the search command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!

    Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.

    biome search '`console.log($message)`' # find all `console.log` invocations

... (truncated)

Commits


Updates @types/node from 22.5.4 to 22.5.5

Commits


Updates typescript from 5.5.4 to 5.6.2

Release notes

Sourced from typescript's releases.

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

Downloads are available on:

Commits
  • 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 (#...
  • e6914a5 Bump version to 5.6.1-rc and LKG
  • 34121c4 Update LKG
  • 2a30c2a Merge remote-tracking branch 'origin/main' into release-5.6
  • 936a79b Expose TypeChecker. getAwaitedType to public (#59268)
  • Additional commits viewable in compare view


Updates vite from 5.4.3 to 5.4.5

Changelog

Sourced from vite's changelog.

5.4.5 (2024-09-13)

5.4.4 (2024-09-11)

Commits


Updates vitest from 2.0.5 to 2.1.1

Release notes

Sourced from vitest's releases.

v2.1.1

   🐞 Bug Fixes

    View changes on GitHub

v2.1.0

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.

Potential Breaking Change

  • workspace:
    • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in vitest-dev/vitest#6316 (afdcb)
    • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
    • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
    • This change doesn't affect non-glob usage.

   🚀 Features

... (truncated)

Commits
  • 699055e chore: release v2.1.1
  • 36b5ace fix(workspace): resolve glob pattern once to avoid name collision (#6489)
  • 16aa76c fix(browser): make example test callbacks async (#6484)
  • 9f1fd18 chore: release v2.1.0
  • 94a186e fix(ui): render project name consistently (#6329)
  • ac698b1 fix: expect.getState().testPath always returns correct path (#6472)
  • b2be23e chore: release v2.1.0-beta.7
  • 0b44722 fix: ignore importer when resolving Vitest (#6469)
  • 97773e2 chore: fix edge case in license files bundling (#6460)
  • 7ab0f4a feat(browser): support --inspect-brk (#6434)
  • Additional commits viewable in compare view


Updates @sveltejs/kit from 2.5.26 to 2.5.27

Release notes

Sourced from @​sveltejs/kit's releases.

@​sveltejs/kit@​2.5.27

Patch Changes

  • fix: asynchronously instantiate components when using Svelte 5 (#12613)

  • fix: use {@render ...} tag when generating default fallback page for svelte 5 apps (#12653)

  • fix: emulate event.platform even when the route does not exist (#12513)

Changelog

Sourced from @​sveltejs/kit's changelog.

2.5.27

Patch Changes

  • fix: asynchronously instantiate components when using Svelte 5 (#12613)

  • fix: use {@render ...} tag when generating default fallback page for svelte 5 apps (#12653)

  • fix: emulate event.platform even when the route does not exist (#12513)

Commits


Updates svelte-check from 4.0.1 to 4.0.2

Release notes

Sourced from svelte-check's releases.

svelte-check-4.0.2

  • fix: ensure components typed through Svelte 5's Component interface get proper intellisense
Commits


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