Andrew Walsh

I've changed the 'npm start' script as it shouldn't really use a process manager. Double check you're running both redis & postgresql as services. Alternatively, docker-compose will handle this for...

Thanks @karuppiah7890 - I've confirmed this bux and am working on a fix. It is related to newer versions of npm.

This was related to #https://github.com/npm/npm/issues/17708, the nested node_modules folder in socket.io-client was not being handled by NPM v5.0 correctly. The socket-io lib contained its own node_modules folder containing libraries which...

The `socket.io-client` module is included with the `socket.io` library. It is nested within this module's node_modules directory. I did mix it up a bit with this issue. This one is...

@ZackWard The new version of NPM threw a bit of a wrench into the works, a few issues appear to have emerged. Next week I'll do another fresh install on...

@joepin This is a feature that would be a very valuable addition, no question. I think we have a few other tasks prior to its implementation, but it's the next...

@karuppiah7890 @ishanjain28 Previously we ran the app with PM2 as a process manager. Our logging in this regard could do with improvement. My knowledge on devops is limited, particularly with...

Does this refer to the async work queue?

Hmm quite strange! Haven't seen this behaviour before. If you have any logs you could share that would be great, otherwise I will investigate this.

The filtering options are somewhat basic and haven't been tested too much, I've updated the associated react-bootstrap-table library. Perhaps options for filtering have been improved.