Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
beeman opened this issue Feb 4, 2017 · 27 comments · Fixed by #4435

Comments

@beeman
Copy link
Contributor

beeman commented Feb 4, 2017

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
Copy link

mattma commented Feb 5, 2017

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

@shakhrillo
Copy link

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

@bjornharvold
Copy link

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

@MatGhp
Copy link

MatGhp commented Feb 9, 2017

+1

@StrontsitskiyVolodymyr
Copy link

+(

@Kozlo
Copy link

Kozlo commented Feb 9, 2017

+1

2 similar comments
@techiezia
Copy link

+1

@MeMeMax
Copy link

MeMeMax commented Feb 9, 2017

+1

@beeman
Copy link
Contributor Author

beeman commented Feb 9, 2017

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
Copy link
Contributor Author

beeman commented Feb 9, 2017

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

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

@bertolo1988
Copy link

+1

1 similar comment
@ccabanero
Copy link

+1

@intellix
Copy link
Contributor

intellix commented Feb 9, 2017

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

@marcusvy
Copy link

marcusvy commented Feb 9, 2017

+1

@mattma
Copy link

mattma commented Feb 10, 2017

Confirmed. The latest Beta.31 works great and this bug has been squashed.

@omachala
Copy link

npm uninstall -g angular-cli @angular/cli
npm cache clean
npm install -g @angular/cli@latest

@niilante
Copy link

@omachala having errors starting ng serve after the 3 steps

@omachala
Copy link

@niilante tested for now project (ng new + ng serve) and this fixed 'fallbackLoader option has been deprecated' and worked fine. What errors do you see?

@shy001
Copy link

shy001 commented Mar 8, 2017

image
after running the 3 steps i say ng serve and i get this

@jmxt3
Copy link

jmxt3 commented Mar 25, 2017

+1

@aucevica
Copy link

Reinstall everything (node, npm, Angular, Angular-cli, Typescript, etc...) and .....
fallbackLoader option has been deprecated - replace with "fallback"

ng -v
@angular/cli: 1.0.0
node: 6.9.4
os: win32 x64
npm -v
4.5.0
rmdir node_modules
npm install
npm start

@daryn-k
Copy link

daryn-k commented Jun 24, 2017

Same problem

@moohkooh
Copy link

moohkooh commented Jun 25, 2017

same problem. Additional ng new PROJECT_NAME create project into my Users directory and not in the folder where i run ng new.

@hithto
Copy link

hithto commented Oct 25, 2017

angular-cli: 1.0.0-beta.28.3
node: 8.6.0
os: win32 x64

Same problem
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"

@MeMeMax
Copy link

MeMeMax commented Oct 25, 2017

Do this as suggested by omachala:

npm uninstall -g angular-cli @angular/cli
npm cache clean
npm install -g @angular/cli@latest

@micksatana
Copy link

In my case, I need npm cache verify instead of npm cache clean

npm uninstall -g angular-cli @angular/cli
npm cache verify
npm install -g @angular/cli@latest

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.