Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Configure a Proxy for Your API Calls With Angular CLI [Video]

DZone's Guide to

Configure a Proxy for Your API Calls With Angular CLI [Video]

Check out this video to learn how to configure the Angular CLI to proxy your API calls to your backend server.

· Web Dev Zone
Free Resource

Get deep insight into Node.js applications with real-time metrics, CPU profiling, and heap snapshots with N|Solid from NodeSource. Learn more.

In this video we will learn and demonstrate how to configure the Angular CLI to proxy your API calls to your backend server.

During development, you often end up in the situation where you have your backend API server running at one address (i.e. localhost:3000) while your frontend development server runs on another (i.e. localhost:4200). However, in your Angular 2 services that query the backend API, you don’t obviously want to hard-code the development server’s host, but instead, write your calls as follows:


this.http.get('/api/v1/people')
    .map(res => res.json());


Clearly, this won’t probably work out of the box, because the Angular CLI development server doesn’t answer at /api/v1/people with an API. This is why you need to have some kind of proxy that intercepts such calls and proxies them to your correct backend server API. Let’s learn how to setup such proxy with the Angular CLI.


You didn’t yet have the chance to create an Angular 2 application, but you’re eager to learn it? Watch my introductory video which learns you how to build your first Angular 2 application using the Angular CLI in under one hour.

Node.js application metrics sent directly to any statsd-compliant system. Get N|Solid

Topics:
cli ,proxy ,backend ,api ,angular ,web dev

Published at DZone with permission of Juri Strumpflohner. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}