fallbackLoader option has been deprecated - replace with "fallback" loader option has been deprecated - replace with "use"

[beeman]

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

• macOS Sierra
• Ubuntu 16.04.1 LTS (clean machine)

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

@angular/cli: 1.0.0-beta.30
node: 7.5.0
os: darwin x64
@angular/common: 2.4.6
@angular/compiler: 2.4.6
@angular/core: 2.4.6
@angular/forms: 2.4.6
@angular/http: 2.4.6
@angular/platform-browser: 2.4.6
@angular/platform-browser-dynamic: 2.4.6
@angular/router: 3.4.6
@angular/cli: 1.0.0-beta.30
@angular/compiler-cli: 2.4.6

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

$ ng new fallbackloader
$ cd fallbackloader
$ ng serve

The log given by the failure.

Normally this include a stack trace and some more information.

fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
** NG Live Development Server is running on http://localhost:4200. **

Mention any other details that might be useful.

The project seems to work correctly.

---

Thanks! We'll be in touch soon.

[mattma]

I experienced the same issue. I think this pr fixed it. Thanks

[shakhrillo]

I'm using windows 7 and everything is up to date. But still warn is giving. Could you help?

[bjornharvold]

Getting the same error as everyone else: Angular CLI beta 30 with Angular 2.4.6

[MatGhp]

+1

[StrontsitskiyVolodymyr]

+(

[Kozlo]

+1

[techiezia]

+1

[MeMeMax]

+1

[beeman]

There's no need to +1 the issue, the problem is confirmed and the fix is in place and will ship with the next release.

I don't know when that next release is but I expect it to be soon as there are more issues that need a fix.

[beeman]

https://twitter.com/hanslatwork/status/829570400384278528

It looks like there will be a new beta today :)

[bertolo1988]

+1

[ccabanero]

+1

[intellix]

There's no need to +1 guys, it just causes unnecessary notifications. That's why Github added reactions: https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments