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 across 1 directory with 8 updates #620

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 2 months ago

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

Package From To
@biomejs/biome 1.8.2 1.8.3
@changesets/cli 2.27.6 2.27.7
@rspack/cli 0.7.4 0.7.5
esbuild 0.21.5 0.23.0
typescript 5.5.2 5.5.3
@rspack/core 0.7.4 0.7.5
@types/node 20.14.8 20.14.10
vite 5.3.1 5.3.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 @changesets/cli from 2.27.6 to 2.27.7

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​2.27.7

Patch Changes

  • #1047 d108fa6 Thanks @​patzick! - Fixed a crash that could occur when depending on a tagged version of another workspace package.

  • #1400 dd6e5bb Thanks @​Andarist! - Fixed a crash that prevented the CLI from running in a scenario when a workspace depends on the root workspace

  • Updated dependencies [d108fa6, dd6e5bb, dd6e5bb]:

    • @​changesets/apply-release-plan@​7.0.4
    • @​changesets/config@​3.0.2
    • @​changesets/get-dependents-graph@​2.1.1
    • @​changesets/assemble-release-plan@​6.0.3
    • @​changesets/get-release-plan@​4.0.3
Commits


Updates @rspack/cli from 0.7.4 to 0.7.5

Release notes

Sourced from @​rspack/cli's releases.

v0.7.5

What's Changed

Bug Fixes 🐞

Full Changelog: https://github.com/web-infra-dev/rspack/compare/v0.7.4...v0.7.5

Commits


Updates esbuild from 0.21.5 to 0.23.0

Release notes

Sourced from esbuild's releases.

v0.23.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.22.0 or ~0.22.0. See npm's documentation about semver for more information.

  • Revert the recent change to avoid bundling dependencies for node (#3819)

    This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

  • Fix preserving collapsed JSX whitespace (#3818)

    When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

    // Original code
<Foo>
  <Bar />
</Foo>

    // Old output (with --jsx=preserve)
    
<Foo><Bar /></Foo>;
    

    // New output (with --jsx=preserve)
    
<Foo>
    
<Bar />
    
</Foo>;

v0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.

  • Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

    The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

  • Drop support for older platforms (#3802)

    This release drops support for the following operating systems:

    • Windows 7
    • Windows 8
    • Windows Server 2008
    • Windows Server 2012

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.23.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.22.0 or ~0.22.0. See npm's documentation about semver for more information.

  • Revert the recent change to avoid bundling dependencies for node (#3819)

    This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

  • Fix preserving collapsed JSX whitespace (#3818)

    When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

    // Original code
<Foo>
  <Bar />
</Foo>

    // Old output (with --jsx=preserve)
    
<Foo><Bar /></Foo>;
    

    // New output (with --jsx=preserve)
    
<Foo>
    
<Bar />
    
</Foo>;

0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.

  • Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

    The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

  • Drop support for older platforms (#3802)

    This release drops support for the following operating systems:

    • Windows 7
    • Windows 8
    • Windows Server 2008

... (truncated)

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 @rspack/core from 0.7.4 to 0.7.5

Release notes

Sourced from @​rspack/core's releases.

v0.7.5

What's Changed

Bug Fixes 🐞

Full Changelog: https://github.com/web-infra-dev/rspack/compare/v0.7.4...v0.7.5

Commits


Updates @types/node from 20.14.8 to 20.14.10

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


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 2 months ago

🦋 Changeset detected

Latest commit: 5bc8dc6df36792981d7512bff787e75963c11d73

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package | Name | Type | | ---------------- | ----- | | create-anywidget | Patch |

Not sure what this means? Click here to learn what changesets are.

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