Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @biomejs/biome to v1.8.2 #759

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 1, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@biomejs/biome (source) 1.8.0 -> 1.8.2 age adoption passing confidence

Release Notes

biomejs/biome (@​biomejs/biome)

v1.8.2

Compare Source

CLI
Bug fixes
  • Fix #​3201 by correctly injecting the source code of the file when printing the diagnostics. Contributed by @​ematipico
  • Fix #​3179 where comma separators are not correctly removed after running biome migrate and thus choke the parser. Contributed by @​Sec-ant
  • Fix #​3232 by correctly using the colors set by the user. Contributed by @​ematipico
Enhancement
  • Reword the reporter message No fixes needed to No fixes applied.

    The former message is misleading when there're still errors or warnings in the files that should be taken care of manually. For example:

    Checked 2 files in <TIME>. No fixes needed.
    Found 2 errors.
    

    The new message suits better in these cases.

    Contributed by @​Sec-ant

Configuration
Bug fixes
  • Don't conceal previous overrides (#​3176).

    Previously, each override inherited the unset configuration of the base configuration.
    This means that setting a configuration in an override can be concealed by a subsequent override that inherits of the value from the base configuration.

    For example, in the next example, noDebugger was disabled for the index.js file.

    {
      "linter": {
        "rules": {
          "suspicious": { "noDebugger": "off" }
        }
      },
      "overrides": [
        {
          "include": ["index.js"],
          "linter": {
            "rules": {
              "suspicious": { "noDebugger": "warn" }
            }
          }
        }, {
          "include": ["index.js"],
          "linter": {
            "rules": {
              "suspicious": { "noDoubleEquals": "off" }
            }
          }
        }
      ]
    }

    The rule is now correctly enabled for the index.js file.

    Contributed by @​Conaclos

Formatter
Bug fixes
JavaScript APIs
Bug fixes
  • Fix a regression introduced by the release of v1.8.0
Linter
New features
Bug fixes
  • Add nursery/noShorthandPropertyOverrides. #​2958 Contributed by @​neokidev

  • Fix [#​3084] false positive by correctly recognize parenthesized return statement. Contributed by @​unvalley

  • useImportExtensions now suggests a correct fix for import '.' and import './.'. Contributed by @​minht11

  • Fix useDateNow false positive when new Date object has arguments new Date(0).getTime(). Contributed by @​minht11.

  • The noUnmatchableAnbSelector rule is now able to catch unmatchable an+b selectors like 0n+0 or -0n+0. Contributed by @​Sec-ant.

  • The useHookAtTopLevel rule now recognizes properties named as hooks like foo.useFoo(). Contributed by @​ksnyder9801

  • Fix #​3092, prevent warning for Custom properties (--*). Contributed by @​chansuke

  • Fix a false positive in the useLiteralKeys rule. (#​3160)

    This rule now ignores the following kind of computed member name:

    const a = {
      [`line1
      line2`]: true,
    };

    Contributed by @​Sec-ant

  • The noUnknownProperty rule now ignores the composes property often used in css modules. #​3000 Contributed by @​chansuke

  • Fix false positives of the useExhaustiveDependencies rule.

    The component itself is considered stable when it is used recursively inside a hook closure defined inside of it:

    import { useMemo } from "react";
    
    function MyRecursiveComponent() {
      // MyRecursiveComponent is stable, we don't need to add it to the dependencies list.
      const children = useMemo(() => <MyRecursiveComponent />, []);
      return <div>{children}</div>;
    }

    Also, export default function and export default class are considered stable now because they can only appear at the top level of a module.

    Contributed by @​Sec-ant

  • Fix missing withDefaults macro in vue files for globals variables. Contributed by @​Shyam-Chen

Parser
Bug fixes

v1.8.1

Compare Source

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
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
Parser
New features
  • Implemented CSS Unknown At-Rule parsing, allowing the parser to gracefully handle unsupported or unrecognized CSS at-rules. Contributed by @​denbezrukov
Bug fixes
  • Fix #​3055 CSS: Layout using named grid lines is now correctly parsed. Contributed by @​denbezrukov
  • Fix #​3091. Allows the parser to handle nested style rules and at-rules properly, enhancing the parser's compatibility with the CSS Nesting Module. Contributed by @​denbezrukov

Configuration

📅 Schedule: Branch creation - "before 5pm on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.6.3 chore(deps): update dependency @biomejs/biome to v1.6.4 Apr 3, 2024
@renovate renovate bot force-pushed the renovate/biomejs-biome-1.x branch from 4a2b9f0 to 03de7aa Compare April 3, 2024 11:15
@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.6.4 chore(deps): update dependency @biomejs/biome to v1.7.0 Apr 15, 2024
@renovate renovate bot force-pushed the renovate/biomejs-biome-1.x branch from 03de7aa to 88c27d4 Compare April 15, 2024 14:21
@renovate renovate bot force-pushed the renovate/biomejs-biome-1.x branch from 88c27d4 to 836b48a Compare April 22, 2024 20:20
@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.7.0 chore(deps): update dependency @biomejs/biome to v1.7.1 Apr 22, 2024
@renovate renovate bot force-pushed the renovate/biomejs-biome-1.x branch from 836b48a to 97885e3 Compare April 30, 2024 13:22
@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.7.1 chore(deps): update dependency @biomejs/biome to v1.7.2 Apr 30, 2024
@renovate renovate bot force-pushed the renovate/biomejs-biome-1.x branch from 97885e3 to 9637b6b Compare May 6, 2024 10:35
@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.7.2 chore(deps): update dependency @biomejs/biome to v1.7.3 May 6, 2024
@renovate renovate bot force-pushed the renovate/biomejs-biome-1.x branch from 9637b6b to da1a207 Compare June 4, 2024 14:07
@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.7.3 chore(deps): update dependency @biomejs/biome to v1.8.0 Jun 4, 2024
@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.8.0 chore(deps): update dependency @biomejs/biome to v1.8.0 - autoclosed Jun 5, 2024
@renovate renovate bot closed this Jun 5, 2024
@renovate renovate bot deleted the renovate/biomejs-biome-1.x branch June 5, 2024 03:19
@renovate renovate bot restored the renovate/biomejs-biome-1.x branch June 10, 2024 15:30
@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.8.0 - autoclosed chore(deps): update dependency @biomejs/biome to v1.8.0 Jun 10, 2024
@renovate renovate bot reopened this Jun 10, 2024
@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.8.0 chore(deps): update dependency @biomejs/biome to v1.8.1 Jun 10, 2024
@renovate renovate bot force-pushed the renovate/biomejs-biome-1.x branch from da1a207 to c4b5463 Compare June 10, 2024 20:08
@renovate renovate bot changed the title chore(deps): update dependency @biomejs/biome to v1.8.1 chore(deps): update dependency @biomejs/biome to v1.8.2 Jun 20, 2024
@renovate renovate bot force-pushed the renovate/biomejs-biome-1.x branch from c4b5463 to f78066e Compare June 20, 2024 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants