angular / angular-cli

CLI tool for Angular
https://cli.angular.io
MIT License
26.72k 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

csmrkid commented 6 years ago

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

nuriu commented 6 years ago

@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
scott-engemann commented 6 years ago

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!

ngochibamu commented 6 years ago

npm install @angular-devkit/schematics@0.0.45 @angular/cli --no-save

This is the vodoo that worked!

Deilan commented 6 years ago

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"
  }
}
yuveliremil commented 6 years ago

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"
  }
Wael3bbas commented 6 years ago

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

j-Cis commented 6 years ago

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?

hugocaldeira commented 6 years ago

Solved! Add to package.json inside devDependencies

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

Save file npm install

Dok11 commented 6 years ago

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

Wael3bbas commented 6 years ago

Also, this works for me

npm i @angular-devkit/schematics@0.0.45 @angular/cli --no-save

abalazsics commented 6 years ago

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

onedotover commented 6 years ago

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"
  }
}
ssokurenko commented 6 years ago

That helped me:

foote-Greg commented 6 years ago

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

intellix commented 6 years ago

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

chandurams commented 6 years ago

Thanks @gurgelv its working.

morismael commented 6 years ago

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

Siafu commented 6 years ago

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

topikus commented 6 years ago

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

markus-heinisch commented 6 years ago

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

Justin-MacIntosh commented 6 years ago

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

marc101101 commented 6 years ago

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
kanafghan commented 6 years ago

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?

Justin-MacIntosh commented 6 years ago

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

kchiragowni commented 6 years ago

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

ilDon commented 6 years ago

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?

Dok11 commented 6 years ago

@ghego1 check versions of your packages

ilDon commented 6 years ago

@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"
  }
MartinNuc commented 6 years ago

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

ilDon commented 6 years ago

@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.

FreezeSoul commented 6 years ago

same error, thk for up

glebmachine commented 6 years ago

I have fixed it by install proper rxjs version: yarn add rxjs@5.5.2

But, my error was

dryRunSink.commit(...).ignoreElements is not a function
olufemioyedepo commented 6 years ago

@mendhak solution worked for me!

RonakR commented 6 years ago

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
markus-heinisch commented 6 years ago

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
andreimcristof commented 6 years ago

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

olufemioyedepo commented 6 years ago

@andreimcristof try this npm install @angular-devkit/schematics@0.0.45 @angular/cli --no-save

yogibimbi commented 6 years ago

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.

NickToony commented 6 years ago

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.

titusfx commented 6 years ago

@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.

jorgeso commented 6 years ago

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

glebmachine commented 6 years ago

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

markus-heinisch commented 6 years ago

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:

  1. Angular dependencies and devDependencies (all the dependencies which come with ng new app)
  2. Material deps
  3. 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" }

splincode commented 6 years ago

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
roddy commented 6 years ago

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/cli@1.6.5
| +-- @angular-devkit/build-optimizer@0.0.42
| +-- @angular-devkit/core@0.0.29
| +-- @angular-devkit/schematics@0.0.52
| +-- @ngtools/json-schema@1.1.0
| +-- @ngtools/webpack@1.9.5
| +-- @schematics/angular@0.1.17
| +-- autoprefixer@7.2.5
| +-- chalk@2.2.2
| +-- circular-dependency-plugin@4.2.1
| +-- common-tags@1.5.1
| +-- copy-webpack-plugin@4.2.3
| +-- core-object@3.1.5
| +-- css-loader@0.28.7
| +-- cssnano@3.10.0
| +-- denodeify@1.2.1
| +-- ember-cli-string-utils@1.1.0
| +-- exports-loader@0.6.4
| +-- extract-text-webpack-plugin@3.0.2
| +-- file-loader@1.1.5
| +-- fs-extra@4.0.2
| +-- glob@7.1.2
| +-- html-webpack-plugin@2.30.1
| +-- istanbul-instrumenter-loader@3.0.0
| +-- karma-source-map-support@1.2.0
| +-- less@2.7.3
| +-- less-loader@4.0.5
| +-- license-webpack-plugin@1.1.1
| +-- loader-utils@1.1.0
| +-- lodash@4.17.4
| +-- memory-fs@0.4.1
| +-- minimatch@3.0.4
| +-- node-modules-path@1.0.1
| +-- node-sass@4.7.2
| +-- nopt@4.0.1
| +-- opn@5.1.0
| +-- portfinder@1.0.13
| +-- postcss-import@11.0.0
| +-- postcss-loader@2.0.10
| +-- postcss-url@7.3.0
| +-- raw-loader@0.5.1
| +-- resolve@1.5.0
| +-- rxjs@5.5.3
| +-- sass-loader@6.0.6
| +-- semver@5.4.1
| +-- silent-error@1.1.0
| +-- source-map-loader@0.2.3
| +-- source-map-support@0.4.18
| +-- style-loader@0.13.2
| +-- stylus@0.54.5
| +-- stylus-loader@3.0.1
| +-- uglifyjs-webpack-plugin@1.1.6
| +-- url-loader@0.6.2
| +-- webpack@3.10.0
| +-- webpack-dev-middleware@1.12.2
| +-- webpack-dev-server@2.11.1
| +-- webpack-merge@4.1.1
| +-- webpack-sources@1.1.0
| `-- webpack-subresource-integrity@1.0.2
`-- npm-check-updates@2.13.0
  +-- bluebird@3.5.1
  +-- chalk@1.1.3
  +-- cint@8.2.1
  +-- cli-table@0.3.1
  +-- commander@2.12.2
  +-- fast-diff@1.1.2
  +-- find-up@1.1.2
  +-- get-stdin@5.0.1
  +-- json-parse-helpfulerror@1.0.3
  +-- lodash@4.17.4
  +-- node-alias@1.0.4
  +-- npm@3.10.10
  +-- npmi@2.0.1
  +-- semver@5.4.1
  +-- semver-utils@1.1.1
  +-- snyk@1.53.0
  +-- spawn-please@0.3.0
  `-- update-notifier@2.3.0
larssn commented 6 years ago

Please reopen, still an issue

Brocco 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.

splincode commented 6 years ago

@Brocco Thank you, it is worked))

mhmo91 commented 6 years ago

@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!