Failure to auto-detect nested CMS installation?

[jacksonrya]

My ContentaCMS is nested (localhost:MAMP-PORT/contenta/web), installed via contenta_jsonapi_project. When writing ContentaJS local config, 'cms.host' requires a complete path to the ContentaCMS to get any type of connection to the node proxy, otherwise connections are refused.

While the app is accepting connections, requests sent to the node proxy api (localhost:NODE-PORT/api) get a 404 response in HTML:
...<pre>Cannot GET /api</pre>...

Direct requests to ContentaCMS API work perfectly.

I've started to go through the built code, but haven't had much luck in finding a solution.

Suggestions?

[jacksonrya]

Debugging has proved that fetching CMS meta works just fine with nested CMS. Will create a new issue if I can't figure it out why I keep a 404 response.