title: Using an auth-cookie when local server and SPA running on different ports
body: <p>I have a <code>nest.js</code> webserver listening on <code>localhost:3000</code> and an angular frontend served to <code>localhost:4200</code> (with dev server). These ports are the defaults. My authentication flow consists of sending an access-token in a cookie to the frontend which doesn't get send back on subsequent calls because of different domain issues by the different ports. Can I overcome this issue somehow? I understand that if I don't run <code>npm serve</code> for the angular application only <code>npm run build</code> then a development server won't be started and I can serve the static files with <code>nest.js</code> which would solve the domain issue for the cookie, but this way I would loose watch mode and hot reloading for angular. Any suggestions?</p>