angular-cli 🚀 - Error: dryRunSink.commit(...).ignoreElements(...).concat is not a function

same, just installed the cli and getting the same error.
[Update]
Tried a couple of versions

Angular CLI: 1.7.0-beta.0
Node: 9.4.0
OS: darwin x64
Angular:
----
Angular CLI: 1.6.0
Node: 9.4.0
OS: darwin x64
Angular:
----
Angular CLI: 1.6.3
Node: 9.4.0
OS: darwin x64
Angular:

With the same result

alexsapran on 12 Jan 2018

I am getting this error, too.

Angular CLI: 1.6.4
Node: 7.10.0
OS: linux x64
Angular:
...

GeorgeDunee on 12 Jan 2018

Me too
Angular cli: 1.6.4
Node: 8.8.1
OS: Windows 10

j-c-levin on 12 Jan 2018

Same error,
Angular CLI: 1.6.4
Node: 8.9.4
OS: win32 x64

fhnaseer on 12 Jan 2018

👍2

Same Error:
Angular CLI: 1.6.4
Node: 9.4.0
OS: linux x64
npm --version: 5.6.0

nilsfriess on 12 Jan 2018

oh my god ! i am having the same problem !
in addition now ! i re down graded to my working version 1.5.3 , that was working all the time perfectly, and still ! i receive the same error ! nothing is fixing my problem !!! HELP NEEDED

anankassis on 12 Jan 2018

👎4

I can offer no help. But I have deep sympathy as I see the same problem.

derobiom on 12 Jan 2018

😄23

Following this worked -

npm install @angular-devkit/[email protected] @angular/cli --no-save
$(npm bin)/ng new my-new-app

mendhak on 12 Jan 2018

👍45 ❤13 🎉12 😄5

https://github.com/angular/devkit/commit/e1f435606ffcf29b3311ab7204ef3eb84d661be2#diff-0dfbc02885bfb31a1e86e72520aad335

This is the commit in the schematics.ts file in the package @angular-devkit/schematics which is causing the problem

As this is just some refactoring, maybe it would be best to just go back.
See this issue on the devkit github: https://github.com/angular/devkit/issues/380

nilsfriess on 12 Jan 2018

👍4

See @maymarx answer in https://github.com/angular/devkit/issues/380:

adding
"@angular-devkit/schematics":"0.0.42", "@angular-devkit/core": "0.0.23", to the package.json fixes the problems if you need a quick fix before the weekend

nilsfriess on 12 Jan 2018

👍18 🎉5 😄2

Same issue here too guys and gals!

slick-k on 12 Jan 2018

Adding
"@angular-devkit/schematics":"0.0.42", "@angular-devkit/core": "0.0.23", to the package.json (dev dependencies) worked for me also.

derobiom on 12 Jan 2018

👍1

how you add those things you talked about ?!
exactly ???
like what to add ?? just "":"0.0.42", "": "0.0.23" ???

anankassis on 12 Jan 2018

👍3

i have the same issue, after adding "@angular-devkit/schematics":"0.0.42", "@angular-devkit/core": "0.0.23", to the package.json, i uninstalled angular cli and re installed it, but the same issue pops up

iamviswajith on 12 Jan 2018

they are dependencies which can be added to the package.json of your project, and no "":"0.0.42", "": "0.0.23" is not enough. you need the full dependency names:
"@angular-devkit/schematics":"0.0.42", "@angular-devkit/core": "0.0.23"

In my case, I had no project to add these dependencies to (creating a new one now), so I had to follow @eclanrs's solution at https://github.com/angular/devkit/issues/380:

npm i @angular-devkit/[email protected] @angular/cli --no-save

gurgelv on 12 Jan 2018

👍36 ❤10 🎉9

thanks @gurgelv that worked 👍

iamviswajith on 13 Jan 2018

🎉2 👍1

Thanks @gurgelv, works!

ricartoons on 13 Jan 2018

That will make you able to create a new project correct !!
but try to do
ng new component name
you will still get : Error: dryRunSink.commit(...).ignoreElements(...).concat is not a function
dryRunSink.commit(...).ignoreElements(...).concat is not a function

anankassis on 13 Jan 2018

👍2

Adding

"@angular-devkit/schematics":"0.0.42", 
"@angular-devkit/core": "0.0.23"

into devDependencies don't resolve problem in my case. The build still broken.

IgorKharkiv on 13 Jan 2018

👍2

i have of same problem :C

LeezMito on 13 Jan 2018

I am also stuck with same error:
Angular CLI: 1.6.4
Node: 8.9.4
OS: win32 x64
Angular:

salimperwaiz on 13 Jan 2018

Great solution @gurgelv works perfect!

