Skip to content

[@microsoft/sp-image-helper@1.24.1] peerDependencies for react and react-dom still pinned to >=16.13.1 <18.0.0 instead of <19.0.0 #11087

New issue
New issue
Open
Open
[@microsoft/sp-image-helper@1.24.1] peerDependencies for react and react-dom still pinned to >=16.13.1 <18.0.0 instead of <19.0.0#11087
Assignees
Ashlesha-MSFT
Labels
AI-generated responsearea:spfxCategory: SharePoint Framework (not extensions related)status:to-be-reviewedIssue needs to be reviewed by Microsoft for additional follow up / review.type:bug-confirmedConfirmed bug, not working as designed / expected.

Description

@flaviuc
Flaviu C. (flaviuc)
opened on Nov 6, 2026

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

Additional environment details

  • SharePoint Framework: 1.24.1 (and 1.24.0)
  • Package: @microsoft/sp-image-helper@1.24.1
  • Node.js: 22.14.0
  • Browser: Microsoft Edge / Google Chrome (latest)

Describe the bug / error

In SharePoint Framework 1.24.1, @microsoft/generator-sharepoint scaffolds react@18.3.1 and react-dom@18.3.1 (along with @types/react@18.2.79 and @types/react-dom@18.2.25), and @microsoft/sp-core-library@1.24.1 widened its react and react-dom peerDependencies range to >=16.13.1 <19.0.0.

However, @microsoft/sp-image-helper@1.24.1 (which is also pulled in transitively by @microsoft/sp-property-pane@1.24.1) still specifies react and react-dom peerDependencies as >=16.13.1 <18.0.0, even though its @types/react and @types/react-dom peerDependencies were widened to <19.0.0:

  "peerDependencies": {
    "@types/react": ">=17.0.45 <19.0.0",
    "@types/react-dom": ">=17.0.17 <19.0.0",
    "react": ">=16.13.1 <18.0.0",
    "react-dom": ">=16.13.1 <18.0.0"
  }

@microsoft/sp-image-helper appears to be the only published @microsoft/sp-* package in 1.24.1 that still caps react and react-dom peerDependencies below 18.0.0.

Steps to reproduce

  1. Scaffold a new SPFx 1.24.1 React Web Part project using @microsoft/generator-sharepoint@1.24.1 (or inspect npm view @microsoft/sp-image-helper@1.24.1 peerDependencies).
  2. Add @microsoft/sp-image-helper@1.24.1 (or inspect the dependency tree via @microsoft/sp-property-pane@1.24.1) alongside the scaffolded react@18.3.1 and react-dom@18.3.1.
  3. Run npm install or npm ls react react-dom.
  4. Observe the peer dependency conflict (ERESOLVE / invalid peer dependency) because @microsoft/sp-image-helper@1.24.1 requires react: ">=16.13.1 <18.0.0" and react-dom: ">=16.13.1 <18.0.0".

Expected behavior

@microsoft/sp-image-helper should specify "react": ">=16.13.1 <19.0.0" and "react-dom": ">=16.13.1 <19.0.0" in peerDependencies (matching @microsoft/sp-core-library@1.24.1) so SPFx solutions using React 18 install without peer dependency conflicts.

Activity

  1. m365-agent-toolkit-assistant commented on Nov 6, 2026

    @m365-agent-toolkit-assistant
    m365-agent-toolkit-assistantBot
    on Nov 6, 2026 – with m365-agent-toolkit-assistant

    👋 Hi Flaviu C. (@flaviuc),

    Thank you for reporting this issue. Here is an AI-generated initial response:

    Classification: Bug — the reported @microsoft/sp-image-helper@1.24.1 peer range excludes React 18.3.1, which Microsoft specifies for SPFx 1.24.1. The package-metadata mismatch is a likely cause of the reported ERESOLVE; it has not been independently confirmed here.

    Upgrade check: You are already on 1.24.1; no fixing version is established.

    What to do now:

    1. Attach the output of npm view @microsoft/sp-image-helper@1.24.1 peerDependencies and the relevant npm install ERESOLVE section so maintainers can verify the published metadata.
    2. Request a corrected package release. If installation is blocked, npm install --legacy-peer-deps is a temporary bypass, not a compatibility fix; test the resulting solution before deployment.

    Useful links:

    Note: AI-generated guidance may be incomplete or incorrect. Please verify suggestions before applying them.

  2. m365-agent-toolkit-assistant
    added
    AI-generated response
    on Nov 6, 2026
  3. Vesa Juvonen (VesaJuvonen)
    added
    area:spfxCategory: SharePoint Framework (not extensions related)
    status:to-be-reviewedIssue needs to be reviewed by Microsoft for additional follow up / review.
    type:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
    on Nov 6, 2026

  4. flaviuc commented on Nov 6, 2026

    @flaviuc
    Flaviu C. (flaviuc)
    on Nov 6, 2026
    ContributorAuthor

    Here is the requested npm view and npm install ERESOLVE output:

    1. npm view output comparing @microsoft/sp-image-helper@1.24.1 and @microsoft/sp-core-library@1.24.1

    $ npm view @microsoft/sp-image-helper@1.24.1 peerDependencies
{
  '@types/react': '>=17.0.45 <19.0.0',
  '@types/react-dom': '>=17.0.17 <19.0.0',
  react: '>=16.13.1 <18.0.0',
  'react-dom': '>=16.13.1 <18.0.0'
}

$ npm view @microsoft/sp-core-library@1.24.1 peerDependencies
{
  '@types/react': '>=17.0.45 <19.0.0',
  '@types/react-dom': '>=17.0.17 <19.0.0',
  react: '>=16.13.1 <19.0.0',
  'react-dom': '>=16.13.1 <19.0.0'
}

    2. npm install ERESOLVE output with SPFx 1.24.1 (react@18.3.1 / react-dom@18.3.1)

    npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: spfx-1241-repro@1.0.0
npm error Found: react@18.3.1
npm error node_modules/react
npm error   react@"18.3.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@">=16.13.1 <18.0.0" from @microsoft/sp-image-helper@1.24.1
npm error node_modules/@microsoft/sp-image-helper
npm error   @microsoft/sp-image-helper@"1.24.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
  5. Ashlesha-MSFT
    self-assigned this
    on Nov 9, 2026

  6. Ashlesha-MSFT commented on Nov 9, 2026

    @Ashlesha-MSFT
    Ashlesha-MSFT
    on Nov 9, 2026
    Contributor

    Hi Flaviu C. (@flaviuc), thank you for sharing the details and reproduction steps.

    We were able to reproduce the reported ERESOLVE error when installing @microsoft/sp-image-helper@1.24.1 alongside React and React DOM 18.3.1. We confirmed that the package’s peer dependency ranges still exclude React 18, unlike @microsoft/sp-core-library@1.24.1.

    We’ll raise a bug with the engineering team for investigation and share updates in this thread as they become available.

  7. Ashlesha-MSFT
    added
    type:bug-confirmedConfirmed bug, not working as designed / expected.
    and removed
    type:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
    on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

AI-generated responsearea:spfxCategory: SharePoint Framework (not extensions related)status:to-be-reviewedIssue needs to be reviewed by Microsoft for additional follow up / review.type:bug-confirmedConfirmed bug, not working as designed / expected.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions