Skip to content
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

ng serve --aot fail after file change #11835

Closed
WandererInVoids opened this issue Aug 9, 2018 · 67 comments
Closed

ng serve --aot fail after file change #11835

WandererInVoids opened this issue Aug 9, 2018 · 67 comments

Comments

@WandererInVoids
Copy link

WandererInVoids commented Aug 9, 2018

Bug Report or Feature Request (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)

- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

Angular CLI: 6.1.2
Node: 10.0.0
OS: win32 x64
Angular: 6.1.2
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

Package Version

@angular-devkit/architect 0.7.2
@angular-devkit/build-angular 0.7.2
@angular-devkit/build-optimizer 0.7.2
@angular-devkit/build-webpack 0.7.2
@angular-devkit/core 0.7.2
@angular-devkit/schematics 0.7.2
@angular/cdk 6.4.3
@angular/material 6.4.3
@ngtools/webpack 6.1.2
@schematics/angular 0.7.2
@schematics/update 0.7.2
rxjs 6.2.2
typescript 2.9.2
webpack 4.9.2
-->

Repro steps

  1. run ng serve with aot flag
  2. change something in watch filles
  3. see error in module find(file that change)

The log given by the failure

Module not found: Error: Can't resolve '@angular/material/button.ngfactory' in 'D:\Flare\flare.ui2\src\homeapp\app\components\reports\profitAndLoss'
ERROR in ./src/homeapp/app/components/reports/profitAndLoss/profit.and.loss.ngfactory.js
Module not found: Error: Can't resolve '@angular/material/checkbox.ngfactory' in 'D:\Flare\flare.ui2\src\homeapp\app\components\reports\profitAndLoss'
ERROR in ./src/homeapp/app/components/reports/profitAndLoss/profit.and.loss.ngfactory.js
Module not found: Error: Can't resolve '@angular/material/form-field.ngfactory' in '.\src\homeapp\app\components\reports\profitAndLoss'
ERROR in ./src/homeapp/app/components/reports/profitAndLoss/profit.and.loss.ngfactory.js
Module not found: Error: Can't resolve '@angular/material/menu.ngfactory' in '.\src\homeapp\app\components\reports\profitAndLoss'

Date: 2018-08-09T17:57:03.581Z - Hash: 12b8572033feade48d1a - Time: 34472ms
4 unchanged chunks
chunk {main} main.js (main) 16.2 MB [initial] [rendered]

i 「wdm」: Failed to compile.

Desired functionality

work as before update

Mention any other details that might be useful

I didn't know where to write, in @angular/compile or here but error showed in cli, so...
This breaking from this fix angular/angular#25335.
Reverting @angular/compiler to 6.1.1 workaround for this.
I tested without fix, it work as before.

@dkchv
Copy link

dkchv commented Aug 9, 2018

the same, v6.1.2 is broken.
downgrade to
"@angular/compiler-cli": "6.1.1",

@klemenoslaj
Copy link

klemenoslaj commented Aug 10, 2018

I have exactly the same problem, and reverting @angular/compiler "fixes" the problem.

@vchimev
Copy link

vchimev commented Aug 10, 2018

Hey,

This issue can also reproduce as follows:

Steps:

ng new ngApp --routing && cd ngApp
ng serve --aot
change a file under watch

Error:

ERROR in ./src/app/app.module.ngfactory.js
Module not found: Error: Can't resolve '@angular/router.ngfactory' in '/Users/vchimev/Work/tmp/ngApp/src/app'
ℹ 「wdm」: Failed to compile.

Causes NativeScript/nativescript-dev-webpack#630.

@MichielDG
Copy link

I have exactly the same problem with Angular CLI: 6.1.3

@alexeagle
Copy link
Contributor

Added to the top of our backlog

@clydin
Copy link
Member

clydin commented Aug 10, 2018

I was unable to replicate this with the following versions. Can you try with the versions listed below? For existing projects, please ensure that @angular-devkit/build-angular is updated; upgrading the CLI does not automatically update @angular-devkit/build-angular.

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

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.7.3
@angular-devkit/build-angular     0.7.3
@angular-devkit/build-optimizer   0.7.3
@angular-devkit/build-webpack     0.7.3
@angular-devkit/core              0.7.3
@angular-devkit/schematics        0.7.3
@angular/cli                      6.1.3
@ngtools/webpack                  6.1.3
@schematics/angular               0.7.3
@schematics/update                0.7.3
rxjs                              6.2.2
typescript                        2.7.2
webpack                           4.9.2

@WandererInVoids
Copy link
Author

WandererInVoids commented Aug 10, 2018

@clydin i used this:

Angular CLI: 6.1.3
Node: 10.8.0
OS: win32 x64(windows 10)
Angular: 6.1.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.7.3
@angular-devkit/build-angular     0.7.3
@angular-devkit/build-optimizer   0.7.3
@angular-devkit/build-webpack     0.7.3
@angular-devkit/core              0.7.3
@angular-devkit/schematics        0.7.3
@angular/cdk                      6.4.3
@angular/cli                      6.1.3
@angular/material                 6.4.3
@ngtools/webpack                  6.1.3
@schematics/angular               0.7.3
@schematics/update                0.7.3
rxjs                              6.2.2
typescript                        2.9.2
webpack                           4.9.2

also i used ng server without bazel,
same error when updated.

my tsconfig

{
  "compilerOptions": {
    "baseUrl": "",
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "listEmittedFiles":true,
    "lib": ["es6", "dom", "es2016.array.include"],
    "mapRoot": "./",
    "module": "es6",
    "moduleResolution": "node",
    "outDir": "../dist/out-tsc",
    "sourceMap": false,
    "target": "es5",
    "alwaysStrict": true,
    "typeRoots": [
      "../node_modules/@types"
    ]
  },
  "angularCompilerOptions": {
    "preserveWhitespaces": false
  }
}

serve config

  "serve": {
          "builder": "@angular-devkit/build-angular:dev-server",
          "options": {
            "browserTarget": "homeapp:build"
          },
          "configurations": {
            "production": {
              "browserTarget": "homeapp:build:production"
            }
          }
        },

command : ng serve --aot --source-map=false
it happen time to time just change file few times. U will see it.

@clydin
Copy link
Member

clydin commented Aug 10, 2018

As a test, every watched file in a new project was changed twice with both TS 2.7.2 and TS 2.9.2; and was unable to reproduce. Two files were also changed 5 times each (a component and a module) with the same outcome. To fully diagnose the issue, a minimal reproduction or exact steps to trigger the issue will be needed in light of the inability to reproduce.

@WandererInVoids
Copy link
Author

WandererInVoids commented Aug 10, 2018

@clydin can u try this #11835 (comment),
u changed file while server active?

@clydin
Copy link
Member

clydin commented Aug 11, 2018

Thanks. Traced the issue to this PR in angular itself: angular/angular#25335
This change was introduced within @angular/compiler in version 6.1.2.

@alanxone
Copy link

Same issue confirmed, and the only solution for AOT so far is back to use 6.1.1

@WandererInVoids
Copy link
Author

any progress?
With this i can`t test angular 7 beta

@deerua
Copy link

deerua commented Aug 15, 2018

For me this issue even with 6.1.1 (6.1.0 all was fine)

@alanxone
Copy link

@deerua Can you share your package.json to see if any conflicts?

@deerua
Copy link

deerua commented Aug 15, 2018

Sure


  "dependencies": {
    "@angular/animations": "^6.1.1",
    "@angular/cdk": "^6.4.1",
    "@angular/common": "^6.1.1",
    "@angular/compiler": "^6.1.1",
    "@angular/core": "^6.1.1",
    "@angular/forms": "^6.1.1",
    "@angular/http": "^6.1.1",
    "@angular/material": "^6.4.1",
    "@angular/platform-browser": "^6.1.1",
    "@angular/platform-browser-dynamic": "^6.1.1",
    "@angular/platform-server": "^6.1.1",
    "@angular/router": "^6.1.1",
    "@ngrx/core": "^1.2.0",
    "@ngrx/effects": "^6.0.1",
    "@ngrx/router-store": "^6.0.1",
    "@ngrx/store": "^6.0.1",
    "@ngrx/store-devtools": "^6.0.1",
    "@nguniversal/common": "6.0.0",
    "@nguniversal/express-engine": "6.0.0",
    "@nguniversal/module-map-ngfactory-loader": "6.0.0",
    "@ngx-translate/core": "10.0.2",
    "@ngx-translate/http-loader": "^3.0.1",
    "@types/angular": "1.6.45",
    "@types/cheerio": "^0.22.7",
    "@types/compression": "0.0.36",
    "@types/googlemaps": "^3.30.8",
    "angular-calendar": "0.25.1",
    "cheerio": "^1.0.0-rc.2",
    "compression": "^1.7.2",
    "core-js": "2.5.1",
    "cross-env": "https://registry.npmjs.org/cross-env/-/cross-env-5.1.4.tgz",
    "date-fns": "1.29.0",
    "express-winston": "latest",
    "hammerjs": "2.0.8",
    "immer": "^1.5.0",
    "jasmine-console-reporter": "^3.0.2",
    "karma-failed-reporter": "0.0.3",
    "localize-router": "https://github.com/manzonif/temp-localize-router/archive/a45b7b3f1eebfe82e3093e0b6cd5bb00612e9bb6.tar.gz",
    "mobile-detect": "1.4.1",
    "ngrx-store-localstorage": "5.0.1",
    "ngx-lazy-load-images": "^1.3.1",
    "ngx-translate-parser-plural-select": "1.1.3",
    "preboot": "6.0.0-beta.4",
    "request": "^2.83.0",
    "rxjs": "^6.2.2",
    "rxjs-tslint": "^0.1.5",
    "ts-action": "^6.0.2",
    "ts-action-operators": "^7.0.0",
    "ts-loader": "^4.4.2",
    "ts-md5": "^1.2.4",
    "winston": "^2.4.0",
    "zone.js": "^0.8.26"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^0.7.3",
    "@angular/cli": "^6.1.1",
    "@angular/compiler-cli": "^6.1.1",
    "@angular/flex-layout": "^6.0.0-beta.17",
    "@angular/language-service": "^6.1.1",
    "@compodoc/compodoc": "1.1.3",
    "@ngrx/schematics": "^6.0.1",
    "@storybook/addon-notes": "4.0.0-alpha.14",
    "@storybook/addon-options": "4.0.0-alpha.14",
    "@storybook/addon-viewport": "4.0.0-alpha.14",
    "@storybook/addons": "4.0.0-alpha.14",
    "@storybook/angular": "4.0.0-alpha.14",
    "@types/express": "^4.11.1",
    "@types/express-winston": "^2.4.0",
    "@types/hammerjs": "2.0.34",
    "@types/jasmine": "2.5.38",
    "@types/lodash": "^4.14.95",
    "@types/node": "6.0.60",
    "@types/request": "^2.47.0",
    "@types/storybook__addon-notes": "^3.3.1",
    "angular-playground": "1.7.1",
    "babel-core": "^6.26.0",
    "codelyzer": "4.2.1",
    "concurrently": "^3.5.1",
    "enhanced-resolve": "3.3.0",
    "jasmine-core": "2.5.2",
    "jasmine-marbles": "^0.3.1",
    "jasmine-spec-reporter": "3.2.0",
    "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",
    "karma-verbose-reporter": "0.0.6",
    "localstorage-polyfill": "^1.0.1",
    "node-pre-gyp": "0.6.39",
    "node-sass": "4.9.2",
    "rxjs-compat": "^6.2.2",
    "rxjs-tslint-rules": "^3.9.0",
    "sass-lint": "1.12.1",
    "source-map-explorer": "1.5.0",
    "ts-node": "4.1.0",
    "tslint": "5.9.1",
    "tslint-eslint-rules": "4.1.1",
    "typescript": "^2.9.0",
    "webpack-bundle-analyzer": "2.9.1",
    "webpack-cli": "^3.0.8"
  },

@deerua
Copy link

deerua commented Aug 15, 2018

After some changes we have 183 ERRORS
Most of it

Module not found: Error: Can't resolve '@angular/router.ngfactory' 

and all material components

@clydin
Copy link
Member

clydin commented Aug 15, 2018

^6.1.1 means install the latest version of 6.x (with a minimum of 6.1.1) which would be 6.1.2

As a temporary workaround, you can fix @angular/compiler to 6.1.1 (note you will receive peer dependency warnings). You can also stay on Angular 6.1.1 as a whole until a fix is available. Also when building for production, moving to consistent versions would be advised (i.e., all 6.1.1 or all 6.1.2).

Note also that CLI and @angular-devkit/build-angular can be at their latest version.

@deerua
Copy link

deerua commented Aug 15, 2018

thx @clydin
i have checked node_modules manually before and all the deps. was 6.1.1 :) in package.json, strange
but after strict version all become fine (looks like)

@Stantmn
Copy link

Stantmn commented Aug 15, 2018

The same issue after update to 6.1.2.
Downgrade to 6.1.1 helped

@darkguy2008
Copy link

Been fighting with this for about a week now. I can confirm this package.json fixes all issues (made with npm i -g @angular/cli@6.1.1 then manually edited):

{
  "name": "admin",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve --aot",
    "build": "ng build --aot --prod"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "6.1.1",
    "@angular/common": "6.1.1",
    "@angular/compiler": "6.1.1",
    "@angular/core": "6.1.1",
    "@angular/forms": "6.1.1",
    "@angular/http": "6.1.1",
    "@angular/platform-browser": "6.1.1",
    "@angular/platform-browser-dynamic": "6.1.1",
    "@angular/router": "6.1.1",
    "core-js": "^2.5.4",
    "rxjs": "^6.0.0",
    "zone.js": "~0.8.26"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "0.7.0",
    "@angular/cli": "6.1.1",
    "@angular/compiler-cli": "6.1.1",
    "@angular/language-service": "6.1.1",
    "@types/node": "~8.9.4",
    "ts-node": "~5.0.1",
    "tslint": "~5.9.1",
    "typescript": "~2.7.2"
  }
}

@iamjoyce
Copy link

@Charlyo @Andrii-A Did you check whether you've installed angular as a global package and if it's upgraded to 6.x?

npm ls --global --depth=0

@Charlyo
Copy link

Charlyo commented Sep 28, 2018

@Charlyo @Andrii-A Did you check whether you've installed angular as a global package and if it's upgraded to 6.x?

npm ls --global --depth=0

This is the output that I get

/usr/local/lib
├── @angular/cli@6.2.3
├── interface2@0.0.0 -> /Users/charlyo/ANIS/interface
└── npm@6.4.1

npm ERR! peer dep missing: @angular/core@^5.0 || ^4.0 || ^2.0, required by d3-ng2-service@2.2.0
npm ERR! peer dep missing: typescript@~2.4.0 || ~2.5.0 || ~2.6.0 || ~2.7.0, required by @ngtools/webpack@6.0.8

@Andrii-A
Copy link

C:\Users\a\AppData\Roaming\npm
+-- @angular/cli@6.0.8
+-- angular-cli@1.0.0-beta.19-3
+-- bower@1.8.2
+-- generator-ng2-webpack@0.6.6
+-- grunt-cli@1.2.0
+-- grunt-init@0.3.2
+-- npm@6.4.1
+-- windows-build-tools@1.3.2
`-- yo@1.8.5