tarah-s on 13 Jan 2018

thank u! @gurgelv it works fine!

casehill on 13 Jan 2018

For some reason I had a earlier local version of the CLI? Make sure you don't. Mine seems to be working now (not getting this error) with the above additions to package.json BUT I think there may be other problems. But I'm able to create components and modules.
Angular CLI: 1.6.4
Node: v8.9.1
OS: Win10 x64

derobiom on 13 Jan 2018

Thank you @gurgelv it works!

salimperwaiz on 13 Jan 2018

I Needed to npm install , after adding those lines to the dev dependencies , and i think now it is working

anankassis on 13 Jan 2018

I have the same error: _"Error: dryRunSink.commit(...)"_

Node.js: v9.4.0
npm: 5.6.0
Angular CLI: 1.6.4

Maybe I would to reinstall Angular CLI 1.5
The commands that I used

sudo npm un -g @angular/cli
sudo npm cache clean --force
sudo npm i -g @angular/[email protected]

DiegoRodriguezTandil on 13 Jan 2018

The same problem here.

Node: 8.5
NPM: 5.3

ng-cli: 1.4.3
ng-cli: 1.5.3
ng-cli: 1.6.4

I've tried with the above cli's versions and is the same problem. For 1.4 and 1.5 cli version I can't create new components, with 1.6 version I can't create new projects.

cdCarlos on 13 Jan 2018

i don't get it ... was working fine just a while ago and then i got the dreaded error why is rolling back to an older version of the cli still producing the same error? tried 1.5.3

Metrophobe on 13 Jan 2018

There is a fix about to be released for this based upon PR angular/devkit#384

Brocco on 13 Jan 2018

❤1

@Metrophobe I think the issue is with the angular/devkit dependency, so even if you use lower releases of ng-cli you'll still get the faulty dependency.

Cosmin-Parvulescu on 13 Jan 2018

@Metrophobe I think the issue is with the angular/devkit dependency, so even if you use lower releases of ng-cli you'll still get the faulty dependency.

so can we actually install an older angular/devkit and get back up and running ? the proposed solution previously further up is not working for me ... projects/ components not generating and am in the middle of some work! :(

Metrophobe on 13 Jan 2018

There is a fix about to be released for this based upon PR angular/devkit#384

Many thanks for the effort! How do I apply this fix ?

Metrophobe on 13 Jan 2018

Working on getting it released to npm, so all you would need to do is reinstall.

Brocco on 13 Jan 2018

👍5 ❤4 😄2 👎2

@Brocco Thanks

rilwans on 13 Jan 2018

@Brocco, does it fix the whole range of issues including the generator commands?

Cosmin-Parvulescu on 13 Jan 2018

@Brocco I reinstall angular-cli and the ng new is fixed but ng generate is still failing
Should I have to update anything else?
Node: 9.4.0
CLI: 1.6.4

DiegoRodriguezTandil on 13 Jan 2018

👍2

@DiegoRodriguezTandil, the fix is not on NPM yet, you can check it out on the project page...

Cosmin-Parvulescu on 13 Jan 2018

Oh boy - I guess there will be a fix by tomorrow

gareththomasnz on 13 Jan 2018

@Cosmin-Parvulescu it will fix generate commands as well.

Brocco on 13 Jan 2018

🎉3

FYI The updated version of @angular-devkit/schematics has been published, the correct version of that package should be 0.0.48.

Closing this issue now, thank you for your patience and for following up on this issue!!! ❤️

Brocco on 13 Jan 2018

👍17 ❤2 🎉1

Still getting this one myself:

$ ng g c player/inventory-form
Error: dryRunSink.commit(...).ignoreElements is not a function
dryRunSink.commit(...).ignoreElements is not a function

Angular CLI: 1.6.4
Node: 8.9.4
OS: darwin x64
Angular: 5.2.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker

@angular/cli: 1.6.4
@angular-devkit/build-optimizer: 0.0.38
@angular-devkit/core: 0.0.25
@angular-devkit/schematics: 0.0.48
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.4
@schematics/angular: 0.1.13
@schematics/schematics: 0.0.13
typescript: 2.5.3
webpack: 3.10.0

I'm also using NX and am not sure if that changes anything. If it does then it might be helpful to list schematic collections when running ng v

intellix on 13 Jan 2018

👍6

@gurgelv Well played man!

johnmikelridz on 14 Jan 2018

Here are the steps that fixed this issue for an existing project that began to fail after upgrading to Angular-CLI 1.6.4:

create a new project using ng new in a different directory, such as c:\projects\aacli\
change to the root directory of the newly created project (e.g., c:\projects\aacli)
perform a dry run to create a service, component, or module. For example try ng generate service aatest --dry-run (__NOTE__: the reason I suggest using the --dry-run switch throughout this sequence of diagnostic and repair steps is that it does not create anything, but it __does help understand if the issue is present in your project__ )
If you encountered the error that is the main topic of this thread, continue with the remaining steps; otherwise, your project does not suffer from the issue and you should not continue with the remaining steps.
switch to the root directory of the failing project
make a copy of package.json in the failing project (e.g., package-backup.json)
compare the generated package.json file in the new project to the one used in the failing project.
carefully copy only the lines of "dependencies" that match by key from the new project (aaclipackage.json) to the failing project.
copy all of the "devDependencies" portion of package.json from the new project to the failing project's equivalent "devDependencies".
rename package-lock.json in the failing project to something else, such as package-lock.backup.
delete the node_modules directory in the failing project.
run npm install in the failing project.'s root directory.
perform a dry run to create a service, component, or module, such as ng generate service aatest --dry-run

The above sequence of steps worked for me on January 14, 2018 at approximately 8:15 AM EST.

After performing the above steps, when I ran ng --version in the (previously failing) project's top-level directory, it produced the following output:

Angular CLI: 1.6.4
Node: 8.9.4
OS: win32 x64
Angular: 5.2.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cdk: 5.0.4
@angular/cli: 1.6.4
@angular/flex-layout: 2.0.0-beta.12
@angular/material: 5.0.4
@angular-devkit/build-optimizer: 0.0.38
@angular-devkit/core: 0.0.25
@angular-devkit/schematics: 0.0.48
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.4
@schematics/angular: 0.1.13
@schematics/schematics: 0.0.13
typescript: 2.5.3
webpack: 3.10.0

fmorriso on 14 Jan 2018

👍4

I was getting the same issue as @intellix with an existing project. Purging lock files and node_modules worked for me.

rm -rf node_modules package-lock.json yarn.lock
yarn || npm install

Just a quick note for Hans and Mike: we know Schematics are work-in-progress (and super exciting!), but this isn't the first time they've affected the stability of Angular CLI core. Perhaps it's worth considering confining Schematics improvements to a non-critical path branch (e.g. 1.7.0) until they too are 1.0 ready. :bowtie:

byrondover on 15 Jan 2018

👍11 🎉2

"npm i @angular-devkit/schematics":"0.0.42", "@angular-devkit/core": "0.0.23"
worked for me.
thanks @gurgelv

goldy-suryan on 15 Jan 2018

Installing @angular-devkit/[email protected] solved this problem, I can generate new services and components now. But another annoying unresolved dependency popped up instead:

@schematics/[email protected] requires a peer of @angular-devkit/[email protected] but none was installed

gehreleth on 16 Jan 2018

👍1

I have the same issue as @gehreleth. Not sure what to do here ...

ltejoles on 16 Jan 2018

Wait until @schematics/angular's dependency got updated to match @angular-devkit/[email protected], I guess. It's not blocking, just outputs annoying warnings during build process.

gehreleth on 16 Jan 2018

I was able to make it work by downgrading the angular-cli to 1.32
"@angular/cli": "1.3.2",

ltejoles on 16 Jan 2018

👍1

by adding "@angular-devkit/schematics":"0.0.42", "@angular-devkit/core": "0.0.23" , then run "npm install" work for me

csmrkid on 16 Jan 2018

@fmorriso steps worked for me (without dry run), thanks.

Angular CLI: 1.6.4 (e)
Node: 9.4.0
OS: linux x64
Angular: 5.2.0
... common, compiler, compiler-cli, core, forms, http
... language-service, platform-browser, platform-browser-dynamic
... router

@angular/cli: 1.6.4
@angular-devkit/build-optimizer: 0.0.38
@angular-devkit/core: 0.0.25
@angular-devkit/schematics: 0.0.48
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.4
@schematics/angular: 0.1.13
@schematics/schematics: 0.0.13
typescript: 2.5.3
webpack-concat-plugin: 1.4.0
webpack-dev-server: 2.9.3
webpack: 3.8.1

nuriu on 16 Jan 2018

I'm currently working on a project that has existed for 6+ months. We encountered this issue with Angular CLI when our new developers attempted to set up their dev environments and run basic Angular CLI commands. I get the following error when we attempt to generate a component:

$ ng g c some-component
Error: dryRunSink.commit(...).ignoreElements is not a function
dryRunSink.commit(...).ignoreElements is not a function

So far the only thing that has worked was downgrading to @angluar/cli to v 1.3.2. I also encountered an error regarding rxjs but that is resolved by upgrading rxjs to version 5.5.2. Here is our package.json

"dependencies": {
    "@angular/animations": "4.4.3",
    "@angular/common": "4.4.3",
    "@angular/compiler": "4.4.3",
    "@angular/core": "4.4.3",
    "@angular/forms": "4.4.3",
    "@angular/http": "4.4.3",
    "@angular/platform-browser": "4.4.3",
    "@angular/platform-browser-dynamic": "4.4.3",
    "@angular/platform-server": "4.4.3",
    "@angular/router": "4.4.3",
    "@types/lodash": "4.14.74",
    "angular2-csv": "0.2.5",
    "angular2-highcharts": "0.5.5",
    "core-js": "2.4.1",
    "lodash": "4.17.4",
    "ngx-bootstrap": "1.9.3",
    "rxjs": "5.1.0",
    "zone.js": "0.8.4"
  },
  "devDependencies": {
    "@angular/cli": "1.4.4",
    "@angular/compiler-cli": "4.4.3",
    "@types/jasmine": "2.5.38",
    "@types/node": "6.0.60",
    "codelyzer": "2.0.0",
    "jasmine-core": "2.5.2",
    "jasmine-spec-reporter": "3.2.0",
    "karma": "1.4.1",
    "karma-chrome-launcher": "2.1.1",
    "karma-cli": "1.0.1",
    "karma-coverage-istanbul-reporter": "0.2.0",
    "karma-jasmine": "1.1.0",
    "karma-jasmine-html-reporter": "0.2.2",
    "lite-server": "2.3.0",
    "protractor": "5.1.0",
    "ts-node": "2.0.0",
    "tslint": "4.5.0",
    "typescript": "2.2.0"
  }

Any help is greatly appreciated!

sengemann on 16 Jan 2018

npm install @angular-devkit/[email protected] @angular/cli --no-save

This is the vodoo that worked!

ngochibamu on 17 Jan 2018

👎1

Nope, fixed not completely. Even after upgrading @angular-devkits and purging node_modules, package.lock.json and yarn.lock.

$ ng generate service qwe
Error: dryRunSink.commit(...).ignoreElements is not a function
dryRunSink.commit(...).ignoreElements is not a function

I also confirm that downgrading to @angular/cli to 1.3.2 is the only completely working solution as of now.

Reference:
Node.js: 8.9.4 x64
npm: 5.6.0
package.json:

{
  "dependencies": {
    "@angular/common": "5.0.1",
    "@angular/compiler": "5.0.1",
    "@angular/core": "5.0.1",
    "@angular/forms": "5.0.1",
    "@angular/http": "5.0.1",
    "@angular/platform-browser": "5.0.1",
    "@angular/platform-browser-dynamic": "5.0.1",
    "@angular/router": "5.0.1",
    "@angular/upgrade": "5.0.1",
    "@asymmetrik/ngx-leaflet": "^3.0.1",
    "bootstrap": "4.0.0-beta.2",
    "chart.js": "2.7.1",
    "core-js": "2.5.1",
    "font-awesome": "^4.7.0",
    "leaflet": "^1.3.0",
    "moment": "2.19.1",
    "ng2-charts": "1.6.0",
    "ngx-bootstrap": "1.9.3",
    "rxjs": "5.5.2",
    "simple-line-icons": "^2.4.1",
    "ts-helpers": "1.1.2",
    "zone.js": "0.8.18"
  },
  "devDependencies": {
    "@angular-devkit/build-optimizer": "^0.0.38",
    "@angular-devkit/core": "^0.0.25",
    "@angular-devkit/schematics": "^0.0.48",
    "@angular/cli": "^1.6.4",
    "@angular/compiler-cli": "5.0.1",
    "@types/jasmine": "2.6.3",
    "@types/leaflet": "^1.2.5",
    "@types/node": "8.0.50",
    "codelyzer": "4.0.1",
    "jasmine-core": "2.8.0",
    "jasmine-spec-reporter": "4.2.1",
    "karma": "1.7.1",
    "karma-chrome-launcher": "2.2.0",
    "karma-cli": "1.0.1",
    "karma-coverage-istanbul-reporter": "1.3.0",
    "karma-jasmine": "1.1.0",
    "karma-jasmine-html-reporter": "0.2.2",
    "protractor": "5.2.0",
    "ts-node": "3.3.0",
    "tslint": "5.8.0",
    "typescript": "2.6.1"
  }
}

Deilan on 17 Jan 2018

😕1 👍1

working perfectly with following :

 
"dependencies": {
    "@angular/animations": "5.2.0",
    "@angular/common": "5.2.0",
    "@angular/compiler": "5.2.0",
    "@angular/core": "5.2.0",
    "@angular/forms": "5.2.0",
    "@angular/http": "5.2.0",
    "@angular/platform-browser": "5.2.0",
    "@angular/platform-browser-dynamic": "5.2.0",
    "@angular/router": "5.2.0",
    "bootstrap": "4.0.0-beta.2",
    "core-js": "2.5.3",
    "font-awesome": "4.7.0",
    "intl": "1.2.5",
    "jquery": "3.2.1",
    "ngx-perfect-scrollbar": "5.2.0",
    "popper.js": "1.12.9",
    "rxjs": "5.5.6",
    "zone.js": "0.8.20"
  },
  "devDependencies": {
    "@angular/cli": "1.6.4",
    "@angular/compiler-cli": "5.2.0",
    "@angular/language-service": "5.2.0",
    "@types/jasmine": "2.8.4",
    "@types/node": "9.3.0",
    "codelyzer": "4.0.2",
    "jasmine-core": "2.8.0",
    "jasmine-spec-reporter": "4.2.1",
    "karma": "2.0.0",
    "karma-chrome-launcher": "2.2.0",
    "karma-cli": "1.0.1",
    "karma-coverage-istanbul-reporter": "1.3.3",
    "karma-jasmine": "1.1.1",
    "karma-jasmine-html-reporter": "0.2.2",
    "protractor": "5.2.2",
    "ts-node": "3.3.0",
    "tslib": "1.8.1",
    "tslint": "5.9.1",
    "typescript": "2.4.2"
  }

yuveliremil on 17 Jan 2018

It works for me on
Angular CLI: 1.6.4
Node: 6.10.3
the common thing I can see on users had this issue is node version greater than 8 or less than 6.9

Wael3bbas on 17 Jan 2018

I have the same problem and installing these libraries

    "@angular-devkit/build-optimizer": "^0.0.38",
    "@angular-devkit/core": "^0.0.25",
    "@angular-devkit/schematics": "^0.0.48",

does not help, someone has already found a bug-fix?

CisSasGot on 18 Jan 2018

Solved!
Add to package.json inside devDependencies

"@angular-devkit/schematics": "0.0.43",
"@angular-devkit/core": "0.0.23"

Save file
npm install

hugocaldeira on 18 Jan 2018

👍2

@hugocaldeira I dont think. This way did not help me.

Dok11 on 18 Jan 2018

Also, this works for me

npm i @angular-devkit/[email protected] @angular/cli --no-save

Wael3bbas on 18 Jan 2018

@mendhak's solution worked for me
Angular CLI: 1.6.2
Node: 9.3.0
OS: darwin x64

abalazsics on 19 Jan 2018

I just upgraded Angular CLI and ran into this issue generating components. I noticed I didn't get this issue when I created a new project.

The fix for me was to remove the node_modules folder and package-lock.json. Then re-install node modules using npm install

Angular CLI: 1.6.5
Node: 8.7.0
OS: darwin x64

package.json
{
  "name": "whatsnew",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build --prod",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^5.2.0",
    "@angular/common": "^5.2.0",
    "@angular/compiler": "^5.2.0",
    "@angular/core": "^5.2.0",
    "@angular/forms": "^5.2.0",
    "@angular/http": "^5.2.0",
    "@angular/platform-browser": "^5.2.0",
    "@angular/platform-browser-dynamic": "^5.2.0",
    "@angular/router": "^5.2.0",
    "core-js": "^2.4.1",
    "rxjs": "^5.5.6",
    "zone.js": "^0.8.19"
  },
  "devDependencies": {
    "@angular/cli": "1.6.5",
    "@angular/compiler-cli": "^5.2.0",
    "@angular/language-service": "^5.2.0",
    "@types/jasmine": "~2.8.3",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "~6.0.60",
    "codelyzer": "^4.0.1",
    "jasmine-core": "~2.8.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~2.0.0",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.1.2",
    "ts-node": "~4.1.0",
    "tslint": "~5.9.1",
    "typescript": "~2.5.3"
  }
}

