angular / angular-cli

CLI tool for Angular
https://cli.angular.io
MIT License
26.76k stars 11.98k forks source link

Error: dryRunSink.commit(...).ignoreElements(...).concat is not a function #9194

Closed rilwans closed 6 years ago

rilwans commented 6 years ago

Just Upgraded to Angular CLI: 1.6.4

each time I run ng new I get this error

Error: dryRunSink.commit(...).ignoreElements(...).concat is not a function dryRunSink.commit(...).ignoreElements(...).concat is not a function

hugocaldeira commented 6 years ago

@Brocco problem solved! Thank you!

LunoDaniel commented 6 years ago

Thank you @gurgelv, that's works fine for me.

CarMoreno commented 6 years ago

@gurgelv You're a Rockstar!, thank you

nyoman commented 6 years ago

I had the same problem. But this (npm install @angular-devkit/schematics@0.0.45 @angular/cli --no-save) solved my problem.

My big thanks go to Mendhak.

Sharkesm commented 6 years ago

I had the same problem but not quite sure if it might work for the rest of you guys, but essentially i deleted node_module folder then uninstalled @angular/cli and re-install it once again but with higher version and finally updated the current node.

Herotko commented 6 years ago

I was helped

"@angular-devkit/ сore": "^0.6.8",
"@angular-devkit/ schematics": "^0.6.8",
"@angular/cli": "^1.7.4",
"@angular/compiler-cli": "^5.1.1",
zshlomyz commented 6 years ago

We the "CLI Team" would like to apologize for the confusion.

Status

This issue has been resolved in version 1.6.6.

Updating

The steps to update your environment to the latest version containing the fix:

npm uninstall -g @angular/cli
npm cache clean
# if npm version is > 5 then use `npm cache verify` to avoid errors (or to avoid using --force)
npm install -g @angular/cli@latest

rm -rf node_modules dist # use rmdir /S/Q node_modules dist in Windows Command Prompt; use rm -r -fo node_modules,dist in Windows PowerShell
npm install --save-dev @angular/cli@latest
npm install

Explanation

The issue of [rxjs operator] is not a function is a result of the migration of the devkit repo to using "pipeable" (formerly "lettable") operators instead of the prototype patching approach that the Angular CLI was using prior to release 1.6.6 (which was just released). The commit which fixed it is here.

The issue is that the CLI was using operators that were not imported and relied on them being on the Observable object. When the devkit was updated it removed this function and the bug in the CLI was exposed. The latest version of the CLI is now using pipeable operators and therefore importing all of the operators needed to work with observables, so this issue has been resolved.

Thank you for your patience and for contributing by reporting this issue.

Hi, The suggested version 1.6.6 is compatible with Angular 5? If no, there is a different version that is compatible & work properly? Regards

angular-automatic-lock-bot[bot] commented 5 years ago

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.