Have you attempted using this import? It successfully works for my use case

 import {Observation} from 'rxjs/Rx';
 import 'rxjs/add/operator/map';

Discovering a solution can be a team effort, and jjokela and VahidN's hints in the comments led me to a workaround that was also outlined in Deborah Kurata's blog post found here. The method she shared involved using Angular2 with an ASP.NET 4 project template, rather than the newer ASP.NET 5 RC template that I'm currently using.

To implement the fix, I followed the instructions provided at https://github.com/Microsoft/TypeScript/issues/8518#issuecomment-229506507

This particular solution is set to be included in the release of Typescript 2.0 for Visual Studio, but in the meantime, manual steps can be taken as outlined below.

For Visual Studio 2015 (Update 3):

- Install Visual Studio 2015 Update 3 - Backup the file at C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TypeScript\typescriptServices.js, then replace it with the one found at https://raw.githubusercontent.com/Microsoft/TypeScript/Fix8518-U3/lib/typescriptServices.js

For Visual Studio 2015 (Update 2):

- Install Visual Studio 2015 Update 2 - Backup the file at C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TypeScript\typescriptServices.js, then replace it with the one found at https://raw.githubusercontent.com/Microsoft/TypeScript/Fix8518/lib/typescriptServices.js

For Visual Studio 2013:

- Install TypeScript 1.8.5 from https://www.microsoft.com/en-us/download/details.aspx?id=48739 - Backup the file at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TypeScript\typescriptServices.js, then replace it with the one found at https://raw.githubusercontent.com/Microsoft/TypeScript/Fix8518-Dev12/lib/typescriptServices.js

After experiencing a similar problem, I found a solution by including the following code snippet within the AppComponent class.

import 'rxjs/Rx'; 

No other than

import { Observable } from 'rxjs/Rx';

The problem appears to be linked to an unresolved issue, as outlined in this GitHub thread. While a full Visual Studio release has not yet addressed this issue, it is possible to solve it by building the sources locally and utilizing Visual Studio Dev Mode.

Since upgrading to Angular2 RC, I've encountered the same issue. Visual Studio 2015 keeps showing Intellisense errors for the property 'map' not existing on type 'Observable'.

Even though I use grunt-ts for transpiling, the errors in the editor are frustrating, especially since they didn't appear before.

I suspect the problem lies with the download of Typescript for Visual Studio: https://www.microsoft.com/en-us/download/details.aspx?id=48593

The current version is 1.8.6 and it seems to influence both Visual Studio's Intellisense and the built-in Typescript compilation. We might just have to wait for a new version of Typescript for Visual Studio to be released.

Hey Dan, I encountered a bunch of issues when I introduced Observable into my code after upgrading to Angular 2 rc1. Adding the following line to my tsconfig.json file fixed the problem for me:

    "emitDecoratorMetadata": true,

After making this adjustment, everything rendered correctly whether I was deploying on IIS or using npm start. Here's my complete tsconfig.json configuration:

{"compilerOptions": {
"noEmitOnError": true,
"removeComments": false,
"sourceMap": true,
"target": "es5",
"experimentalDecorators": true,
"module": "commonjs",
"moduleResolution": "node",
"emitDecoratorMetadata": true,
"noImplicitAny": true,
"suppressImplicitAnyIndexErrors": true  },  
"exclude": [
"node_modules",
"typings/main",
"typings/main.d.ts"   
]}

(Apologies for the messy formatting, it's getting late). I hope this solution proves helpful to you.

When working with the toPromise.d.ts file, make sure to include the line "import {Observable} from '../../Observable';"

import { ToPromiseSignature } from '../../operator/toPromise';
import {Observable} from '../../Observable';
declare module '../../Observable' {
    interface Observable<T> {
        toPromise: ToPromiseSignature<T>;
    }
}

It's also important to apply the same changes to the map.d.ts file.

I hope this explanation helps clarify the process for you.

Your imports appear to be in good shape. The main issue causing the problem has been explained in detail at this GitHub link

To resolve this issue, it is recommended to update to the latest version of TypeScript 1.8.

Keep in mind that when you run tsc, you are using the global TypeScript installation (verify using tsc -v). To update the global TypeScript installation, run npm i typescript -g.

If you prefer to use the TypeScript version specified in your package.json, you must run it through the "scripts" section. For example, add "build": "tsc" to your scripts and run it with npm run build.

Experiencing the identical problem here. Using TypeScript version 1.8.11 with no luck finding a resolution. My suspicion is that the issue lies with either rxjs or angular 2 rc 1.

Managed to resolve the issue by reverting back to rxjs beta 2. However, this caused conflicts as angular rc1 relies on beta 6, resulting in a failed npm install.

import { Injectable } from '@angular/core';
import { Http, Response, Headers, RequestOptions} from '@angular/http';    
import 'rxjs/Rx';
import {Observable} from 'rxjs/Observable';
import 'rxjs/add/operator/map';

const fetchData = () => {
    return this._http.post(url, null, args).map(this.extractData)
}

Create a function called extractData

Give this code a try. It should work for you as it is currently working for me.

I managed to successfully implement this solution for the ag-grid Angular 2 component, which can be found here.

To make it work, I required the Promise typings which can be obtained by running: tsd install es6-shim

After that, in your TypeScript options, include the downloaded typings file as one of the files to compile in tsconfig.json, for example:

{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "removeComments": false,
    "noImplicitAny": false,
    "outDir": "lib"
  },
  "files": [
    "typings/es6-shim/es6-shim.d.ts", // the typings file
    "app/boot.ts" // your application
  ]
}

Resolving the issue for me involved installing the typings for es6-shim in this manner:

typings i es6-shim --ambient --save-dev

I encountered a similar issue due to a breaking change in beta 6. To work around this issue, referencing the internal typings files within angular was a temporary solution. However, these internal typings files were removed in version 2.0.0-rc.0, necessitating the use of external typings for the same purpose.

For those who have recently upgraded to Angular2 rc1, it's important to use the new @angular import statements instead of using the old angular2 syntax:

`import { Component } from 'angular2/core';`

The correct way is:

`import { Component } from '@angular/core';`

It may seem like a small change, but failing to do so can lead to issues.

Locate the beta version 2.0.0 of TypeScript designed specifically for use with Visual Studio 2015. I found that this release successfully addressed a particular issue I was encountering on my own device. It is important to note, however, that this is still a beta version.

When transitioning from an early Angular2 release-candidate (such as 2.0.0-rc.1) to a 2.x.x release, make sure to follow these steps:

1. Ensure your package.json is updated by referring to the one at https://github.com/angular/quickstart/blob/master/package.json

2. Check that your systemjs.config.js file matches the one at https://github.com/angular/quickstart/blob/master/systemjs.config.js

3. Adjust the import statement to:

   import {Observable} from 'rxjs'