Error when installing DSpace 10.0 frontend

[Lewatle Johannes Phaladi]

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]

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]

What are the versions of npm and node are you running on your machine?

[Lewatle Johannes Phaladi]

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]

Kindly try using node v22.x

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/156d9ef4-66cd-4b98-93be-096f7699d9dan%40googlegroups.com.

[Kevon Muhoozi]

Downgrade your npm version to 10.9.4

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/156d9ef4-66cd-4b98-93be-096f7699d9dan%40googlegroups.com.

[Kevon Muhoozi]

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.

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/CAMMUn6hr94JvKQhGCYBmhiyMbXNEE-3_CuWhfNDLF2SJGuPGaA%40mail.gmail.com.

[Lewatle Johannes Phaladi]

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]

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"

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/20f52260-232c-4fbe-af72-08c68bcb83b0n%40googlegroups.com.

[Alfeu Uzai Tavares]

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.

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/CA%2BLKazpacKVsLrB1-WDY-9TVo_TRwi%3Dh5_BJGEGkSWe7krjOBg%40mail.gmail.com.

[Lewatle Johannes Phaladi]

Hello Alfeu,

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

Regards,

Lewatle 

[Lewatle Johannes Phaladi]

Hello Alfeu and DSpace Tech,

I have followed your steps and getting error below, is there any network settings that needs to be configured to get npm dependencies sorted? 

Is there any need to wait for DSpace version 10.1 that maybe come bug free from npm dependencies? 

$ npm install
npm warn deprecated infl...@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you wan                                                                                                            t a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated rim...@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rim...@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated gl...@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated redux-devtoo...@2.13.9: Package moved to @redux-devtools/extension.
npm warn deprecated sourcem...@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm warn deprecated crit...@0.0.24: Ownership of Critters has moved to the Nuxt team, who will be maintaining the project going forward. If you'd like to keep using Critters, please switch to the actively-maintained fork at https://github.com/danielroe/beasties
npm warn deprecated @npmcli/move...@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated @humanwhocodes/config...@0.13.0: Use @eslint/config-array instead
npm warn deprecated @humanwhocodes/object...@2.0.3: Use @eslint/object-schema instead
npm warn deprecated uu...@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm warn deprecated uu...@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm warn deprecated @material-ui/sty...@4.11.5: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.
npm warn deprecated @material-ui/l...@4.0.0-alpha.61: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.
npm warn deprecated react-bea...@13.1.1: react-beautiful-dnd is now deprecated. Context and options: https://github.com/atlassian/react-beautiful-dnd/issues/2672
npm warn deprecated esl...@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm warn deprecated @material-ui/co...@4.12.4: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.

> dspace-...@9.1.0 postinstall
> npm run build:lint || echo 'Skipped DSpace ESLint plugins.'


> dspace-...@9.1.0 build:lint
> rimraf 'lint/dist/**/*.js' 'lint/dist/**/*.js.map' && tsc -b lint/tsconfig.json

lint/src/util/structure.ts:18:20 - error TS2314: Generic type 'RuleMetaData<MessageIds, Options>' requires 2 type argument(s).

18 export type Meta = RuleMetaData<string, unknown, unknown[]>;
                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

lint/src/util/theme-support.ts:13:26 - error TS7016: Could not find a declaration file for module 'glob'. '/dspace/Install/dspace-angular-dspace-10.0/node_modules/glob/glob.js' implicitly has an 'any' type.
  Try `npm i --save-dev @types/glob` if it exists or add a new declaration (.d.ts) file containing `declare module 'glob';`

13 import { globSync } from 'glob';
                            ~~~~~~

lint/src/rules/ts/alias-imports.ts:204:343 - error TS2352: Conversion of type 'Identifier' to type 'StringLiteral' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Type 'Identifier' is missing the following properties from type 'StringLiteral': value, raw

204   const hasCorrectAliasedImport: boolean = (node.parent as TSESTree.ImportDeclaration).specifiers.find((specifier: TSESTree.ImportClause) => specifier.local.name === option.local && specifier.type === AST_NODE_TYPES.ImportSpecifier && ((((specifier as TSESTree.ImportSpecifier).imported as TSESTree.Identifier).name === option.imported) || (((specifier as TSESTree.ImportSpecifier).imported as TSESTree.StringLiteral).value === option.imported))) !== undefined;
                                                                                                                                                                                                                                                                                                                                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

lint/src/rules/ts/alias-imports.ts:264:107 - error TS2352: Conversion of type 'Identifier' to type 'StringLiteral' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.

264     } else if ((node.local.name === (node.imported as TSESTree.Identifier).name) || (node.local.name === (node.imported as TSESTree.StringLiteral).value)) {
                                                                                                              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

lint/src/rules/ts/themed-component-usages.ts:123:101 - error TS2352: Conversion of type 'Identifier' to type 'StringLiteral' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.

123       const entry = getThemeableComponentByBaseClass((importedNode as TSESTree.Identifier).name ?? (importedNode as TSESTree.StringLiteral).value);
                                                                                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

lint/src/rules/ts/themed-component-usages.ts:126:117 - error TS2352: Conversion of type 'Identifier' to type 'StringLiteral' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.

126         throw new Error(`No such themeable component in registry: '${(importedNode as TSESTree.Identifier).name ?? (importedNode as TSESTree.StringLiteral).value}'`);
                                                                                                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

lint/test/testing.ts:29:3 - error TS2353: Object literal may only specify known properties, and 'languageOptions' does not exist in type 'RuleTesterConfig'.

29   languageOptions: {
     ~~~~~~~~~~~~~~~

lint/test/testing.ts:54:3 - error TS2353: Object literal may only specify known properties, and 'languageOptions' does not exist in type 'RuleTesterConfig'.

54   languageOptions: {
     ~~~~~~~~~~~~~~~


Found 8 errors.

Skipped DSpace ESLint plugins.

added 1701 packages, and audited 1704 packages in 55s

337 packages are looking for funding
  run `npm fund` for details

96 vulnerabilities (12 low, 37 moderate, 44 high, 3 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

Regards,

Lewatle 

[DSpace Technical Support]

Hi Lewatle,

It sounds, to me, like you have some pre-installed dependencies that may be conflicting with the new DSpace 10.0 dependencies.

I'd recommend trying to run the following to ensure all your previously dependencies have been removed:

# This removes all previously installed DSpace NPM dependencies, allowing you to start fresh

npm run clean

# Then, try the install again

npm install

Hopefully that'll help you get past this.  I don't believe this is a bug in 10.0 specifically, but rather something that is cached on your machine (in NPM) that is resulting in these errors.

- Tim