search

manzt / anywidget

jupyter widgets made easy
https://anywidget.dev
MIT License
451 stars 35 forks source link

chore(deps-dev): bump the dev-dependencies group with 7 updates #605

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

Bumps the dev-dependencies group with 7 updates:

Package From To
@biomejs/biome 1.7.3 1.8.1
@rspack/cli 0.7.0 0.7.1
esbuild 0.21.4 0.21.5
@rspack/core 0.7.0 0.7.1
@types/node 20.14.0 20.14.2
svelte 4.2.17 4.2.18
vite 5.2.12 5.2.13

Updates @biomejs/biome from 1.7.3 to 1.8.1

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.1

CLI

Bug fixes

  • Fix #3069, prevent overwriting paths when using --staged or --changed options. Contributed by @​unvalley
  • Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by @​uncenter

Configuration

Bug fixes

  • Fix #3067, by assigning the correct default value to indentWidth. Contributed by @​ematipico

Formatter

Bug fixes

  • Fix the bug where whitespace after the & character in CSS nesting was incorrectly trimmed, ensuring proper targeting of child classes #3061. Contributed by @​denbezrukov
  • Fix #3068 where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by @​denbezrukov
  • Fix the formatting of CSS grid layout properties. Contributed by @​denbezrukov

Linter

Bug fixes

  • The noEmptyBlock css lint rule now treats empty blocks containing comments as valid ones. Contributed by @​Sec-ant

  • useLiteralKeys no longer reports quoted member names (#3085).

    Previously useLiteralKeys reported quoted member names that can be unquoted. For example, the rule suggested the following fix:

    - const x = { "prop": 0 };
+ const x = { prop: 0 };

    This conflicted with the option quoteProperties of our formatter.

    The rule now ignores quoted member names.

    Contributed by @​Conaclos

  • noEmptyInterface now ignores empty interfaces in ambient modules (#3110). Contributed by @​Conaclos

  • noUnusedVariables and noUnusedFunctionParameters no longer report the parameters of a constructor type (#3135).

    Previously, arg was reported as unused in a constructor type like:

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.8.1 (2024-06-10)

Analyzer

CLI

Bug fixes

  • Fix #3069, prevent overwriting paths when using --staged or --changed options. Contributed by @​unvalley
  • Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by @​uncenter

Configuration

Bug fixes

  • Fix #3067, by assigning the correct default value to indentWidth. Contributed by @​ematipico

Editors

Formatter

Bug fixes

  • Fix the bug where whitespace after the & character in CSS nesting was incorrectly trimmed, ensuring proper targeting of child classes #3061. Contributed by @​denbezrukov
  • Fix #3068 where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by @​denbezrukov
  • Fix the formatting of CSS grid layout properties. Contributed by @​denbezrukov

JavaScript APIs

Linter

Bug fixes

  • The noEmptyBlock css lint rule now treats empty blocks containing comments as valid ones. Contributed by @​Sec-ant

  • useLiteralKeys no longer reports quoted member names (#3085).

    Previously useLiteralKeys reported quoted member names that can be unquoted. For example, the rule suggested the following fix:

    - const x = { "prop": 0 };
+ const x = { prop: 0 };

    This conflicted with the option quoteProperties of our formatter.

    The rule now ignores quoted member names.

    Contributed by @​Conaclos

... (truncated)

Commits


Updates @rspack/cli from 0.7.0 to 0.7.1

Release notes

Sourced from @​rspack/cli's releases.

v0.7.1

What's Changed

Highlights

Check exports presence

Now Rspack will emit warnings for using non-existent exports and conflicting re-exports, checkout docs for more details.

10%-15% performance improvement for JavaScript parsing

The old JavaScript parser performs multiple times of parsing and code generation. In this version, Rspack refactored the current implementation. It's one time parsing now. Check out the PR for detail.

image

Performance Improvements ⚡

Exciting New Features 🎉

Bug Fixes 🐞

Document Updates 📖

... (truncated)

Commits


Updates esbuild from 0.21.4 to 0.21.5

Release notes

Sourced from esbuild's releases.

v0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }

  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
  2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }

  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
  2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Commits


Updates @rspack/core from 0.7.0 to 0.7.1

Release notes

Sourced from @​rspack/core's releases.

v0.7.1

What's Changed

Highlights

Check exports presence

Now Rspack will emit warnings for using non-existent exports and conflicting re-exports, checkout docs for more details.

10%-15% performance improvement for JavaScript parsing

The old JavaScript parser performs multiple times of parsing and code generation. In this version, Rspack refactored the current implementation. It's one time parsing now. Check out the PR for detail.

image

Performance Improvements ⚡

Exciting New Features 🎉

Bug Fixes 🐞

Document Updates 📖

... (truncated)

Commits


Updates @types/node from 20.14.0 to 20.14.2

Commits


Updates svelte from 4.2.17 to 4.2.18

Release notes

Sourced from svelte's releases.

svelte@4.2.18

Patch Changes

  • chore: speed up regex (#11922)
Changelog

Sourced from svelte's changelog.

4.2.18

Patch Changes

  • chore: speed up regex (#11922)
Commits


Updates vite from 5.2.12 to 5.2.13

Changelog

Sourced from vite's changelog.

5.2.13 (2024-06-07)

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
changeset-bot[bot] commented 3 months ago

⚠️ No Changeset found

Latest commit: 16e62b38b98fa3476d942c39b0fd8a73bd8309ee

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR