eslint-plugin-unicorn 77 moves 11 CSS rules into a package that requires ESLint 10.4 and ESM

Every change here ships in version 77.0.0 ^[2], so the break arrives when a team chooses to install it. The work comes in two sizes. The config fix is a rename of two preset names ^[4]. Of the 11 CSS rules that left the plugin ^[14], seven change only their prefix, from unicorn/ to cssicorn/ ^[15]. The other four also drop "css" from the rule name. A search-and-replace on the prefix alone leaves those four pointing at names eslint-cssicorn does not use ^[15][3].

The larger cost sits in the new package's install line. eslint-cssicorn runs through the @eslint/css language plugin, which goes in next to it as a dev dependency ^[9]. Its README lists ESLint 10.4 or later, flat config and ESM as requirements ^[10]. Its presets cover `**/*.css` files and set up the language plugin themselves ^[11]. For a team already on that stack, the case for calling version 77 routine holds: two packages and a preset. A team on an older ESLint, or with a config that is not ESM, has to finish that migration before it can run version 77 and its CSS checks at once.

A team that lets the CSS rules go at the upgrade keeps some coverage. The cssicorn README says unicorn still has rules that lint CSS, naming no-zero-fractions and no-shorthand-property-overrides ^[1]. Version 77 also adds a recommended-css preset, one of six new presets for languages other than JavaScript ^[5].

The new package is young, and it does not take outside code. It is at version 0.1 ^[13], and its README states: "We do not accept pull requests because of too much AI slop." ^[12]

The recommended preset also changes for teams that make every edit. The rule number-literal-case moves into it from the unopinionated preset, and no-asterisk-prefix-in-documentation-comments, which now also covers CSS and JSON, is enabled in it ^[7]. The release notes list 28 new rules ^[16] without saying which of them recommended turns on.