@odahcam
Copy link

odahcam commented Oct 11, 2018

Same here (Angular 6.1.10):

$ ng -v

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


Angular CLI: 6.2.4
Node: 8.11.1
OS: win32 x64
Angular: 6.1.10

Ouput:

i 「wdm」: Compiled successfully.
i 「wdm」: Compiling...
C:\PROJECT_PATH\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:92
                                        throw data[0];
                                        ^

Error: ENOENT: no such file or directory, stat 'C:\PROJECT_PATH\src\app\@shared\sr-only\sr-only.component.ngfactory.js'
    at Object.fs.statSync (fs.js:948:11)

@smasala
Copy link

smasala commented Oct 12, 2018

Workaround angular-cli@6.0.0
Workaround angular-cli@6.2.5

@fetis
Copy link

fetis commented Oct 16, 2018

I have the same issue with angular-cli@6.2.5 and compiler@6.1.10

It fails with error
Error: ENOENT: no such file or directory, stat '/Users/sergeyf/job/case-management-frontend/src/app/shared/components/cost-center-image/cost-center-image.component.ngfactory.js'

What's unusual here we use an inline template, not standalone. Might be this a problem?

#12260 (comment) this helped me out

@turoo12
Copy link

turoo12 commented Oct 16, 2018

In our case, we were optimizing the ng serve which threw similar error message.

Instead of:

           "dev": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.dev.ts"
                }
              ],
              "optimization": false,
              "outputHashing": "all",
              "sourceMap": false,
              "extractCss": true,
              "namedChunks": false,
              "aot": true,
              "extractLicenses": true,
              "vendorChunk": false,
              "buildOptimizer": true
            },

Use:

           "localdev": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.localdev.ts"
                }
              ]
            }

@selvam326
Copy link

angular/quickstart#365 (comment)
plz see the issue reply me.

@lincolnmandal
Copy link

ERROR in ./src/main.ts
Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in 'D:\2019\DCubeBillingSystem\DCubeHotelSystem\app\src'
ERROR in Error: Cannot determine the module for class ReportDashboardComponent in D:/2019/DCubeBillingSystem/DCubeHotelSystem/app/src/app/components/ReportDashboard/reportdashboard.component.ts! Add ReportDashboardComponent to the NgModule to fix it.

