Bump @biomejs/biome from 1.4.1 to 1.5.3

[dependabot[bot]]

Bumps @biomejs/biome from 1.4.1 to 1.5.3.

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.5.3

LSP

Bug fixes

• Fix #1584. Ensure the LSP only registers the formatter once. Contributed by @​nhedger

• Fix #1589. Fix invalid formatting of own line comments when they were at the end of an import/export list. Contributed by @​spanishpear

Configuration

Bug fixes

• Override correctly the recommended preset (#1349).

  Previously, if unspecified, Biome turned on the recommended preset in overrides. This resulted in reporting diagnostics with a severity level set to off. This in turn caused Biome to fail.

  Now Biome won't switch on the recommended preset in overrides unless told to do so.

  Contributed by @​Conaclos

• Don't format ignored files that are well-known JSONC files when files.ignoreUnknown is enabled (#1607).

  Previously, Biome always formatted files that are known to be JSONC files (e.g. .eslintrc) when files.ignoreUnknown was enabled.

  Contributed by @​Conaclos

Formatter

Bug fixes

• Fix #1178, where the line ending option wasn't correctly applied. Contributed by @​ematipico
• Fix #1571. Fix invalid formatting of nested multiline comments. Contributed by @​ah-yu

Linter

Bug fixes

• Fix #1575. noArrayIndexKey now captures array index value inside template literals and with string concatination. Contributed by @​vasucp1207

• Linter rules that inspect regexes now handle multibyte characters correctly (#1522).

  Previously, noMisleadingCharacterClass, noMultipleSpacesInRegularExpressionLiterals, and noEmptyCharacterClassInRegex made Biome errors on multi-bytes characters. Multibyte characters are now handled correctly.

  The following code no longer raises an internal error:

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

1.5.3 (2024-01-22)

LSP

Bug fixes

• Fix #1584. Ensure the LSP only registers the formatter once. Contributed by @​nhedger

• Fix #1589. Fix invalid formatting of own line comments when they were at the end of an import/export list. Contributed by @​spanishpear

Configuration

Bug fixes

• Override correctly the recommended preset (#1349).

  Previously, if unspecified, Biome turned on the recommended preset in overrides. This resulted in reporting diagnostics with a severity level set to off. This in turn caused Biome to fail.

  Now Biome won't switch on the recommended preset in overrides unless told to do so.

  Contributed by @​Conaclos

• Don't format ignored files that are well-known JSONC files when files.ignoreUnknown is enabled (#1607).

  Previously, Biome always formatted files that are known to be JSONC files (e.g. .eslintrc) when files.ignoreUnknown was enabled.

  Contributed by @​Conaclos

Formatter

Bug fixes

• Fix #1178, where the line ending option wasn't correctly applied. Contributed by @​ematipico
• Fix #1571. Fix invalid formatting of nested multiline comments. Contributed by @​ah-yu

Linter

Bug fixes

• Fix #1575. noArrayIndexKey now captures array index value inside template literals and with string concatination. Contributed by @​vasucp1207

• Linter rules that inspect regexes now handle multibyte characters correctly (#1522).

  Previously, noMisleadingCharacterClass, noMultipleSpacesInRegularExpressionLiterals, and noEmptyCharacterClassInRegex made Biome errors on multi-bytes characters. Multibyte characters are now handled correctly.

  The following code no longer raises an internal error:

... (truncated)

Commits

• 906de83 release: 1.5.3 (#1629)
• 09db855 feat(project): Deserializable derive macro (#1564)
• 80bb3d7 release: 1.5.2 (#1562)
• 7f78594 refactor(linter): add source metadata (#1519)
• 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)
• 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)