onedotover on 19 Jan 2018

👍4

That helped me:

Removed node_modules and re-installed by npm install
Installed npm i --save-dev @angular-devkit/core

ssokurenko on 19 Jan 2018

👍1

@ssokurenko solution worked for me after the other solutions failed to work....

foote-Greg on 20 Jan 2018

👍1

same thing for me on 1.6.5 it seems. Deleted node_modules and package-lock.json and reinstalled. Now it's all good

intellix on 21 Jan 2018

👍1

Thanks @gurgelv its working.

chandurams on 21 Jan 2018

Thanks @ssokurenko . Your solution worked for me (CLI 1.6.5)!

morismael on 21 Jan 2018

👍1

Why is this issue closed? I can't seem to get rid of it at all.

Siafu on 21 Jan 2018

👍3

Thanks @ssokurenko . Your solution worked for me (CLI 1.6.5)!

topikus on 22 Jan 2018

👍1

Sorry, still get same error!
I have deleted my node_modules folder and reinstalled my dependencies.
What can I do now?
Thanks, Markus

My environment:
Angular CLI: 1.6.5
Node: 6.9.1
OS: win32 x64
Angular: 5.2.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

@angular/cdk: 5.1.0
@angular/cli: 1.6.5
@angular/flex-layout: 2.0.0-beta.12
@angular/material: 5.1.0
@angular-devkit/build-optimizer: 0.0.41
@angular-devkit/core: 0.0.28
@angular-devkit/schematics: 0.0.51
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.5
@schematics/angular: 0.1.16
typescript: 2.4.2
webpack: 3.10.0

markus-heinisch on 22 Jan 2018

The workaround in the commit by @jgarciao was the only thing that worked for me.

EDIT: for clarity, needed to delete node-modules folder and npm install after making the changes

Justin-MacIntosh on 22 Jan 2018

still same problem. Tried @jgarciao 's solution - not working for me :(

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

marc101101 on 22 Jan 2018

I'm also facing this issue with the following configuration:

Angular CLI: 1.6.5
Node: 6.11.2
OS: win32 x64
Angular: 5.2.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.6.5
@angular-devkit/build-optimizer: 0.0.41
@angular-devkit/core: 0.0.28
@angular-devkit/schematics: 0.0.51
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.5
@schematics/angular: 0.1.16
typescript: 2.4.2
webpack: 3.10.0

However, the following is working on another project on the same machine:

Angular CLI: 1.5.0
Node: 6.11.2
OS: win32 x64
Angular: 5.0.0
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic, router

@angular/cli: 1.5.0
@angular-devkit/build-optimizer: 0.0.32
@angular-devkit/core: 0.0.20
@angular-devkit/schematics: 0.0.35
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.0
@schematics/angular: 0.1.0
typescript: 2.4.2
webpack: 3.1.0

My global CLI version is 1.6.5

None of the solutions mentioned above are working for me.