FrederikSchlemmer pushed a commit to FrederikSchlemmer/angular that referenced this issue Jan 3, 2019
… ngfactory & ngsummary files (angular#25604)

Workaround was added in angular#25335. It was necessary for .ngfactory & .ngsummary files to have proper AMD module names starting with @angular when building angular downstream from source using Bazel. The underlying issue has been resolved in the compiler and these files now get proper AMD module names without the need for this workaround. The workaround had an unexpected consequence angular/angular-cli#11835 which is fixed by its removal.

PR Close angular#25604
@artuska
Copy link

artuska commented Feb 20, 2019

Issue still exists when ng build --aot.
Issue still exists when ng serve --aot.

Angular CLI: 7.3.2
Node: 10.0.0
OS: darwin x64
Angular: 7.2.5
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.2
@angular-devkit/build-angular     0.13.2
@angular-devkit/build-optimizer   0.13.2
@angular-devkit/build-webpack     0.13.2
@angular-devkit/core              7.3.2
@angular-devkit/schematics        7.3.2
@angular/cli                      7.3.2
@ngtools/webpack                  7.3.2
@schematics/angular               7.3.2
@schematics/update                0.13.2
rxjs                              6.4.0
typescript                        3.2.4
webpack                           4.29.0

@JWBrownie
Copy link

JWBrownie commented Feb 22, 2019

I have the same issue as @artuska with the same specs.

Angular CLI: 7.3.3
Node: 8.12.0
OS: win32 x64
Angular: 7.2.6
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.3
@angular-devkit/build-angular     0.13.3
@angular-devkit/build-optimizer   0.13.3
@angular-devkit/build-webpack     0.13.3
@angular-devkit/core              0.7.5
@angular-devkit/schematics        0.7.5
@angular/cdk                      7.3.3
@angular/cli                      7.3.3
@angular/flex-layout              7.0.0-beta.23
@angular/material                 7.3.3
@ngtools/json-schema              1.1.0
@ngtools/webpack                  7.3.3
@schematics/angular               7.3.3
@schematics/update                0.13.3
ng-packagr                        4.7.1
rxjs                              6.4.0
typescript                        3.2.4
webpack                           4.29.0

@artuska
Copy link

artuska commented Feb 23, 2019

@JWBrownie If you have this type of error probably you have upgraded from Angular 5 to 6 or 7.

Replace "rootDir": "./src", in your tsconfig.json file to "rootDir": "./", or just remove this parameter completely.

@artuska
Copy link

artuska commented Feb 23, 2019

See also #13721

@gatsbyz
Copy link

gatsbyz commented Feb 27, 2019

@artuska VERIFIED. Worked for me. Thank you from NYC.

@andrewantar
Copy link

Still having this issue on Angular 7.2
Only with ng build or serve --aot or --prod, I get: .ngfactory.js Module not found
Any help? I see a 'fixed by Ivy' tag applied - would I have to wait for Ivy?

@gatsbyz
Copy link

gatsbyz commented Mar 19, 2019

@andrewantar try removing optimization flags in angular.json

@andrewantar
Copy link

@gatsbyz Set them to false and also tried removing the params, and still same error..

@gatsbyz
Copy link

gatsbyz commented Mar 19, 2019

@andrewantar And you've tried removing this from your tsconfig.json -> "rootDir": "./src"

@sridhar-natuva
Copy link

If your tsconfig.json has this path. remove and try it. It worked for me.

"paths": { "@angular/*": ["../node_modules/@angular/*"] },

@alvaroarandaj
Copy link

If your tsconfig.json has this path. remove and try it. It worked for me.

"paths": { "@angular/*": ["../node_modules/@angular/*"] },

It works like black magic mate!!!!!!!

@bishwa-poudel
Copy link

bishwa-poudel commented Jul 27, 2019

I am still getting error in Angular 7.2.15 while building using --aot flag. Normal build is working fine.
The error message looks like:

ERROR in src\app\Test.component.html(6,8): : Property 'sort' does not exist on type 'TestComponent'.

src\app\Test.component.html(3,74): : Property 'allowUnsort' does not exist on type 'TestComponent'.

It is not recognizing any of the kendo grid properties. My kendo grid html looks like this:

<kendo-grid #grid [kendoGridBinding]="gridData | async" [pageSize]="10" [pageable]="true" [filterable]="true"
  [groupable]="true" [resizable]="true" [reorderable]="true" [filterable]="true" [columnMenu]="true"
  [rowClass]="rowCallback" (dataStateChange)="onDataStateChange($event)" [sortable]="{
    allowUnsort: allowUnsort,
    mode: multiple ? 'multiple' : 'single'
    }" [sort]="sort" (sortChange)="sortChange($event)">

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.