grunt-connect seems to stop generated routes from working

[wakandan]

trafficstars

While the web server can start and run after grunt server, accessing a model via generated routes will yield 404. Does anyone else also have this issue like me, or I'm configuring something wrongly? I was working on a fresh instance of this generator btw. I already got a fix for this which replaces grunt-connect with grunt-concurrent and grunt-nodemon, just need to verify it's a real issue. Thanks

[rayokota]

Which version of node are you using?

[wakandan]

I'm using the latest version of node. Also, when doing grunt server, there doesn't seem to be any log running into my console. Not sure while, but it could mean that either 1) the server might not be actually running, or 2) the plugin is oppressing the logs from the node sever. If it happens either way I think it's worth replacing.