Error when installing DSpace 10.0 frontend

40 views
Skip to first unread message

Lewatle Johannes Phaladi

unread,
Jun 18, 2026, 8:40:01 AM (5 days ago) Jun 18
to DSpace Technical Support
Hi All DSpace Tech,

I am getting the following error:

dspace-angular-dspace-10.0$ npm install
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @mui/icons-m...@7.3.11
npm error Found: re...@16.14.0
npm error node_modules/react
npm error   peer react@">=16" from @custom-react-hooks/use-elem...@1.5.1
npm error   node_modules/@custom-react-hooks/use-element-size
npm error     @custom-react-hooks/use-element-size@"^1.5.1" from mir...@4.0.0
npm error     node_modules/mirador
npm error       mirador@"^4.0.0" from the root project
npm error       2 more (mirador-dl-plugin, mirador-share-plugin)
npm error   peer react@">=16.8.0" from @emotion/re...@11.14.0
npm error   node_modules/@emotion/react
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/sty...@11.14.1
npm error     node_modules/@emotion/styled
npm error       peerOptional @emotion/styled@"^11.3.0" from @mui/mate...@7.3.11
npm error       node_modules/@mui/material
npm error         peer @mui/material@"^7.3.11" from @mui/icons-m...@7.3.11
npm error         node_modules/@mui/icons-material
npm error         4 more (mirador, mirador-dl-plugin, mirador-share-plugin, @mui/x-tree-view)
npm error       6 more (@mui/system, @mui/styled-engine, mirador, ...)
npm error     peerOptional @emotion/react@"^11.5.0" from @mui/mate...@7.3.11
npm error     node_modules/@mui/material
npm error       peer @mui/material@"^7.3.11" from @mui/icons-m...@7.3.11
npm error       node_modules/@mui/icons-material
npm error         @mui/icons-material@"^7.0.0" from mir...@4.0.0
npm error         node_modules/mirador
npm error         1 more (mirador-share-plugin)
npm error       4 more (mirador, mirador-dl-plugin, mirador-share-plugin, @mui/x-tree-view)
npm error     6 more (@mui/system, @mui/styled-engine, mirador, ...)
npm error   27 more (@emotion/styled, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^17.0.0 || ^18.0.0 || ^19.0.0" from @mui/icons-m...@7.3.11
npm error node_modules/@mui/icons-material
npm error   @mui/icons-material@"^7.0.0" from mir...@4.0.0
npm error   node_modules/mirador
npm error     mirador@"^4.0.0" from the root project
npm error     2 more (mirador-dl-plugin, mirador-share-plugin)
npm error   peer @mui/icons-material@"^7.0.0" from mirador-sh...@1.0.0
npm error   node_modules/mirador-share-plugin
npm error     mirador-share-plugin@"^1.0.0" from the root project
npm error
npm error Conflicting peer dependency: re...@19.2.7
npm error node_modules/react
npm error   peer react@"^17.0.0 || ^18.0.0 || ^19.0.0" from @mui/icons-m...@7.3.11
npm error   node_modules/@mui/icons-material
npm error     @mui/icons-material@"^7.0.0" from mir...@4.0.0
npm error     node_modules/mirador
npm error       mirador@"^4.0.0" from the root project
npm error       2 more (mirador-dl-plugin, mirador-share-plugin)
npm error     peer @mui/icons-material@"^7.0.0" from mirador-sh...@1.0.0
npm error     node_modules/mirador-share-plugin
npm error       mirador-share-plugin@"^1.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /dspace/.npm/_logs/2026-06-18T12_31_52_517Z-eresolve-report.txt
npm error A complete log of this run can be found in: /dspace/.npm/_logs/2026-06-18T12_31_52_517Z-debug-0.log

May you help where to adjust.

Regards,
Lewatle 

Bold T Ncube

unread,
Jun 18, 2026, 9:41:31 AM (5 days ago) Jun 18
to Lewatle Johannes Phaladi, DSpace Technical Support
Hi Lewatle, 

What node version are you using? It might be a node version issue

Kind regards,

--
All messages to this mailing list should adhere to the Code of Conduct: https://lyrasis.org/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/e95b8fe7-cc4e-4532-bdda-704152a21e4en%40googlegroups.com.

Disclaimer:  https://www.nust.ac.zw/index.php/e-mail-disclaimer.html

Privacy Notice: https://www.nust.ac.zw/index.php/privacy-notice.html.html

Kevon Muhoozi

unread,
Jun 18, 2026, 9:41:31 AM (5 days ago) Jun 18
to Lewatle Johannes Phaladi, DSpace Technical Support
What are the versions of npm and node are you running on your machine?


Lewatle Johannes Phaladi

unread,
Jun 18, 2026, 10:06:23 AM (5 days ago) Jun 18
to DSpace Technical Support
Hello Kevon,

I am using the following versions :
$ node -v
v24.16.0

$ nodejs -v
v24.16.0

$ npm -v
11.13.0


Regards,
Lewatle 

Bold T Ncube

unread,
Jun 18, 2026, 10:11:36 AM (5 days ago) Jun 18
to Lewatle Johannes Phaladi, DSpace Technical Support
Kindly try using node v22.x

Kevon Muhoozi

unread,
Jun 18, 2026, 11:21:37 AM (5 days ago) Jun 18
to Lewatle Johannes Phaladi, DSpace Technical Support
Downgrade your npm version to 10.9.4

Kevon Muhoozi

unread,
Jun 18, 2026, 11:46:14 AM (5 days ago) Jun 18
to Bold T Ncube, Lewatle Johannes Phaladi, DSpace Technical Support
These errors are not caused by node version but instead they are usually because of the node package manager npm to fail import legacy packages.


Lewatle Johannes Phaladi

unread,
Jun 19, 2026, 4:21:30 AM (4 days ago) Jun 19
to DSpace Technical Support
Hello Bold,

I have downgraded node to version 22,  but still getting error when installing frontend.

$ node -v
v22.23.0

Regards,
Lewatle 

Kevon Muhoozi

unread,
Jun 19, 2026, 8:45:46 AM (4 days ago) Jun 19
to Lewatle Johannes Phaladi, DSpace Technical Support
Hello Lewatle!
Use this: npm install -g n...@10.9.4 to install a supported version of npm for the packages.
Please don't run npm fix audit; these errors often occur when you try to fix the warnings.
And also you go ahead to allow npm to install the legacy dependencies with  npm install --legacy-peer-deps
The step you are at is to install dependencies to support your frontend build.
Also, for clear support, provide this output: "cat  /dspace/.npm/_logs/2026-06-18T12_31_52_517Z-eresolve-report.txt"

Alfeu Uzai Tavares

unread,
Jun 19, 2026, 12:55:32 PM (4 days ago) Jun 19
to Kevon Muhoozi, Lewatle Johannes Phaladi, DSpace Technical Support
Hello Lewatle,

I had similar dependency problems when upgrading from 9.2 to 10.0 due to other npm dependencies I had installed in the project, used in custom code.
To fix it, I deleted the node_modules folder and replaced files package.json and package-lock.json with default ones from the DSpace version being used. 
After that, I re-installed the other packages with npm install <package-name>, and then performed the npm install of the project. This fixed all problems.
I'm using node --version: v24.12.0 and npm --version: 10.9.8.


Lewatle Johannes Phaladi

unread,
7:09 AM (9 hours ago) 7:09 AM
to DSpace Technical Support
Hello Alfeu,

Thanks a lot for sharing the steps, I will try on my side and come back with feedback.

Regards,
Lewatle 

Reply all
Reply to author
Forward
0 new messages