almeidx / discord-ban-sync

Sync bans across multiple Discord servers
Apache License 2.0
6 stars 5 forks source link

Bump the non-major group with 4 updates #239

Closed dependabot[bot] closed 9 months ago

dependabot[bot] commented 10 months ago

Bumps the non-major group with 4 updates: @biomejs/biome, @types/node, dprint and esbuild.

Updates @biomejs/biome from 1.4.1 to 1.5.1

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.5.1

CLI

Bug fixes

  • The diagnostics files/missingHandler are now shown only when the option --verbose is passed. Contributed by @​ematipico
  • The diagnostics for protected files are now shown only when the option --verbose is passed. Contributed by @​ematipico
  • Fix #1465, by taking in consideration the workspace folder when matching a pattern. Contributed by @​ematipico
  • Fix #1465, by correctly process globs that contain file names. Contributed by @​ematipico

Formatter

Bug fixes

  • Fix #1170. Fix placement of comments inside default switch clause. Now all line comments that have a preceding node will keep their position. Contributed by @​kalleep

Linter

Bug fixes

  • Fix #1335. noUselessFragments now ignores code action on component props when the fragment is empty. Contributed by @​vasucp1207

  • useConsistentArrayType was accidentally placed in the style rule group instead of the nursery group. It is now correctly placed under nursery.

  • Fix #1483. useConsistentArrayType now correctly handles its option. Contributed by @​Conaclos

  • Fix #1502. useArrowFunction now correctly handle functions that return a (comma) sequence expression. Contributed by @​Conaclos

    Previously the rule made an erroneous suggestion:

    - f(function() { return 0, 1; }, "");
    + f(() => 0, 1, "")
    

    Now, the rule wraps any comma sequence between parentheses:

    - f(function() { return 0, 1; }, "");
    + f(() => (0, 1), "")
    

What's Changed

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

1.5.1 (2024-01-10)

CLI

Bug fixes

  • The diagnostics files/missingHandler are now shown only when the option --verbose is passed. Contributed by @​ematipico
  • The diagnostics for protected files are now shown only when the option --verbose is passed. Contributed by @​ematipico
  • Fix #1465, by taking in consideration the workspace folder when matching a pattern. Contributed by @​ematipico
  • Fix #1465, by correctly process globs that contain file names. Contributed by @​ematipico

Formatter

Bug fixes

  • Fix #1170. Fix placement of comments inside default switch clause. Now all line comments that have a preceding node will keep their position. Contributed by @​kalleep

Linter

Bug fixes

  • Fix #1335. noUselessFragments now ignores code action on component props when the fragment is empty. Contributed by @​vasucp1207

  • useConsistentArrayType was accidentally placed in the style rule group instead of the nursery group. It is now correctly placed under nursery.

  • Fix #1483. useConsistentArrayType now correctly handles its option. Contributed by @​Conaclos

  • Fix #1502. useArrowFunction now correctly handle functions that return a (comma) sequence expression. Contributed by @​Conaclos

    Previously the rule made an erroneous suggestion:

    - f(function() { return 0, 1; }, "");
    + f(() => 0, 1, "")
    

    Now, the rule wraps any comma sequence between parentheses:

    - f(function() { return 0, 1; }, "");
    + f(() => (0, 1), "")
    
  • Fix #1473: useHookAtTopLevel now correctly handles React components and hooks that are nested inside other functions. Contributed by @​arendjr

1.5.0 (2024-01-08)

Biome now scores 97% compatibility with Prettier and features more than 180 linter rules.

... (truncated)