Shouldn't this issue be opened again?

kanafghan on 22 Jan 2018

👍2

@marc101101 Did you delete the node-modules folder, and npm install after making the fix in the commit?

Justin-MacIntosh on 22 Jan 2018

@Justin-MacIntosh deleting node_modules and ran npm install fixed my issue. Thanks

kchiragowni on 22 Jan 2018

The solution suggested by @jgarciao does not work for me, even after deleting all node modules. I also tried installing globally the packages, but still getting the same error. Any idea?

ilDon on 23 Jan 2018

👍1

@ghego1 check versions of your packages

Dok11 on 23 Jan 2018

@Dok11 Yes checked, they all seem in line with those suggested by @jgarciao:

"dependencies": {
    "@angular-devkit/schematics": "0.0.51",
    "@angular-devkit/core": "0.0.28",
    "@angular-redux/store": "^7.0.2",
    "@angular/animations": "^5.2.0",
    "@angular/cdk": "^5.0.4",
    "@angular/common": "^5.2.0",
    "@angular/compiler": "^5.2.0",
    "@angular/core": "^5.2.0",
    "@angular/flex-layout": "2.0.0-beta.12",
    "@angular/forms": "^5.2.0",
    "@angular/http": "^5.2.0",
    "@angular/material": "^5.0.4",
    "@angular/platform-browser": "^5.2.0",
    "@angular/platform-browser-dynamic": "^5.2.0",
    "@angular/platform-server": "^5.2.0",
    "@angular/router": "^5.2.0",
    "@nguniversal/express-engine": "^5.0.0-beta.5",
    "@ngx-cache/core": "^5.0.0",
    "@ngx-translate/core": "^9.1.1",
    "@ngx-translate/http-loader": "^2.0.1",
    "@ngx-universal/translate-loader": "^5.0.0",
    "@types/lodash": "^4.14.92",
    "core-js": "^2.5.3",
    "hammerjs": "^2.0.8",
    "lodash": "^4.17.4",
    "ngx-cookie-service": "^1.0.10",
    "q": "^1.5.0",
    "redux": "^3.7.2",
    "rxjs": "^5.5.6",
    "spider-detector": "^1.0.18",
    "zone.js": "^0.8.20"
  },
  "devDependencies": {
    "@angular/cli": "^1.6.5",
    "@angular/compiler-cli": "^5.2.1",
    "@angular/language-service": "^5.2.1",
    "@types/jasmine": "~2.8.4",
    "@types/jasminewd2": "~2.0.3",
    "@types/node": "~9.3.0",
    "angular-tslint-rules": "^1.1.0",
    "codelyzer": "~4.0.2",
    "jasmine-core": "~2.8.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~2.0.0",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.3.3",
    "karma-jasmine": "~1.1.1",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.2.2",
    "ts-loader": "^3.2.0",
    "ts-node": "~4.1.0",
    "tslint": "^5.9.1",
    "typescript": ">=2.4.2 <2.6.0",
    "webpack-node-externals": "^1.6.0"
  }

