René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support either proxy-conf or use ssr entrypoint for @angular-devkit/build-angular:dev-server","articleBody":"### Command\n\nserve\n\n### Description\n\nI have a project using @angular-devkit/build-angular:application as executor. \r\nThis project has SSR enabled, via `ssr: { entry: 'path/to/file' }` and `server: path-to-main.server.ts`\r\n\r\nWhen i run `nx serve` it detects that i have SSR enabled, and helpfully starts the server side rendering, by bootstrapping the thing from `server` path (not the thing from `ssr.entry`)\r\n\r\nI have an external api, that is usually mapped via proxyConf, but this seems not to take effect. Ie the client side requests for /api/ does not get proxied, but rather the requests get sent to the SSR part which then just renders index.html\r\n\r\nAnd since its not using the ssr-entry point to run this server, i cant add, say, an express-proxy to the configuration.\n\n### Describe the solution you'd like\n\nI'd like to be able to proxy calls to third party, for browser side calls, on projects that use  build-angular:application and build-angular:dev-server\r\n\r\n\n\n### Describe alternatives you've considered\n\nI can inject the true host names for third party service, from server side variables into client side, but this adds CORS overhead and management issues during normal development.","author":{"url":"https://github.com/asgerjensen","@type":"Person","name":"asgerjensen"},"datePublished":"2024-02-22T11:21:45Z","url":"https://github.com/angular/angular-cli/issues/27144"}