Issue 1:
I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request

Current behavior

ngc doesn't work. If I run ngc, I then get the response:

C:\Users\George\Source\Repos\docs>ngc
module.js:457
throw err;
^

Error: Cannot find module '@angular/compiler'
at Function.Module._resolveFilename (module.js:455:15)
at Function.Module._load (module.js:403:25)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (C:\Users\George\AppData\Roaming\nvm\v6.7.0\node_modules\@angular\compiler-cli\src\codegen.js:13:16)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)

Expected behavior

ngc to work as described in the docs.

Minimal reproduction of the problem with instructions

I assume this is something with my system, but:

npm install @angular/compiler-cli typescript@next @angular/platform-server @angular/compiler

ngc (in same dir as above)

What is the motivation / use case for changing the behavior?

Use AOT compilation

Please tell us about your environment:

Windows 10 Pro, Command Prompt, npm

Angular version: 2.0.2

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

Node (for AoT issues): node --version = 6.7.0 (x64)

Issue 2:
Version Alpha 46, TS

When trying to learn the various ways of working with forms I ran into an odd issue where select elements trigger change events twice for the same change when subscribed to the valueChanges observable.

If I have a function that changes the value from the model it only fires the change event once as expected.

It's pretty short so heres my code:

@Component({
selector: 'my-app',
})
@View({
template: `
<h3>Simple Select on App Component</h3>
<form>
<select [ng-form-control]="simpleSelect">
<option value="1">One</option>
<option value="2">Two</option>
<option value="3">Three</option>
</select>
<button type="button" (click)="changeSelect()">Change Select to 3 From Model</button>
</form>
`,
directives: [FORM_DIRECTIVES]

})
export class App {
simpleSelect: Control = new Control('');
counter: number = 0;
constructor() {
//watch simple select
this.simpleSelect.valueChanges.subscribe((value)=>{
console.log("Simple Select Val:" + value + " and counter:"+this.counter)
this.counter++;
});
};
changeSelect() {
this.simpleSelect.updateValue(3);
}
}

And Here is a Plunker of this in action.

I thought maybe it was something with how simple I was interfacing it so I did it with the FormBuilder and got the same results. I added a text field to see how it's changes effect the form and they work correctly (only fire once)

That Plunker Here

I'm not sure if I'm doing something incorrectly, but I think the expected behavior is the event to fire only once. I'm not experienced enough to track back whats causing the double bindings so I hoped I could have someone take a look at it...