ilDon on 23 Jan 2018

Deleting yarn.lock and running yarn install again helped me.

MartinNuc on 23 Jan 2018

👍2 👎1

@MartinNuc right! So the trick when using yarn is to first update package.json as described by @jgarciao, delete yarn.lock, and then run yarn install.

ilDon on 23 Jan 2018

same error, thk for up

FreezeSoul on 24 Jan 2018

I have fixed it by install proper rxjs version:
yarn add [email protected]

But, my error was

dryRunSink.commit(...).ignoreElements is not a function

glebmachine on 24 Jan 2018

@mendhak solution worked for me!

olufemioyedepo on 24 Jan 2018

👍1

I have the proper rxjs version (5.5.2) along with all the proper version above and I still see the same error.

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

RonakR on 24 Jan 2018

Hi, has someone tried to solve the problem with angular-cli v1.7.0-beta.1?
I'm referring to:

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

markus-heinisch on 24 Jan 2018

👍1

have the exact same issue right now when using ng generate component

andreimcristof on 24 Jan 2018

👍2

@andreimcristof try this
npm install @angular-devkit/[email protected] @angular/cli --no-save

olufemioyedepo on 24 Jan 2018

seems updating to

"@angular-devkit/schematics":"0.0.51",
"@angular-devkit/core": "0.0.28",

and deleting node_modules + npm install might have done the trick for me. But I also updated some other versions of ng libraries that were warned about after previous installs, so I can't say with absolute certainty that the above two lines are what pushed it over the top.
So, at least ng g service bla now works.

yogibimbi on 24 Jan 2018

👍1

Also experiencing this issue, tried various fixes suggested here. I don't think this issue should be closed.

Error:

ng g component name
Error: dryRunSink.commit(...).ignoreElements is not a function
dryRunSink.commit(...).ignoreElements is not a function

And version info:

Angular CLI: 1.6.5
Node: 9.2.0
OS: darwin x64
Angular: 5.2.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

@angular/cdk: 5.1.0
@angular/cli: 1.6.5
@angular/flex-layout: 2.0.0-beta.10-4905443
@angular/material: 5.1.0
@angular-devkit/build-optimizer: 0.0.41
@angular-devkit/core: 0.0.28
@angular-devkit/schematics: 0.0.45
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.5
@schematics/angular: 0.1.16
typescript: 2.4.2
webpack-bundle-analyzer: 2.9.2
webpack: 3.10.0

EDIT: My problem was with using rxjs 5.5.2. I changed to the following dev dependencies:

"@angular-devkit/core": "0.0.28",
"@angular-devkit/schematics": "0.0.51",

and updated to rxjs 5.5.6

"rxjs": "5.5.6",

and then deleted my node_modules and package-lock, then npm install. Hope this helps someone.

NickToony on 24 Jan 2018

👍3 🎉2

@mendhak solution didn't work for me. I got a new one after that:

Error: Path "/app/app.module.ts" does not exist.
Path "/app/app.module.ts" does not exist.

I don't think this issue should be closed.

titusfx on 24 Jan 2018

I've tried every single solution offered here and nothing works. This is ridiculous. Why is this issue closed?

jorgeso on 24 Jan 2018

👍5 😕2

Try using this:

yarn add --dev @angular-devkit/core@^0.0.28
yarn add rxjs@^5.5.2
rm -rf yarn.lock; rm -rf node_modules;
yarn;

This error cause in angular-devkit/core. There was undefined observable
method.
Yesterday it was take me about 3 hours to investigate and fix that. I hope
it will help

glebmachine on 25 Jan 2018

I have found a solution for my project: I have deleted my node_modules folder, checked my package.json and installed my dependencies in several steps:

Angular dependencies and devDependencies (all the dependencies which come with ng new app)
Material deps
all other dependencies

