- This topic has 14 replies, 3 voices, and was last updated 4 years, 6 months ago by beleta1.
-
AuthorPosts
-
beleta1ParticipantIn a project that uses @angulat/cli 8.3.21 I am getting the following error “Port xxxx is already in use” when running
ng serve
inside Terminal+, no matter which port I try using--port xxxx
.When using the same
ng serve
command on and OS terminal outside Eclipse things go well.Perhaps a problem with angular-ide?
beleta1ParticipantIf I use:
node_modules/.bin/ng serve
instead of simply
ng serve
things go with no problem.
support-swapnaModeratorbeleta1,
Sorry that you are seeing this issue. I could replicate the problem at my end with
ng serve
The app starts fine from the Servers view. When you start the app from the Servers view, you will see command similar to this one :'node_modules/angular-ide/bin/ng' 'serve' --port=4200 --live-reload=true --webclipse-launch-id=891829734499754220
Theangular-ide
in the above command is our module. If you typeng serve
from the Terminal+, then it comes from angular-cli.I will file a bug report for the dev team to look into this problem. We will get back to you soon with our findings.
Thank you for reporting this issue.Apologies for inconvenience caused.
–Swapna
Genuitec Support
Salvador CabreraMemberHi beleta1,
We have pushed a new version of the angular-ide npm module that should fix this problem.
You can run:npm i angular-ide@0.9.71
in a project’s Terminal+ tab to get the fix.Please let us know how it goes!
Cheers,
Sal
beleta1ParticipantYes Sal, that fixed the problem. Thank you for your support and fast response.
Regards
Jose Maria
beleta1ParticipantHi Sal,
The problem showed again, this time with angular-ide@0.9.72 and @angular/cli@8.3.24.
Regards
Jose Maria
Salvador CabreraMemberHi Jose Maria,
Odd, anyway, i’ll take a look at it, will let you know when we have a fix.
Cheers,
Sal- This reply was modified 4 years, 8 months ago by Salvador Cabrera.
Salvador CabreraMemberHi Jose Maria,
We have pushed a fix for this issue.
As usual, you can try it by updating to the latest angular-ide version:npm i angular-ide@latest
in the project’s Terminal+ tab to get the fix.Best Regards,
Sal
beleta1ParticipantUnfortunately the fix angular-ide@0.9.73 does not work.
JM
support-swapnaModeratorJose,
Sorry that you are still seeing the issue.
I see no issues runningangular-ide@0.9.73
app withng serve
at my end.1. Can you please recheck if there is any other app already running on the specified port?
2. Does specifying a different port viang serve --port xxxx
also throw the same error?
3. Please create a fresh project and check if the issue persists.–Swapna
Genuitec Support
beleta1ParticipantAs you can infer from my other post in this thread, I checked several times that no port was in use before reporting the problem. No, the issue still exists. Furthermore, as I already said, executing
node_modules/.bin/ng serve
serves the program with no problem.Clearly the problem is on your angular-ide.
I am including my package.json if it can enlighten you in finding a solution.
- This reply was modified 4 years, 7 months ago by beleta1.
- This reply was modified 4 years, 7 months ago by beleta1.
Attachments:
You must be logged in to view attached files.
support-swapnaModeratorHi,
Thank you for sharing the package.json.
I removed the carver-login and carver-validator dependencies as they are throwing 404 errors and with the other dependencies, I see no issues with ng serve.1. If you delete the node_modules folder and run ‘npm install’ again, does it help?
2. Can you please clarify if you see the issue with a newly created project as well (please dont add the additional dependencies, just accept the defaults)? If yes, then please share the entire output of the ‘ng serve’ command.
Apologies for inconvenience caused.
–Swapna
Genuitec Support
support-swapnaModeratorJose,
Our latest CodeMix release, CI 2020.2.25 is out. Please go to Help > Check for Updates and update to it.
Let us know if you are still seeing the ‘Port already in use’ error.–Swapna
Genuitec Support
Salvador CabreraMemberHi beleta1,
In case you’re still seeing this problem, try updating to the latest
angular-ide
npm package version which contains several fixes (including one that might fix this one)Let us know how it goes.
Cheers,
Sal
beleta1ParticipantYes, it works now.
Thank you Sal.
Jose
-
AuthorPosts