Please provide us with the following information:
Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
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
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
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. **
The project seems to work correctly.
Thanks! We'll be in touch soon.
I experienced the same issue. I think this pr fixed it. Thanks
I'm using windows 7 and everything is up to date. But still warn is giving. Could you help?
Getting the same error as everyone else: Angular CLI beta 30 with Angular 2.4.6
+1
+(
+1
+1
+1
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.
https://twitter.com/hanslatwork/status/829570400384278528
It looks like there will be a new beta today :)
+1
+1
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
+1
Confirmed. The latest Beta.31 works great and this bug has been squashed.
npm uninstall -g angular-cli @angular/cli
npm cache clean
npm install -g @angular/cli@latest
@omachala having errors starting ng serve after the 3 steps
@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?
after running the 3 steps i say ng serve and i get this
+1
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
Same problem
same problem. Additional ng new PROJECT_NAME create project into my Users directory and not in the folder where i run ng new.
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"
Do this as suggested by omachala:
npm uninstall -g angular-cli @angular/cli
npm cache clean
npm install -g @angular/cli@latest
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
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._
Most helpful comment
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