Here is my package.json
"dependencies": { "@angular/animations": "~5.2.2", "@angular/cdk": "^5.1.0", "@angular/common": "~5.2.2", "@angular/compiler": "~5.2.2", "@angular/core": "~5.2.2", "@angular/flex-layout": "2.0.0-beta.12", "@angular/forms": "~5.2.2", "@angular/http": "~5.2.2", "@angular/material": "^5.1.0", "@angular/platform-browser": "~5.2.2", "@angular/platform-browser-dynamic": "~5.2.2", "@angular/router": "~5.2.2", "classlist.js": "1.1.20150312", "core-js": "2.5.3", "hammerjs": "2.0.8", "intl": "1.2.5", "moment": "2.20.1", "moment-business": "3.0.1", "parse-decimal-number": "1.0.0", "rxjs": "^5.5.6", "web-animations-js": "2.3.1", "zone.js": "0.8.4" }, "devDependencies": { "@angular/cli": "^1.6.5", "@angular/compiler-cli": "~5.2.2", "@angular/language-service": "~5.2.2", "@types/jasmine": "2.5.38", "@types/node": "6.0.96", "codelyzer": "4.1.0", "jasmine-core": "2.6.4", "jasmine-spec-reporter": "4.1.1", "karma": "1.4.1", "karma-chrome-launcher": "2.0.0", "karma-cli": "1.0.1", "karma-coverage-istanbul-reporter": "0.2.0", "karma-jasmine": "1.1.0", "karma-jasmine-html-reporter": "0.2.2", "protractor": "5.1.2", "replace-in-file": "2.6.4", "sass-lint": "1.10.2", "ts-node": "3.2.2", "tslint": "5.7.0", "typescript": "2.4.2" }

markus-heinisch on 25 Jan 2018

Not working

mivanov@9TDQH5J MINGW64 /c/Develop/rosnfo-ui/rosnfo-ui/src/app/test (hotfix/RSBNFO-302/sms-product-bugfix)
$ ng g c Test
Error: dryRunSink.commit(...).ignoreElements is not a function
dryRunSink.commit(...).ignoreElements is not a function

mivanov@9TDQH5J MINGW64 /c/Develop/rosnfo-ui/rosnfo-ui/src/app/test (hotfix/RSBNFO-302/sms-product-bugfix)
$ ng -v

    _                      _                 ____ _     ___
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/

Angular CLI: 1.6.5
Node: 8.9.1
OS: win32 x64
Angular: 5.2.2
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic, router

@angular/cdk: 5.1.0
@angular/cli: 1.6.5
@angular/material: 5.1.0
@angular-devkit/build-optimizer: 0.0.42
@angular-devkit/core: 0.0.28
@angular-devkit/schematics: 0.0.51
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.5
@schematics/angular: 0.1.17
typescript: 2.4.2
webpack-bundle-analyzer: 2.9.2
webpack: 3.10.0

splincode on 25 Jan 2018

This was closed as no longer an issue, but I just installed @angular/cli (using npm install -g @angular/cli@latest) and cannot create a new app. Is 1.6.5 still pulling in the old dependency? I was under the impression, per https://github.com/angular/angular-cli/issues/9283#issuecomment-358937066 that this was no longer an issue.

C:\workspace>ng -v

    _                      _                 ____ _     ___
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/

Angular CLI: 1.6.5
Node: 6.11.1
OS: win32 x64
Angular:
...

C:\workspace>ng new test
Error: dryRunSink.commit(...).ignoreElements is not a function
dryRunSink.commit(...).ignoreElements is not a function

C:\workspace>npm list -g --depth=1
C:\Users\me\AppData\Roaming\npm
+-- @angular/[email protected]
| +-- @angular-devkit/[email protected]
| +-- @angular-devkit/[email protected]
| +-- @angular-devkit/[email protected]
| +-- @ngtools/[email protected]
| +-- @ngtools/[email protected]
| +-- @schematics/[email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| +-- [email protected]
| `-- [email protected]
`-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  +-- [email protected]
  `-- [email protected]

roddy on 25 Jan 2018

👍3

Please reopen, still an issue

larssn on 25 Jan 2018

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.

Brocco on 25 Jan 2018

👍25 ❤12 👎2

@Brocco Thank you, it is worked))

splincode on 26 Jan 2018

@Brocco
We -The Developers- understand the complexity of such technology n we love n appreciate all of ur efforts BUT please take into consideration testing whatever new build before pushing, as a bug blocks n wastes thousands of hours of angular lovers, thanks for understanding, cheers!

mhmo91 on 26 Jan 2018

👍13

@Brocco problem solved! Thank you!

hugocaldeira on 26 Jan 2018

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

LunoDaniel on 31 Jan 2018

@gurgelv You're a Rockstar!, thank you

CarMoreno on 9 Feb 2018

👎1

I had the same problem.
But this (npm install @angular-devkit/[email protected] @angular/cli --no-save) solved my problem.

My big thanks go to Mendhak.

nyoman on 13 Apr 2018

👎1

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.

Sharkesm on 12 May 2018

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",

Herotko on 7 Jun 2018

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.