Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

(foal CLI) TypeError: Cannot set property 'proxyConfig' of undefined

See original GitHub issue

Version of FoalTS: 2.5.0

Steps:

foal createapp portal
npm i -g @angular/cli
ng new portal-frontend
cd portal
foal connect angular …/portal-frontend

Error:

C:\Users\Luciano\Documents\GitHub\forjagames-portal\portal>foal connect angular ../portal-frontend
CREATE ..\portal-frontend\src\proxy.conf.json
UPDATE ..\portal-frontend\package.json
UPDATE ..\portal-frontend\angular.json
(node:5548) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'proxyConfig' of undefined
    at C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\lib\generate\generators\angular\connect-angular.js:38:84
    at FileSystem.modify (C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\lib\generate\file-system.js:245:46)
    at Object.connectAngular (C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\lib\generate\generators\angular\connect-angular.js:35:10)
    at Command.<anonymous> (C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\lib\index.js:67:24)
    at Command.listener [as _actionHandler] (C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\node_modules\commander\index.js:922:31)
    at Command._parseCommand (C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\node_modules\commander\index.js:1503:14)
    at Command._dispatchSubcommand (C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\node_modules\commander\index.js:1443:18)    
    at Command._parseCommand (C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\node_modules\commander\index.js:1460:12)
    at Command.parse (C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\node_modules\commander\index.js:1292:10)
    at Object.<anonymous> (C:\Users\Luciano\AppData\Roaming\npm\node_modules\@foal\cli\lib\index.js:152:9)
(node:5548) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:5548) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Issue Analytics

State:
Created 2 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

LoicPoullaincommented, Sep 7, 2021

Do you know when the version 2.6.0 will be published?

This week or next week.

I’m asking you this because I’m making a couple of videos about FoalTS, and I’m waiting for this feature to continue.

Oh glad to hear it! Feel free to share your videos on the awesome page when they’re published 👍

1reaction

LoicPoullaincommented, Sep 7, 2021

Fixed in v2.6.0

Top Results From Across the Web

Proxy configuration did not working with angular CLI

In Angular2 package.json I changed start procedure to "start": "ng serve --proxy-config proxy.config.json" When I type inside commander npm ...

AW: Problems Installing Flash SDK according to ...

Hi Micheal, well it seems that the download itself seems to be working, it even confirms that the artifacts are all installed successfully....

Untitled

Autobase co nz armstrong prestige, No te dejare ir salsa, Zhuo yao ji song, ... Cifrare messaggi, Bibenzyl physical properties, Good funeral home...

Untitled

#scenes Star dance center monterey park, Via dell'oceano indiano, Tameiki no gogo mangapark, Sim taxi 3d funny games, Office stationery online bangalore, ...