microsoft / microsoft/fluentui

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

Open
#36,466 0 comments 0 reactions 1 assignee View on GitHub

@chrisdholt is already working on this.

Since Aug 3, 2026.

Area: Build System Fluent UI WC (v3) From Shield Good First Issue 🏆 Help Wanted ✨ Type: Bug :bug: web-components
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

Description

Component

Other...

Package version

3.0.2

@microsoft/fast-element version

3.0.0

Environment
Installing @fluentui/web-components@3.0.2 on Node.js 26+ outputs an EBADENGINE warning because the package specifies an upper-bound restriction on supported Node versions (^22.0.0 || ^24.0.0).

The ceiling on the Node.js version field was added in PR #35286.

Suggested Fix
Update the engines.node field in package.json to allow newer Node.js releases (e.g., >=22.0.0 or updating to include ^26.0.0).
Current Behavior

The following warning is printed during install:

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@fluentui/web-components@3.0.2',
npm warn EBADENGINE   required: { node: '^22.0.0 || ^24.0.0' },
npm warn EBADENGINE   current: { node: 'v26.5.1', npm: '11.17.0' }
npm warn EBADENGINE }
Expected Behavior

npm install completes without engine compatibility warnings on active, stable/even-numbered Node versions unless there is an intentional breaking incompatibility.

Reproduction

npm install @fluentui/web-components@3.0.2

Steps to reproduce

Ensure Node.js version is >= 26.0.0 (e.g., v26.5.1).
Run npm install @fluentui/web-components@3.0.2.

Are you reporting an Accessibility issue?

no

Suggested severity

Low - Has or doesn't need a workaround

Products/sites affected

No response

Are you willing to submit a PR to fix?

yes

Validations
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • The provided reproduction is a minimal reproducible example of the bug.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.