"GETTING_STARTED.md" mismatch with the angular-cli@webpack

[lewgun]

Bug, feature request, or proposal:

bug

What is the expected behavior?

What is the current behavior?

there is no "angular-cli-build.js" file in a latest angular-cli new project. so please update this file to match it . it seems the pr #1002 does not working too

What are the steps to reproduce?

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd

What is the use-case or motivation for changing an existing behavior?

Which versions of Angular, Material, OS, browsers are affected?

angular: rc5
angular-cli: 1.0.0-beta.11-webpack.2
node: 5.12.0
os: darwin x64
material: ^2.0.0-alpha.7-2

Is there anything else we should know?

[Kosmonaft]

You can skip: Add components to vendor bundle andConfigure SystemJS from "GETTING_STARTED.md"
The only thing which I noticed is not working is Additional setup for md-menu and md-tooltip

Angular-cli webpack is just not creating a vendor for this. I don't have any idea how to fix this

[jelbourn]

@hansl can you make sure the getting started guide is good to go for alpha.8 + RC6 + webpack cli?

[jelbourn]

AFAIK the getting started should be totally up to date with angular-cli at this point.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}