Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Fresh project from analyze. The starter @api features all fail with HTML where JSON should be, and the reason is in the env file:
ui:
baseUrl: http://localhost:3000
api:
baseUrl: http://localhost:3000Our API is at /api on the same origin. I expected the /api suffix to be there. It is a Next app; the only Express in the repo is a small socket server in another package.
Accepted answer
That socket server is the cause.
Environment detection checks whether any manifest in scope depends on express. If one does, it runs a .listen() port heuristic to find the API origin, and when that heuristic finds nothing usable it falls back to http://localhost:3000 — which happens to be what ui already is. Crucially, taking that branch skips the default that would otherwise have set api to the UI base URL plus /api. So one unrelated package in the workspace changes the answer for the whole proposal.
Open issue. The fix on your side is one line per environment:
api:
baseUrl: http://localhost:3000/apiDo it before you write features, because the failure is downstream and confusing — the request succeeds, returns the app shell, and you get a JSON parse error or a schema mismatch rather than anything that points at configuration.
Quick check for anyone reading this later, run it right after --apply:
grep -n 'baseUrl' projects/<slug>/envs/*.yamlIf ui and api are byte-identical, you are in this bug. Ours was, and we have no Express at all in the app — it came in through a dev dependency of a tool package.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.