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.
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.
#1361954a16a Thanks @jakebailey! - Version 2.25.0 introduced the privatePackage configuration option with default { version: false, tag: false }; due to a bug, these options were not respected in all commands, leading to commands like changeset tag still tagging private packages. This has been fixed, and all packages now respect this option.
#1369d729d8c Thanks @Andarist! - changeset tag should now correctly skip tags that exist on the remote
#135718c966a Thanks @Andarist! - Fixed an issue with changeset status executed without since argument. It should now correctly use the configured base branch as the default value.
Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.
⚠️ This change may cause significant differences in your coverage results compared to Vitest v1. These changes are expected as coverage reporting is now more accurate. See vitest-dev/vitest#5423 for more details.
Previously, the location field pointed to the error location instead of the test location. Now it is aligned with jest and contains the line and column of a test function, but requires includeTaskLocation to be enabled.
⚠️ Vitest no longer unwraps promises in spy.mock.returns. If the function is async or returns a promise, it will always succeed and have a Promise in results. To make migration easier, we introduced spy.mock.settledResults that unwraps promises and expect().toHaveResolved() matcher that accepts unwrapped value.
Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.
⚠️ This change may cause significant differences in your coverage results compared to Vitest v1. These changes are expected as coverage reporting is now more accurate. See vitest-dev/vitest#5423 for more details.
Previously, the location field pointed to the error location instead of the test location. Now it is aligned with jest and contains the line and column of a test function, but requires includeTaskLocation to be enabled.
⚠️ Vitest no longer unwraps promises in spy.mock.returns. If the function is async or returns a promise, it will always succeed and have a Promise in results. To make migration easier, we introduced spy.mock.settledResults that unwraps promises and expect().toHaveResolved() matcher that accepts unwrapped value.
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 0 packages
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Bumps the dev-dependencies group with 12 updates:
1.6.11.8.32.27.12.27.71.4.02.0.01.4.02.0.020.11.2820.14.107.2.07.15.08.57.09.6.00.31.41.2.26.8.06.9.00.13.00.14.03.2.53.3.20.5.90.8.0Updates
@biomejs/biomefrom 1.6.1 to 1.8.3Release notes
Sourced from
@biomejs/biome's releases.... (truncated)
Changelog
Sourced from
@biomejs/biome's changelog.... (truncated)
Commits
c28d597release: v1.8.3 (#3302)f88b7b2chore: update codegen to include GraphQL (#3301)6f9c938feat(noExportedImports): add lint rule (#3097)cd3bb04chore(deps): update@biomejspackages (#3266)54b4c9arelease: v1.8.2 (#3243)6f8cab7feat(biome_css_analyzer): implement function-linear-gradient-no-nonstandard-d...0d9b60afeat(lint/useValidAutocomplete): add rule (#3143)9d518d8chore(deps): update@biomejspackages (#3145)4a7baaafeat(biome_js_analyzer):noSubstr(#3125)535acc7fix(ci): rule check error messages (#3158)Updates
@changesets/clifrom 2.27.1 to 2.27.7Release notes
Sourced from
@changesets/cli's releases.... (truncated)
Commits
b593756Version Packages (#1398)d83e458Update changelog for privatePackage fix (#1402)dd6e5bbFixed a crash when root workspace has dependents (#1400)d108fa6Fixed a crash when using tag versions of workspace packages (#1047)a832b64fix typo in automating-changesets.md (#1155)b036aaeVersion Packages (#1393)6a3452eRemove tty-table dependency (#1390)f295b3eReplace meow with mri (#1392)761b2d3update yarn.lock file for breakword@1.0.6 (#1372)fcfb0f8Add FUNDING.jsonUpdates
@vitest/uifrom 1.4.0 to 2.0.0Release notes
Sourced from
@vitest/ui's releases.... (truncated)
Commits
1b150a3chore: release v2.0.05611895chore: release v2.0.0-beta.1305d5f38chore(deps): update all non-major dependencies (#5957)7ec298efeat(ui): add action to explorer item to show the test/suite line in the sour...cd9cc6bchore: release v2.0.0-beta.127fd341cchore(ui): addexplorer.mdoverall behavior (#5950)c31c41cfeat(ui): add initializing explorer logic (#5941)ea12834chore(ui): fix teardown type in Error shim (#5949)e390cb9chore(ui): cleanup old optimization code (#5951)e9ddf9cfix(ui):FileDetailstitle status icon not being updated (#5942)Updates
vitestfrom 1.4.0 to 2.0.0Release notes
Sourced from vitest's releases.
... (truncated)
Commits
1b150a3chore: release v2.0.05131992docs: default pool in the types of 2.0 config (#6043)5611895chore: release v2.0.0-beta.138f65ae9fix: transpile esnext to node18 to support newest JS and TS features (#4409)583dd8afeat(vitest)!: add "vitest list" API to print collected tests without running...f645e48feat: exposeparseAst,parseAstAsyncfrom vite91ba6f9fix(vitest): show all failed tests when rerunning a test (#6022)a820b15docs: add mock fs section (#6021)05d5f38chore(deps): update all non-major dependencies (#5957)c8d56fefix(vitest): allow testing unandled rejection/exception (#6016)Updates
@types/nodefrom 20.11.28 to 20.14.10Commits
Updates
@typescript-eslint/parserfrom 7.2.0 to 7.15.0Release notes
Sourced from
@typescript-eslint/parser's releases.... (truncated)
Changelog
Sourced from
@typescript-eslint/parser's changelog.... (truncated)
Commits
2865d31chore(release): publish 7.15.0b4fe94fchore(release): publish 7.14.1dfc4469chore(release): publish 7.14.01212a8fchore(release): publish 7.13.18a178edchore(release): publish 7.13.0c9a6dd9feat(parser, typescript-estree): export withoutProjectParserOptions utility (...7e93b28chore(release): publish 7.12.02bbf656fix(types): correct typing ParserOptions (#9202)e360541chore(release): publish 7.11.0c18226echore(release): publish 7.10.0Updates
eslintfrom 8.57.0 to 9.6.0Release notes
Sourced from eslint's releases.
🦋 Changeset detected
Latest commit: ebf60bd211b34aff22734a86a8a25af34a05954b
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 0 packages
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver typesNot 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
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.
To ignore these dependencies, configure ignore rules in dependabot.yml