I'm following the document on single-spa for angular. My angular version is 11+. I followed the steps from
https://single-spa.js.org/docs/ecosystem-angular/#angular-cli through https://single-spa.js.org/docs/ecosystem-angular/#finish-installation successfully.
But as subsequent step when I complete https://single-spa.js.org/docs/ecosystem-angular/#configure-routes
and run the script at https://single-spa.js.org/docs/ecosystem-angular/#serving at npm run serve:single-spa (npm run serve:single-spa:my-app) actually,
I get the following error:
Can anyone point out why this may be occuring and what's the remedy for this ?
This is the relevant log file

Asked
Active
Viewed 1.9k times
14
Arvind Maurya
- 910
- 12
- 25
Syed Abrar Jaleel
- 141
- 1
- 1
- 4
4 Answers
13
You probably just forgot to run npm install before running your application. This was the problem in my case.
Another solution you can try is to delete package-lock.json then npm install again if you already have the node modules installed.
James Ikubi
- 2,552
- 25
- 18
9
Did you try: "npm i -D @angular-builders/custom-webpack" in your SPA directory?
reference: https://www.npmjs.com/package/@angular-builders/custom-webpack
(Worked for me).
Jeffrey Brewster
- 141
- 3
1
- Go to the package.json file.
- add "@angular-builders/custom-webpack": "^12.0.0"
- to find the latest version of @angular-builders/custom-webpack go this link https://www.npmjs.com/package/@angular-builders/custom-webpack?activeTab=versions and pick the latest version.
- then npm install again
Daniyal Ali
- 11
- 1
0
For me it was "builderS" (what it should be) vs "builder" (what I had) which I incorrectly typed into my angular.json
jameseg
- 730
- 1
- 4
- 19