Angular build fails
See original GitHub issueType of Issue
[X] Bug Report
[ ] Feature Request
Description
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'dist'
1 verbose cli ]
2 info using npm@6.14.13
3 info using node@v14.17.0
4 verbose run-script [ 'predist', 'dist', 'postdist' ]
5 info lifecycle bizdoc.core@1.4.3~predist: bizdoc.core@1.4.3
6 info lifecycle bizdoc.core@1.4.3~dist: bizdoc.core@1.4.3
7 verbose lifecycle bizdoc.core@1.4.3~dist: unsafe-perm in lifecycle true
8 verbose lifecycle bizdoc.core@1.4.3~dist: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;...
9 verbose lifecycle bizdoc.core@1.4.3~dist: CWD: C:\...\Angular\ClientApp
10 silly lifecycle bizdoc.core@1.4.3~dist: Args: [
10 silly lifecycle '/d /s /c',
10 silly lifecycle 'npm run packagr && npm run copy-themes && npm run copy-assets && npm run publish'
10 silly lifecycle ]
11 silly lifecycle bizdoc.core@1.4.3~dist: Returned: code: 1 signal: null
12 info lifecycle bizdoc.core@1.4.3~dist: Failed to exec dist script
13 verbose stack Error: bizdoc.core@1.4.3 dist: `npm run packagr && npm run copy-themes && npm run copy-assets && npm run publish`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:376:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:376:20)
13 verbose stack at maybeClose (internal/child_process.js:1055:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid bizdoc.core@1.4.3
15 verbose cwd C:\Users\barak\source\repos\BizDoc.Core\Angular\ClientApp
16 verbose Windows_NT 10.0.19042
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "dist"
18 verbose node v14.17.0
19 verbose npm v6.14.13
20 error code ELIFECYCLE
21 error errno 1
22 error bizdoc.core@1.4.3 dist: `npm run packagr && npm run copy-themes && npm run copy-assets && npm run publish`
22 error Exit status 1
23 error Failed at the bizdoc.core@1.4.3 dist script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
HowTo Reproduce
npm run packagr
Output “Compiling with Angular in legacy View Engine compilation mode.”
Produces Maximum call stack size exceeded.
Version Information
ng-packagr: 12.2.0-next.0
@angular/compiler: 12.1.4
rollup: 2.55.1
typescript: 4.3.5
Issue Analytics
- State:
- Created 2 years ago
- Comments:17 (7 by maintainers)
Top Results From Across the Web
Identify and Fix Build and Deployment Errors in Your Angular ...
In this guide, you will learn how to spot some of the most common build and deployment errors and how to resolve them...
Read more >Angular build for production fails - Stack Overflow
When I try to build for production my angular application with the following command ng build --prod --build-optimizer I get the following ...
Read more >Angular 12.2 ng build fails with NOENT esbuild.exe error
I had a working application running angular 12.1.1 and just updated angular to 12.2.4 and received a NOENT error attempting to delete an...
Read more >Angular CLI ng build fails - Visual Studio Feedback
I have been trying to get a dotnet core 2.0, Angular CLI 1.5.0 & Angular 5.0.0 ... followed by an npm task with...
Read more >Pages deployment for Angular, Build Fails
Hello,. I am having some issues trying to deploy my Angular application. The build is failing each time I try to deploy.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve reagraned my code as @SchnWalter suggested and used
npm publish
rather than calling ng-packagr directly and now it works!Can you confirm you’re capacity in this forum?