hey alex, ive seen similar probs, solved it by rechecking my env settings and cleaning cache. sometimes the base url in angular.json gets misconfiged, causing merge issues. might be worth a look if youve not already done so.
hey alex im surprisd its actin weird. did u try usin a proxy settings file? maybe its a misconfig wit the base href or something else. what changes have u made lately?
I experienced a similar issue in one of my projects where the absence of a leading slash in the API endpoint led Angular to treat it as a relative path. The problem was rectified once I corrected the endpoint in the environment file by prefixing it with a slash, ensuring that it pointed correctly to the external API rather than appending to the base URL. Additionally, examining proxy configurations in the development server settings helped me understand how routing merges could occur, and adjusting those settings also provided a solution.
hey alex, maybe its a caching issue or a misconfigured base hre in your index.html? sometimes angular holds onto old env details accidently. did you try clearing both cli and browser caches? how does your proxy config look - any mismatch there?