micahstubbs commented on issue #2053:
URL: https://github.com/apache/helix/issues/2053#issuecomment-1120448897

   `npm` start doesn't recognize our proxy config anymore, after migrating to 
the new `angular.json` config format. 
   
   ```py
   [nodemon] starting `node dist/server/app.js`
   App is listening on port 3000 as HTTP
   Configuration './proxy.conf.json' could not be found in project 
'helix-front'.
   Error: Configuration './proxy.conf.json' could not be found in project 
'helix-front'.
       at Architect.getBuilderConfiguration 
(/helix/helix-front/node_modules/@angular-devkit/architect/src/architect.js:106:23)
       at 
MergeMapSubscriber._loadWorkspaceAndArchitect.pipe.operators_1.concatMap [as 
project] 
(/helix/helix-front/node_modules/@angular/cli/models/architect-command.js:70:55)
       at MergeMapSubscriber._tryNext 
(/helix/helix-front/node_modules/@angular/cli/node_modules/rxjs/internal/operators/mergeMap.js:65:27)
       at MergeMapSubscriber._next 
(/helix/helix-front/node_modules/@angular/cli/node_modules/rxjs/internal/operators/mergeMap.js:55:18)
       at MergeMapSubscriber.Subscriber.next 
(/helix/helix-front/node_modules/@angular/cli/node_modules/rxjs/internal/Subscriber.js:64:18)
       at TapSubscriber._next 
(/helix/helix-front/node_modules/@angular/cli/node_modules/rxjs/internal/operators/tap.js:62:26)
       at TapSubscriber.Subscriber.next 
(/helix/helix-front/node_modules/@angular/cli/node_modules/rxjs/internal/Subscriber.js:64:18)
       at MergeMapSubscriber.notifyNext 
(/helix/helix-front/node_modules/@angular/cli/node_modules/rxjs/internal/operators/mergeMap.js:84:26)
       at InnerSubscriber._next 
(/helix/helix-front/node_modules/@angular/cli/node_modules/rxjs/internal/InnerSubscriber.js:25:21)
       at InnerSubscriber.Subscriber.next 
(/helix/helix-front/node_modules/@angular/cli/node_modules/rxjs/internal/Subscriber.js:64:18)
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to