Skip to content

fix(web-components): allow Node.js 26 in engines - #36481

Draft
AKnassa wants to merge 1 commit into
microsoft:masterfrom
AKnassa:ak-issue-36466-node26-engines
Draft

fix(web-components): allow Node.js 26 in engines#36481
AKnassa wants to merge 1 commit into
microsoft:masterfrom
AKnassa:ak-issue-36466-node26-engines

Conversation

@AKnassa

@AKnassa AKnassa commented Aug 1, 2026

Copy link
Copy Markdown

Previous Behavior

Installing @fluentui/web-components on Node.js 26 prints a scary EBADENGINE warning, because the package says it only supports Node 22 and 24. That list was written before Node 26 existed.

New Behavior

Installing on Node 26 is quiet and clean. The package now lists Node 22, 24, and 26 as supported — keeping the same "even LTS versions only" style the repo already uses, so odd versions (23, 25, 27) are still excluded on purpose.

What changed

  • One line in packages/web-components/package.json: the supported-Node list gains ^26.0.0.
  • A change file for the release notes.

How to verify

Run npm install @fluentui/web-components on Node 26 — no more warning. We also checked the version range directly with semver: 22.x/24.x/26.x pass, 23/25/27 still don't.

Related Issue(s)

Installing @fluentui/web-components on Node.js 26+ prints an
npm EBADENGINE warning because the engines range (^22.0.0 || ^24.0.0,
set before Node 26 existed) excludes it. Add ^26.0.0, keeping the
even-LTS-majors pinning style.

Verified with semver: 22.x/24.x/26.x satisfy the new range; odd
majors (23/25/27) remain excluded as before.

Fixes microsoft#36466
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Engine warning on Node.js 26+ (@fluentui/web-components@3.0.2)

1 participant