npm update corrupt project

[waynelam-bod]

Hi,

I am trying update the project since there is a few high (33 vulnerabilities (13 low, 9 moderate, 11 high)) vulnerability. But after the update, npm run start:proxy and build no longer works. Please see below:

Environment:
node -v
v22.21.1

npm -v
10.9.4

npm update message

`npm update
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

added 142 packages, removed 158 packages, changed 354 packages, and audited 1051 packages in 36s

175 packages are looking for funding
run npm fund for details

13 vulnerabilities (6 low, 7 moderate)

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.
PS C:\Users\bodl3227\PycharmProjects\customModule> npm run start:proxy

custom-module@2.0.0 start:proxy
ng serve --proxy-config ./proxy/proxy.conf.mjs -o

Warning: Running a server with --disable-host-check is a security risk. See https://medium.com/webpack/webpack-dev-server-middleware-security-issues-1489d950874a for more information.

• Generating browser application bundles (phase: setup)...C:\Users\bodl3227\PycharmProjects\customModule\node_modules\webpack\lib\container\ModuleFederationPlugin.js:58
  throw new TypeError(
  ^

TypeError: The 'compilation' argument must be an instance of Compilation
at ModuleFederationPlugin.getCompilationHooks (C:\Users\bodl3227\PycharmProjects\customModule\node_modules\webpack\lib\container\ModuleFederationPlugin.js:58:10)
at Hook.eval [as call] (eval at create (C:\Users\bodl3227\PycharmProjects\customModule\node_modules\tapable\lib\HookCodeFactory.js:19:10), :92:1)
at Hook.CALL_DELEGATE [as _call] (C:\Users\bodl3227\PycharmProjects\customModule\node_modules\tapable\lib\Hook.js:16:14)
at Compiler.newCompilation (C:\Users\bodl3227\PycharmProjects\customModule\node_modules@angular-devkit\build-angular\node_modules\webpack\lib\Compiler.js:1273:30)
at C:\Users\bodl3227\PycharmProjects\customModule\node_modules@angular-devkit\build-angular\node_modules\webpack\lib\Compiler.js:1318:29
at eval (eval at create (C:\Users\bodl3227\PycharmProjects\customModule\node_modules\tapable\lib\HookCodeFactory.js:31:10), :31:1)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

Node.js v22.21.1`

My package.json
package.json

Angular.json:
angular.json

[ShoulM]

My best guess it that you are experiencing a problem with multiple versions of webpack.
Take a look at this thread and see if some of the suggestions help:
https://stackoverflow.com/questions/67727180/the-compilation-argument-must-be-an-instance-of-compilation

[waynelam-bod]

An update for the issue and thanks to the message, i did manage to make the error message go away. As ShouIM has pointed out, it was related to an issue with webpack being reference twice as dependency. I tried with the "resolution" method in the link provided but that wasn't working for me. I eventually removed the follow 3 lines of webpack related dependency and managed to get it running again.

"webpack": "^5.88.2",
"webpack-cli": "^5.1.4",
"webpack-dev-server": "^4.15.1"

However, running it with npm update and npm audit, there is still 5 high vulnerability which I wasn't been able to get rid of. "npm audit fix" wasn't been able to fix it and "npm audit fix --force" upgrade Angular version to 21 which seems out of my scope since I would just want to fix the vulnerability issue and I wasn't completely sure if that is supported in Primo NDE at the moment.