Skip to content

chore(deps-dev): bump ultracite from 7.12.4 to 8.2.0 in /npm - #99

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm/ultracite-8.2.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm/ultracite-8.2.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps ultracite from 7.12.4 to 8.2.0.

Release notes

Sourced from ultracite's releases.

ultracite@8.2.0

Minor Changes

  • f971134: The ESLint angular preset now lints Angular templates, accessibility included, with @angular-eslint/eslint-plugin-template. Until now the preset only linted component classes, so a template got no checks on ESLint.

    Angular projects on ESLint will see new errors in templates. The preset covers every .html file and the inline template of each component in a .ts file, where errors are reported at their place in the TypeScript file and ultracite fix fixes them there. Thirty-nine rules are on at error. The accessibility rules cover missing alt text, labels with no control, click and mouse handlers with no keyboard equivalent, handlers on elements that can't take focus, empty headings, links and buttons, and invalid ARIA roles and attributes. The rest are Angular's general template rules, such as @angular-eslint/template/prefer-control-flow, @angular-eslint/template/eqeqeq, @angular-eslint/template/button-has-type and @angular-eslint/template/no-duplicate-attributes. Measured on three open-source Angular apps, the two rules that report most are @angular-eslint/template/attributes-order and @angular-eslint/template/prefer-self-closing-tags, and ultracite fix fixes both.

    • @angular-eslint/template/no-autofocus is off, as jsx-a11y/no-autofocus is in the React presets. Autofocus is a deliberate UX choice (a waitlist or search field that's ready to type into), and the rule can't tell that from a harmful use.
    • @angular-eslint/template/i18n is off. It only applies to apps translated with Angular's own i18n, and wants an i18n attribute on every element with text and beside attributes such as rel and data-testid.
    • @angular-eslint/template/no-call-expression is off. It reports every signal read (count()), which is how a template reads a signal.
    • @angular-eslint/template/cyclomatic-complexity allows 20 control-flow blocks in a template, as core's complexity allows a function, in place of the plugin's 5.
    • @angular-eslint/template/no-duplicate-attributes accepts a static class or style beside a binding to the same attribute, which Angular merges.
    • @angular-eslint/template/no-inline-styles accepts a style bound to a computed value ([style.width.%]="progress()"), which can't be a class. A static style attribute is still reported.
    • The rules can't see what a directive or component adds. A button whose label comes from a directive (<button appIconButton></button>) is reported as empty by @angular-eslint/template/elements-content. List those attributes in the rule's allowList option in your own config.

    Every .html file is linted as a template, because Angular no longer names templates *.component.html. That includes whole pages: files that start with a doctype, an XML declaration, or an <html>, <head> or <body> element, such as src/index.html, a static page in public/ or an email. A page gets the accessibility rules and the other template rules, apart from three that only fit a template Angular compiles: @angular-eslint/template/prefer-ngsrc, @angular-eslint/template/no-inline-styles and @angular-eslint/template/prefer-self-closing-tags. The last one's fix would turn <my-widget></my-widget> into <my-widget />, which a browser reads as an open tag. A { or } in a page's text, such as in a code sample, is read as text. In any other HTML file it's a parse error, as it is when Angular compiles the template. The inline scripts of an HTML file are linted by core's rules, and github/filenames-match-regex checks each HTML file's name, as core does.

    To change a template rule, set it in a config object with files: ["**/*.html"], which also matches inline templates. That pattern no longer reaches the inline scripts of an HTML file, which are linted as a block of their own: settings for them, such as extra browser globals, need files: ["**/*.html/*.htm"]. Core's JavaScript rules are off for templates, since they can't read a template's syntax tree. A rule your config turns on for every file runs on templates too. Some report there: jsdoc/require-file-overview, for example, reports every template as missing @file. Others throw: github/js-class-name, github/unescaped-html-literal and sonarjs/code-eval throw on a template literal in a template ({{ `Hi ${name}` }}). Give rules meant for your TypeScript files that leave out **/*.html.

    ultracite init installs @angular-eslint/eslint-plugin-template and @angular-eslint/template-parser for Angular projects that choose ESLint. Existing projects get both from ultracite upgrade, which installs every package the presets in your ESLint config load, and ultracite doctor reports the plugin as missing until then. Oxlint doesn't parse Angular templates, and Biome's accessibility rules already run on .html files from its core preset, so neither changes.

  • 37ead86: Ultracite no longer sorts object keys by default. sort-keys is off in the Oxlint and ESLint core presets, and useSortedKeys is off in the Biome core preset, so ultracite fix stops reordering your objects and ultracite check stops reporting unsorted ones.

    Both fixes are classed as safe, so they ran on every ultracite fix, and key order can change what code does: the bytes JSON.stringify writes, the order a loop visits keys, which entry of an exports map wins, and what TypeScript infers for an options object. The research post has the cases we measured on real codebases.

    To keep sorting, turn the rule back on in your own config:

    • Oxlint and ESLint: "sort-keys": "error" in rules.
    • Biome: "useSortedKeys": "on" under assist.actions.source.

    The TanStack presets no longer need their own exemption from key sorting and have dropped it. If you turn sorting back on in a TanStack project, turn it off again for your query, mutation and route option objects, where sorting breaks type inference.

    Biome's useSortedSelectionSet is off too: the order of a GraphQL selection set is the key order of the response. Biome's other sorting actions (imports, JSX attributes, interface members, CSS properties, package.json fields and Tailwind classes) are unchanged.

  • 37ead86: Bring the three linters' presets in line with each other on the rules the research posts measured. Oxlint is the benchmark, so most changes move ESLint and Biome to what Oxlint already did.

    Stricter. These can report new problems when you upgrade.

    • Biome: noExplicitAny now applies to test files too, as no-explicit-any does in Oxlint and ESLint.
    • Biome: noImportCycles moves from the type-aware preset into core, where Oxlint and ESLint already check import cycles. It adds no measurable time, because core skips node_modules (#843).
    • Biome: noExcessiveClassesPerFile is on, matching max-classes-per-file in Oxlint and ESLint.
    • ESLint: the react preset now applies to every JavaScript and TypeScript file, not only .jsx and .tsx, so custom hooks in .ts files get the react-hooks rules and JSX in .js files gets the accessibility rules. Oxlint and Biome already checked both. Linting a non-React TypeScript project with the react preset loaded took about 30% longer in our measurement.
    • Oxlint: the js-plugins, next/js-plugins and tanstack/js-plugins presets gain the 267 React Doctor rules the ESLint presets already ran, so both linters now run the same list. Most are for one library (React Router, three.js, Ink, Motion, Remotion) and stay silent in projects that don't use it. The JS plugin pass took about 1.6 times as long on our test project.
    • ESLint and Oxlint js-plugins: sonarjs/shorthand-property-grouping is on. It was off only because it conflicted with sort-keys, which is now off by default.
    • Oxlint and ESLint: no-warning-comments also reports JSDoc's @todo tag and a marker behind the asterisks of a block comment (/** @todo */, /* ** TODO */).

    Looser, or off.

    • no-unused-vars follows one convention in all three linters: a leading underscore marks a parameter, variable, caught error or destructured array element as unused on purpose, and a property left out with a rest sibling (const { secret, ...rest } = obj) and a using declaration aren't reported. ESLint used to report all of these, and Oxlint reported a bare _ and every unused catch binding. This also stops ultracite fix --unsafe on Oxlint from deleting the omitted property, which put it back into rest. sonarjs/no-unused-vars is off in ESLint and Oxlint js-plugins: it duplicates the rule and has no option for the convention.
    • no-use-before-define sets variables: false in Oxlint and ESLint: a function that mentions a variable declared further down in an outer scope is no longer reported, since the body runs later. Functions that call each other had no order that passed. A use in the same scope, such as a call at load time above the definition, still reports. The TanStack presets now keep the rule on in route files instead of turning it off, so a route that reads its component before the component is declared is reported.
    • react/function-component-definition is off in Oxlint and ESLint. Its fix turned a hoisted function component into a const that could be read before it was defined, and its fix for an unnamed component produced code the rule reported again. func-style still asks for function expressions, and leaves export default function Page() alone.
    • Namespace imports are allowed everywhere: sonarjs/no-wildcard-import is off in ESLint and Oxlint js-plugins, and noNamespaceImport is off in Biome, matching import/no-namespace in Oxlint core. Libraries such as Zod and Radix document import * as as their API.

... (truncated)

Commits
  • cfa365b Version Packages (#865)
  • 9743dfc Lint whole HTML pages as Angular templates and give template nodes a range (#...
  • 872f937 Fix the Oxlint env check and upgrade, and agent-fix matching edge cases (#871)
  • be030e6 Restore a sentence in the waiting list's Qwik row
  • dac28a8 Link the upstream reports for the Solid and Qwik handler names
  • f971134 Add accessibility linting for Vue, Angular, Solid and Qwik
  • 29db0f4 Stop two agent-fix tests depending on test file order
  • d51d243 Read oxlint config names from the AST and keep agent-fix pairing local (#866)
  • 4236d84 Add the prompt revision experiment
  • 59dcdc1 Re-measure the site for the preset changes and correct two changelog entries
  • Additional commits viewable in compare view

Dependabot compatibility score

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 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)

Bumps [ultracite](https://github.com/haydenbleasel/ultracite) from 7.12.4 to 8.2.0.
- [Release notes](https://github.com/haydenbleasel/ultracite/releases)
- [Commits](https://github.com/haydenbleasel/ultracite/compare/ultracite@7.12.4...ultracite@8.2.0)

---
updated-dependencies:
- dependency-name: ultracite
  dependency-version: 8.2.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from mstuart as a code owner November 16, 2026 03:10
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 16, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants