Issues with npm run build:prod in DSpace 10.0

[Marc GOOVAERTS]

When running the build command it is aborted. What can be the problem?

node --version: v24.21.0
npm --version: 11.19.0

These are the messages in my terminal:

marc@marc:~/Downloads/dspace-angular-dspace-10.0$ 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 want 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 gl...@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated gl...@7.2.3: Glob versions prior to v9 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 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 uu...@8.3.2: uuid@10 and below is no longer supported.  For ESM codebases, update to uuid@latest.  For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).
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 @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-...@10.0.0 postinstall
> npm run build:lint || echo 'Skipped DSpace ESLint plugins.'


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


added 1751 packages, and audited 1754 packages in 20s

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

75 vulnerabilities (4 low, 36 moderate, 32 high, 3 critical)

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

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

Run `npm audit` for details.
npm warn install-scripts 7 packages have install scripts not yet covered by allowScripts:
npm warn install-scripts   esb...@0.27.7 (postinstall: node install.js)
npm warn install-scripts   @parcel/wat...@2.5.1 (install: node scripts/build-from-source.js)
npm warn install-scripts   cor...@3.49.0 (postinstall: node -e "try{require('./postinstall')}catch(e){}")
npm warn install-scripts   cyp...@15.15.0 (postinstall: node dist/index.js --exec install)
npm warn install-scripts   esb...@0.28.0 (postinstall: node install.js)
npm warn install-scripts   lm...@3.4.2 (install: node-gyp-build-optional-packages)
npm warn install-scripts   msgpackr...@3.0.3 (install: node-gyp-build-optional-packages)
npm warn install-scripts
npm warn install-scripts Run `npm install-scripts ls` to review, or `npm install-scripts approve <pkg>` to allow.
marc@marc:~/Downloads/dspace-angular-dspace-10.0$ npm run build:prod

> dspace-...@10.0.0 build:prod
> cross-env NODE_ENV=production npm run build:ssr


> dspace-...@10.0.0 build:ssr
> ng build --configuration production && ng run dspace-angular:server:production

⠴ Generating browser application bundles (phase: building)...
<--- Last few GCs --->

[15014:0xc382000]   114101 ms: Scavenge (interleaved) 2031.2 (2055.2) -> 2025.7 (2055.4) MB, pooled: 0 MB, 8.46 / 0.00 ms  (average mu = 0.289, current mu = 0.254) allocation failure;
[15014:0xc382000]   114843 ms: Mark-Compact (reduce) 2033.2 (2056.2) -> 2024.5 (2040.7) MB, pooled: 0 MB, 82.43 / 0.00 ms  (+ 591.2 ms in 117 steps since start of marking, biggest step 8.3 ms, walltime since start of marking 742 ms) (average mu = 0.288, c
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x931db0  [ng build --configuration production (dspace-angular)]
 2: 0x75968e node::OOMErrorHandler(char const*, v8::OOMDetails const&) [ng build --configuration production (dspace-angular)]
 3: 0xc70d60  [ng build --configuration production (dspace-angular)]
 4: 0xc70e4f  [ng build --configuration production (dspace-angular)]
 5: 0xf14725  [ng build --configuration production (dspace-angular)]
 6: 0xf14752  [ng build --configuration production (dspace-angular)]
 7: 0xf14a4a  [ng build --configuration production (dspace-angular)]
 8: 0xf2574a  [ng build --configuration production (dspace-angular)]
 9: 0xf29af0  [ng build --configuration production (dspace-angular)]
10: 0x19c77d1  [ng build --configuration production (dspace-angular)]
Aborted (core dumped)

[schu...@effective-webwork.de]

> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

"out of memory" should be the current problem Try running the build like this (change 8192 to suit your system / the needed memory), to increase the available memory for the build process:

NODE_OPTIONS="--max-old-space-size=8192" npm run build:prod

[Alan Orth]

Dear Marc,

For what it's worth, the DSpace GitHub CI workflows use 4096MB, so this should be enough:

NODE_OPTIONS="--max-old-space-size=4096" npm run build:prod

Also note that officially you should be using NPM v10 to build. That will reduce some of the warnings printed during the process. We will probably switch to a newer NPM from DSpace 11 (see: https://github.com/DSpace/dspace-angular/issues/6245).

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/6df4124d-28b8-4231-a49f-68495c455a3bn%40googlegroups.com.

--

Alan Orth
alan...@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch