I encountered a surprising error while using the Azure Build pipeline, specifically in the loadrunner.js file. The error message from the pipeline is: "The callback was already called".
C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" run build:prod"
D:\a\31\s\node_modules\loader-runner\lib\LoaderRunner.js:106
throw new Error("callback(): The callback was already called.");
^
Error: callback(): The callback was already called.
at context.callback (D:\a\31\s\node_modules\loader-runner\lib\LoaderRunner.js:106:10)
at D:\a\31\s\node_modules\css-loader\dist\index.js:137:5
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
I successfully built the same code on January 31, 2023 without any errors. However, during the production push, this issue surfaced. I have been trying to troubleshoot and find a solution since then.
Here is a screenshot for reference:
https://i.stack.imgur.com/VPCVc.png
In my attempts to resolve the issue, I upgraded the bootstrap version to 5.0 and above. While this allowed the build to succeed, it caused issues with the UI. My Angular version is 9.2.X, and the bootstrap version specified in my package.json is ^3.4.1.
Another user has reported a similar loadrunner issue on Stack Overflow, but the suggested solution did not work for me.
I am concerned about the Bootstrap ^3.4.1 library, as it has been heavily downloaded from the nodejs website in recent days. Could there be an issue with this particular version?
Note that although upgrading Angular resolved the problem, it is currently not a viable option for me. What other solutions can I explore?
Additionally, here are the details of the pipeline configuration (All jobs include custom commands):
Cache Clean:- Task Version 1.*, command: cache clean --force
Npm update:- Task Version 1.*, command: update --force
Npm install:- Task Version 1.*, command: install --legacy-peer-deps --force
Npm build:- Task Version 1.*, command: run build:ps
It's worth noting that our angular version was upgraded from 6 to 9, leading to the inclusion of the npm update command in the pipeline.
The pipeline successfully completes all steps but encounters a failure during npm build.