Commits
  • 0ed9e3e release: 1.5.1 (#1506)
  • 6473a2e fix(lint/useConsistentArrayType): move this unstable rule to nursery (#1492)
  • d0d7aec fix(lint/useConsistentArrayType): correctly handle rule's option (#1490)
  • c1fdabc release: 1.5.0 (#1231)
  • a42f202 feat(lint/noGlobalAssign): add rule (#1377)
  • 6f2a887 feat(lint/useImportType): add rule (#1204)
  • dcf34c4 docs(README): update rule count (#1434)
  • b88f8b7 feat(lint/noGlobalEval): add rule (#1133)
  • ff8862b fix(lint/useHookAtTopLevel): fix false positives, don't require hook config (...
  • 9b07bc8 feat(lint/useFilenamingConvention): allow PascalCase in config (#1414)
  • Additional commits viewable in compare view


Updates @types/node from 20.10.5 to 20.11.0

Commits


Updates dprint from 0.44.0 to 0.45.0

Release notes

Sourced from dprint's releases.

0.45.0

Changes

  • feat: experimental lsp (#803)
  • feat: protect against plugin formatting non-empty file above 300 chars to empty file (#807)
  • fix: upgrade wasmer to 4.2.5 (#809)
  • fix: respect NO_COLOR env var (#808)

Experimental Language Server

This release adds a language server to dprint found at dprint lsp. This will allow more easily using dprint in editors beside vscode and intellij, such as Neovim.

To try it out in vscode, add "dprint.experimentalLsp": true to your vscode settings. Please try it out and let me know if you run into any issues.

Outstanding tasks:

  • Figure out how to do completions for dprint.json files (dprint/dprint#806)
  • Document how to use dprint lsp with editors such as Neovim (dprint/dprint#810)
    • If you use Neovim or any other editor that easily supports the LSP, please consider contributing some setup documentation instructions as I'm very unfamiliar with other editors.

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

Artifact SHA-256 Checksum
dprint-x86_64-apple-darwin.zip 6df01e0357049ad3bc62bbd2f60c9c448bd747b650ebf20f7ab5a38cefd36b44
dprint-aarch64-apple-darwin.zip cf23ab2785ca25f27ed5ca5127663dfe0131ae146d0b8d5159b06e0694ad74ac
dprint-x86_64-pc-windows-msvc.zip 0a5a83b521f152cd83cfb95ef119286e472b3b43077b3ffaeb4b3297fbb52e7f
dprint-x86_64-pc-windows-msvc-installer.exe 88d7bd63ce389f0ac2cacb53b020de1319bbe9ea104aa8390788cbfe10a74bea
dprint-x86_64-unknown-linux-gnu.zip 581e44d57631498edfed6baad5dd77d832116a12c94dd6fb394045ed40af18ea
dprint-x86_64-unknown-linux-musl.zip 8fb959aeeb441e0038217a7973f3a8e246e7aa46b77b33ba5f5e2f38d86f531b
dprint-aarch64-unknown-linux-gnu.zip 45af380a82a65ebe173de25329093fc2e27cf64f3aeef9e39f723873b12fba7f
dprint-aarch64-unknown-linux-musl.zip 48ba9f0910e32a66c869cffc6fd96d2d8f000ffb3d11234e71ae952f322dc849
Commits


Updates esbuild from 0.19.10 to 0.19.11

Release notes

Sourced from esbuild's releases.

v0.19.11

  • Fix TypeScript-specific class transform edge case (#3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
    class Foo extends Bar {
      #private = 1;
      public: any;
      constructor() {
        super();
      }
    }
    

    // Old output (with esbuild v0.19.9) class Foo extends Bar { constructor() { super(); this.#private = 1; } #private; }

    // Old output (with esbuild v0.19.10) class Foo extends Bar { constructor() { this.#private = 1; super(); } #private; }

    // New output class Foo extends Bar { #private = 1; constructor() { super(); } }

  • Minifier: allow reording a primitive past a side-effect (#3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

    // Original code
    function f() {
      let x = false;
    

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.19.11

  • Fix TypeScript-specific class transform edge case (#3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
    class Foo extends Bar {
      #private = 1;
      public: any;
      constructor() {
        super();
      }
    }
    

    // Old output (with esbuild v0.19.9) class Foo extends Bar { constructor() { super(); this.#private = 1; } #private; }

    // Old output (with esbuild v0.19.10) class Foo extends Bar { constructor() { this.#private = 1; super(); } #private; }

    // New output class Foo extends Bar { #private = 1; constructor() { super(); } }

  • Minifier: allow reording a primitive past a side-effect (#3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

    // Original code
    function f() {
    

... (truncated)

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
dependabot[bot] commented 9 months ago

Superseded by #240.