ngx-socket-io | Socket.IO module for Angular

Since IoRequestService is annotated with @Injectable() you need to inject its instance in your component:

Well after hours of scanning through GitHub, stack-overflow and all other various results from searching @ngtools/webpack/src/ivy/plugin.js I found one result of someone who may have a similar issue as me... However, this is probably a stretch because his seemed to be triggering only on his/her local machine and only upon running npm audit fix (Errors after npm audit fix angular 10.0.1). This is a very recent post, so I am assuming it must be a recent package issue or dependancy clash, most likely to do with @ngtools/webpack & @angular/compiler. However this is kind of a guess based on the logs, but upon looking into my local machine the file complained about node_modules/@ngtools/webpack/src/ivy/plugin.js did not exist yet built perfectly. So after hours or removing, updating and downgrading various packages, deleting my node_modules and rebuilding my package-lock.json file nothing seemed to work yet all the while it worked perfectly on my machine no matter what package.json changes I made. So I turned to my buildspec.yml and miraculously after trial and error resolved the build issue. Here is my working buildspec:

It was the firewall. The port 3000 was not open.

Thanks @ZabojCampula

I am going to attach some working code as promised, but I might have just noticed something... The error message mentions port 3000 and ALSO port 4200, it looks like your socket is open on port 3000, so I wonder if you could track down where the 4200 is coming from?

In reply to your comment: I believe that Socket.IO is used to connect Client <-> Server. So there may be an issue with your configuration. Are you sure you want different ports? as you mentioned you want 2 servers, but my guess would be you really want 1 port and 1 server, running 1 app that has Client <-> Server communication?
Anyways if I am off there, it may just be possible because of the different ports / servers that the CORS error is actually valid here and you'd have to figure out how to add CORS headers to your web server:

Example:

You are initiating a new subscription each time the listFormData function is called. Instead you could subscribe in the ngOnInit() hook once.

Messages is in the beginning an array, but then I see this line:

Solved it by using the service version instead of registering SocketIoModule in AppModule as per documentation in npm.

I found the problem. In my case, the firewall of my pc doesn't allow any other device on local network connect to the server. When I turned off the firewall the connection between client-server was established!

You could try to disconnect using