-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Comments
I experienced the same issue. I think this pr fixed it. Thanks |
Getting the same error as everyone else: Angular CLI beta 30 with Angular 2.4.6 |
+1 |
+( |
+1 |
2 similar comments
+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 similar comment
+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 |
@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? |
+1 |
Reinstall everything (node, npm, Angular, Angular-cli, Typescript, etc...) and .....
|
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 Same problem |
Do this as suggested by omachala: npm uninstall -g angular-cli @angular/cli |
In my case, I need
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
Versions.
Repro steps.
The log given by the failure.
Mention any other details that might be useful.
The project seems to work correctly.
The text was updated successfully, but these errors were encountered: