Virtualisation is not working in kendo-Grid - kendo-ui

I have used a kendo virtualization local data sample in my application as it is for testing the virtualization scroll bar but it's not working
Virtualization with Local data from the official page
FYI instead of creating my own data, I have used the same kendo sample of virtualization with the local data sample from this doc Kendo virtualization with Local Data & following is the StackBlitz for same
Following is my package.json in case
"dependencies": {
"#angular/animations": "~12.2.0",
"#angular/cdk": "^12.2.0",
"#angular/common": "~12.2.0",
"#angular/compiler": "~12.2.0",
"#angular/core": "~12.2.0",
"#angular/forms": "~12.2.0",
"#angular/localize": "~12.2.0",
"#angular/material": "^11.2.3",
"#angular/platform-browser": "~12.2.0",
"#angular/platform-browser-dynamic": "~12.2.0",
"#angular/router": "~12.2.0",
"#progress/kendo-angular-buttons": "^6.0.0",
"#progress/kendo-angular-common": "^2.0.0",
"#progress/kendo-angular-dateinputs": "^5.0.0",
"#progress/kendo-angular-dialog": "^5.2.3",
"#progress/kendo-angular-dropdowns": "^5.0.0",
"#progress/kendo-angular-excel-export": "^4.0.0",
"#progress/kendo-angular-grid": "^5.5.1",
"#progress/kendo-angular-icons": "^0.4.4",
"#progress/kendo-angular-indicators": "^1.1.1",
"#progress/kendo-angular-inputs": "^7.0.0",
"#progress/kendo-angular-intl": "^3.0.0",
"#progress/kendo-angular-l10n": "^3.0.0",
"#progress/kendo-angular-label": "^3.0.0",
"#progress/kendo-angular-layout": "^6.3.6",
"#progress/kendo-angular-menu": "^3.0.3",
"#progress/kendo-angular-pager": "^3.0.3",
"#progress/kendo-angular-pdf-export": "^3.0.0",
"#progress/kendo-angular-popup": "^4.0.0",
"#progress/kendo-angular-progressbar": "^2.0.0",
"#progress/kendo-angular-toolbar": "^4.1.3",
"#progress/kendo-angular-tooltip": "^3.1.6",
"#progress/kendo-angular-treeview": "^5.0.0",
"#progress/kendo-data-query": "^1.0.0",
"#progress/kendo-drawing": "^1.0.0",
"#progress/kendo-licensing": "^1.0.2",
"#progress/kendo-svg-icons": "^0.1.2",
"#progress/kendo-theme-default": "^4.42.0",
"rxjs": "~6.6.0",
"tslib": "^2.3.0",
"zone.js": "~0.11.4"
},
Please let me know if this is related to the lower kendo package versions because in my case the page change event is not calling when i scroll the grid
This is how my application behaves
Application behavior after running the application

Related

Stuck on build error on migration of basic Tabs from {N} 6 to 8

We have an app written in NativeScript Angular and based on BottomNavigation and TabView.
I've posted before about issues we have had building our app after migrating from NativeScript 6 to 8.
I can't share our code base so I have taken the legacy code in {N} 6 and stripped out all of our own components to leave just the bare bones.
There is a public repo here: https://github.com/syborp/testapp
It builds and runs fine in {N} 6 and there is a screenshot on the GitHub README.
When we migrate to {N} 8 we keep ending up at this error.
Searching for devices...
Preparing project...
webpack is watching the files...
C:\Users\user\testapp\node_modules\#angular\compiler-cli\ngcc\src\entry_point_finder\targeted_entry_point_finder.js:40
throw new Error("The target entry-point \"" + invalidTarget.entryPoint.name + "\" has missing dependencies:\n" +
^
Error: The target entry-point "undefined" has missing dependencies:
- nativescript-angular/element-registry
at TargetedEntryPointFinder.findEntryPoints (C:\Users\user\testapp\node_modules\#angular\compiler-cli\ngcc\src\entry_point_finder\targeted_entry_point_finder.js:40:23)
at C:\Users\user\testapp\node_modules\#angular\compiler-cli\ngcc\src\execution\analyze_entry_points.js:29:41
at SingleProcessExecutorSync.SingleProcessorExecutorBase.doExecute (C:\Users\user\testapp\node_modules\#angular\compiler-cli\ngcc\src\execution\single_process_executor.js:28:29)
at C:\Users\user\testapp\node_modules\#angular\compiler-cli\ngcc\src\execution\single_process_executor.js:57:59
at SyncLocker.lock (C:\Users\user\testapp\node_modules\#angular\compiler-cli\ngcc\src\locking\sync_locker.js:34:24)
at SingleProcessExecutorSync.execute (C:\Users\user\testapp\node_modules\#angular\compiler-cli\ngcc\src\execution\single_process_executor.js:57:27)
at Object.mainNgcc (C:\Users\user\testapp\node_modules\#angular\compiler-cli\ngcc\src\main.js:74:25)
at Object.process (C:\Users\user\testapp\node_modules\#angular\compiler-cli\ngcc\index.js:29:23)
at NgccProcessor.processModule (C:\Users\user\testapp\node_modules\#ngtools\webpack\src\ngcc_processor.js:175:16)
at C:\Users\user\testapp\node_modules\#ngtools\webpack\src\ivy\host.js:146:18
at C:\Users\user\testapp\node_modules\#ngtools\webpack\src\ivy\host.js:76:24
at Array.map (<anonymous>)
at Object.host.resolveModuleNames (C:\Users\user\testapp\node_modules\#ngtools\webpack\src\ivy\host.js:74:32)
at actualResolveModuleNamesWorker (C:\Users\user\testapp\node_modules\typescript\lib\typescript.js:109497:133)
at resolveModuleNamesWorker (C:\Users\user\testapp\node_modules\typescript\lib\typescript.js:109760:26)
at resolveModuleNamesReusingOldState (C:\Users\user\testapp\node_modules\typescript\lib\typescript.js:109857:24)
Executing webpack failed with exit code 1.
It sounds like the entry point main.ts cannot be found but I think it looks ok in package.json.
"description": "Test App",
"license": "SEE LICENSE IN <your-license-filename>",
"readme": "NativeScript Application",
"repository": "<fill-your-repository-here>",
"scripts": {
"lint": "tslint \"app/**/*.ts\""
},
"dependencies": {
"#angular/animations": "^12.2.5",
"#angular/common": "^12.2.5",
"#angular/compiler": "^12.2.5",
"#angular/core": "^12.2.5",
"#angular/forms": "^12.2.5",
"#angular/http": "8.0.0-beta.10",
"#angular/platform-browser": "^12.2.5",
"#angular/platform-browser-dynamic": "^12.2.5",
"#angular/router": "^12.2.5",
"#master.technology/permissions": "^2.0.1",
"#nativescript/angular": "^12.2.0",
"#nativescript/core": "~8.1.1",
"#nativescript/fingerprint-auth": "^8.0.0",
"nativescript": "^6.5.0",
"nativescript-app-sync": "^2.0.0",
"nativescript-bottom-navigation": "^2.0.5",
"nativescript-camera": "^4.0.2",
"nativescript-drop-down": "^5.0.6",
"nativescript-fancyalert": "^3.0.9",
"nativescript-fingerprint-auth": "^7.0.2",
"nativescript-fontawesome": "^1.0.0",
"nativescript-gradient": "^2.0.1",
"nativescript-imagepicker": "^7.1.0",
"nativescript-iqkeyboardmanager": "^1.5.1",
"nativescript-modal-datetimepicker": "^1.1.4",
"nativescript-pdf-view": "^2.1.0",
"nativescript-permissions": "^1.3.12",
"nativescript-theme-core": "~1.0.4",
"nativescript-toast": "^1.4.6",
"nativescript-ui-listview": "^10.0.2",
"reflect-metadata": "~0.1.10",
"ruby": "^0.6.1",
"rxjs": "~7.3.0",
"zone.js": "~0.11.4"
},
"devDependencies": {
"#angular-devkit/build-angular": "^13.2.5",
"#angular/cli": "^12.2.5",
"#angular/compiler-cli": "^12.2.5",
"#nativescript/android": "~8.1.1",
"#nativescript/webpack": "~5.0.0",
"#ngtools/webpack": "^12.2.5",
"#types/node": "14.6.2",
"babel-traverse": "6.26.0",
"babel-types": "6.26.0",
"babylon": "6.18.0",
"codelyzer": "~4.5.0",
"extract-text-webpack-plugin": "~3.0.2",
"lazy": "1.0.11",
"sass": "~1.39.0",
"tslint": "~5.12.1",
"typescript": "~4.3.5",
"uglifyjs-webpack-plugin": "^2.2.0"
},
"main": "./app/main.ts"
}
Or is it a webpack issue?
Any advice much appreciated.
TIA.

object(...) is not a function when publish angular 11 application

I had application in angular 6 with .net core 2.1 and now I upgraded into 11 with .Net 5 and its works fine in my local system but when I published to Azure virtual machine at that time it is giving me below error, I already update necessary package like Angular CLI and .NET runtime at vitual machine so not sure why this error appear
here is my package.json
"dependencies": {
"#agm/core": "1.0.0",
"#angular/animations": "^11.2.8",
"#angular/cdk": "^11.2.7",
"#angular/common": "11.2.8",
"#angular/compiler": "11.2.8",
"#angular/core": "11.2.8",
"#angular/forms": "11.2.8",
"#angular/http": "7.2.16",
"#angular/localize": "^11.2.8",
"#angular/platform-browser": "11.2.8",
"#angular/platform-browser-dynamic": "11.2.8",
"#angular/router": "11.2.8",
"#ng-bootstrap/ng-bootstrap": "^9.1.0",
"#nguniversal/module-map-ngfactory-loader": "^5.0.0-beta.8",
"#ngx-translate/core": "^9.1.1",
"#ngx-translate/http-loader": "^2.0.1",
"#progress/telerik-angular-report-viewer": "^11.20.1021",
"#ryancavanaugh/jquery.prettyphoto": "^3.1.14-alpha",
"#types/googlemaps": "^3.43.3",
"#videogular/ngx-videogular": "^3.0.1",
"adal-angular4": "^3.0.16",
"angular-google-charts": "^0.1.6",
"angular-moment": "^1.3.0",
"angular-safeguard": "^2.1.0",
"aspnet-prerendering": "^3.0.1",
"bootstrap": "^4.6.0",
"core-js": "^2.6.12",
"file-saver": "^2.0.5",
"flexslider": "^2.7.2",
"font-awesome": "^4.7.0",
"google-code-prettify": "^1.0.5",
"html2canvas": "^1.0.0-alpha.12",
"jquery": "^3.6.0",
"jquery.easing": "^1.4.1",
"jspdf": "^2.3.1",
"jspdf-autotable": "^3.5.14",
"modernizr": "^3.11.6",
"moment": "^2.29.1",
"moment-timezone": "^0.5.32",
"ng-drag-drop": "5.0.0",
"ng2-pdfjs-viewer": "^5.0.7",
"ngx-material-timepicker": "^3.3.1",
"ngx-sortablejs": "^11.1.0",
"ngx-spinner": "^6.1.2",
"popper.js": "^1.16.1",
"primeflex": "^2.0.0",
"primeicons": "^1.0.0",
"primeng": "^11.3.1",
"rxjs": "^6.6.7",
"rxjs-compat": "^6.6.7",
"sequencejs": "^2.0.0",
"sortablejs": "1.7.0",
"videogular2": "^7.0.2",
"xlsx": "^0.16.9",
"yarn": "^1.22.10",
"zone.js": "^0.10.3"
},
"devDependencies": {
"#angular-devkit/build-angular": "^0.1102.6",
"#angular/cli": "^11.2.6",
"#angular/compiler-cli": "^11.2.8",
"#angular/language-service": "11.2.8",
"#types/core-js": "^0.9.46",
"#types/flexslider": "0.0.2",
"#types/jasmine": "^2.8.17",
"#types/jasminewd2": "^2.0.8",
"#types/jquery": "^3.5.5",
"#types/jspdf": "^1.3.3",
"#types/modernizr": "^3.5.3",
"#types/node": "^6.14.13",
"codelyzer": "^4.5.0",
"jasmine-core": "~2.8.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "^6.3.2",
"karma-chrome-launcher": "~2.2.0",
"karma-coverage-istanbul-reporter": "^1.4.3",
"karma-jasmine": "^1.1.2",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "^7.0.0",
"ts-node": "~4.1.0",
"tslint": "~5.9.1",
"typescript": "4.1.5"
}
Any help would be appreciated
This is likely an issue with one of your dependencies, which you should generally update alongside updating the framework.
I can see "ngx-spinner": "^6.1.2" in your package.json file, can you please check its version as well. It should be 11.0.2, try to install that specific version and check again.

Unexpected EventSource requests after updating Angular 4.4 to 5.2

I am trying to migrate web application I'm working on to Angular 5.2.
Followed the instructions on https://angular-update-guide.firebaseapp.com/ ,
I've been able to run the application in the development mode using 'ng serve -lr' as usually.
However, after application launches, multiple HTTP requests, which weren't triggering on Angular 4.4 are executing and eventually, webpack-dev-server disconnects.
My package.json on Angular 4.4, before update:
"dependencies": {
"#agm/core": "^1.0.0-beta.1",
"#angular/animations": "^4.4.0-RC.0",
"#angular/cdk": "^2.0.0-beta.10",
"#angular/common": "^4.4.4",
"#angular/compiler": "^4.4.4",
"#angular/core": "^4.4.4",
"#angular/forms": "^4.4.4",
"#angular/http": "^4.4.4",
"#angular/material": "^2.0.0-beta.10",
"#angular/platform-browser": "^4.4.4",
"#angular/platform-browser-dynamic": "^4.4.4",
"#angular/router": "^4.4.4",
"#ng-bootstrap/ng-bootstrap": "^1.0.0-beta.5",
"#types/jquery": "^3.2.12",
"angular2-multiselect-dropdown": "^1.3.6",
"angular2-text-mask": "^8.0.4",
"autoprefixer": "^7.1.1",
"bootstrap": "^4.0.0-beta.2",
"core-js": "^2.4.1",
"jquery": "^3.2.1",
"lodash": "^4.17.4",
"moment": "^2.19.1",
"ng2-daterangepicker": "^2.0.12",
"rxjs": "^5.1.0",
"tinymce": "^4.6.7",
"zone.js": "^0.8.4"
}, "devDependencies": {
"#angular/cli": "1.4.5",
"#angular/compiler-cli": "^4.4.4",
"#types/jasmine": "2.5.38",
"#types/node": "~6.0.60",
"codelyzer": "~2.0.0",
"concurrently": "^3.4.0",
"htmlhint-ng2": "0.0.13",
"jasmine-core": "~2.5.2",
"jasmine-spec-reporter": "~3.2.0",
"json-server": "^0.10.1",
"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",
"protractor": "~5.1.0",
"sass-lint": "latest",
"scss-lint": "0.0.0",
"scss-lint-html-reporter": "^0.3.2",
"ts-node": "~2.0.0",
"tslint": "~4.5.0",
"typescript": "~2.2.0"
},
"sasslintConfig": "sass-lint.yml"
}
package.json after update to angular 5.2:
"private": true,
"dependencies": {
"#agm/core": "^1.0.0-beta.2",
"#angular/animations": "^5.2.3",
"#angular/cdk": "^5.1.1",
"#angular/common": "^5.2.3",
"#angular/compiler": "^5.2.3",
"#angular/core": "^5.2.3",
"#angular/forms": "^5.2.3",
"#angular/http": "^5.2.3",
"#angular/material": "^5.1.1",
"#angular/platform-browser": "^5.2.3",
"#angular/platform-browser-dynamic": "^5.2.3",
"#angular/platform-server": "^5.2.3",
"#angular/router": "^5.2.3",
"#ng-bootstrap/ng-bootstrap": "^1.0.0",
"#types/jquery": "^3.2.12",
"angular2-multiselect-dropdown": "^1.3.6",
"angular2-text-mask": "^8.0.4",
"autoprefixer": "^7.2.5",
"bootstrap": "^4.0.0",
"core-js": "^2.5.3",
"file-loader": "^1.1.6",
"jquery": "^3.2.1",
"lodash": "^4.17.5",
"mixpanel-browser": "^2.17.0",
"moment": "^2.19.1",
"ng2-daterangepicker": "^2.0.12",
"node-sass": "^4.7.2",
"popper.js": "^1.12.9",
"rxjs": "^5.5.6",
"tinymce": "^4.7.6",
"zone.js": "^0.8.20"
},
"devDependencies": {
"#angular/cli": "^1.6.7",
"#angular/compiler-cli": "^5.2.3",
"#types/jasmine": "2.5.38",
"#types/node": "^6.0.96",
"codelyzer": "^4.1.0",
"concurrently": "^3.5.1",
"htmlhint-ng2": "0.0.13",
"jasmine-core": "~2.5.2",
"jasmine-spec-reporter": "~3.2.0",
"json-server": "^0.10.1",
"karma": "^2.0.0",
"karma-chrome-launcher": "~2.1.1",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^0.2.0",
"karma-jasmine": "^1.1.1",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~5.1.0",
"sass-lint": "latest",
"scss-lint": "0.0.0",
"scss-lint-html-reporter": "^0.3.2",
"ts-node": "~2.0.0",
"tslint": "^5.9.1",
"typescript": "^2.6.2",
"webpack": "^3.10.0"
},
"sasslintConfig": "sass-lint.yml"
}
Unexpected requests in the network tab of Chrome Dev Tools
Browser console errors
Similar issue posted on angular-cli GitHub page
Seems like the problem was in webpack live reloading. Solved it by adding parameter to launch script, now it is
ng serve --public-host http://localhost:4200/ -lr

Jasmine unit tests run in Chrome but not in PhantomJs

I have a project that was created with the angular cli. I generate new components with the cli and even the most basic tests fail when using PhantomJS with the following stack.
× should create an instance
PhantomJS 2.1.1 (Windows 8 0.0.0)
Failed: undefined is not a constructor (evaluating 'attr.name.startsWith(_I18N_ATTR_PREFIX)')
http://localhost:9876/_karma_webpack_/vendor.bundle.js:48660:70
filter#[native code]
_visitAttributesOf#http://localhost:9876/_karma_webpack_/vendor.bundle.js:48660:24
visitElement#http://localhost:9876/_karma_webpack_/vendor.bundle.js:48603:32
visit#http://localhost:9876/_karma_webpack_/vendor.bundle.js:40053:62
http://localhost:9876/_karma_webpack_/vendor.bundle.js:48595:59
forEach#[native code]
visitElement#http://localhost:9876/_karma_webpack_/vendor.bundle.js:48594:31
visit#http://localhost:9876/_karma_webpack_/vendor.bundle.js:40053:62
http://localhost:9876/_karma_webpack_/vendor.bundle.js:48595:59
forEach#[native code]
visitElement#http://localhost:9876/_karma_webpack_/vendor.bundle.js:48594:31
visit#http://localhost:9876/_karma_webpack_/vendor.bundle.js:40053:62
http://localhost:9876/_karma_webpack_/vendor.bundle.js:48595:59
forEach#[native code]
visitElement#http://localhost:9876/_karma_webpack_/vendor.bundle.js:48594:31
I suspect that there is some incompatibility with my combination of npm packages. Here is my package.json
"dependencies": {
"#angular/animations": "^5.0.2",
"#angular/common": "^5.0.2",
"#angular/compiler": "^5.0.2",
"#angular/core": "^5.0.2",
"#angular/forms": "^5.0.2",
"#angular/http": "^5.0.2",
"#angular/platform-browser": "^5.0.2",
"#angular/platform-browser-dynamic": "^5.0.2",
"#angular/router": "^5.0.2",
"angularfire2": "^5.0.0-rc.4",
"core-js": "^2.4.1",
"crds-styles": "^1.3.1",
"firebase": "^4.6.2",
"intl": "^1.2.5",
"ng2-toastr": "^4.1.2",
"ngx-bootstrap": "1.9.3",
"rxjs": "^5.5.2",
"zone.js": "^0.8.14"
},
"devDependencies": {
"#angular/cli": "1.5.4",
"#angular/compiler-cli": "^5.0.2",
"#angular/language-service": "^5.0.2",
"#types/jasmine": "2.5.38",
"#types/jasminewd2": "~2.0.2",
"#types/node": "~6.0.89",
"codelyzer": "^4.0.1",
"firebase-tools": "^3.15.4",
"jasmine-core": "~2.6.0",
"jasmine-spec-reporter": "~4.2.0",
"karma": "~1.7.0",
"karma-chrome-launcher": "~2.1.1",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^1.2.1",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"karma-mocha-reporter": "2.2.4",
"karma-phantomjs-launcher": "^1.0.4",
"karma-teamcity-reporter": "^1.0.0",
"prettier": "^1.9.2",
"protractor": "~5.1.2",
"replace": "^0.3.0",
"ts-node": "~2.0.0",
"tslint": "~5.7.0",
"tslint-config-prettier": "^1.6.0",
"typescript": "2.5.3"
}
Any ideas?
You use the startsWith() method which was introduced in ECMAScript 6. Phantom JS currently does not support this JS version. You can see the current status here : https://github.com/ariya/phantomjs/issues/14506 . You could use ChromeHeadless instead or skip the files that contain ES6 code (but they won't be tested).

reusable custom-filter components reset after dropdownlist lost focus

I'm trying to use the example of Reusable Custom-Filter Components. If I check the provided Plunker example I changed the filter. After I clicked somewhere else the filter is reseted to default item. How can I achieve that the filter stays so I can do other stuff on grid?
Here an excerpt from package.json:
"#angular/animations": "^5.0.4",
"#angular/common": "~5.0.0",
"#angular/compiler": "~5.0.0",
"#angular/core": "~5.0.0",
"#angular/forms": "~5.0.0",
"#angular/http": "~5.0.0",
"#angular/platform-browser": "~5.0.0",
"#angular/platform-browser-dynamic": "~5.0.0",
"#angular/router": "~5.0.0",
"#angular/upgrade": "~5.0.0",
"#progress/kendo-angular-buttons": "^2.0.0",
"#progress/kendo-angular-dateinputs": "^1.4.1",
"#progress/kendo-angular-dialog": "^1.3.0",
"#progress/kendo-angular-dropdowns": "^1.2.2",
"#progress/kendo-angular-excel-export": "^1.0.4",
"#progress/kendo-angular-grid": "^1.6.0",
"#progress/kendo-angular-inputs": "^1.3.3",
"#progress/kendo-angular-intl": "^1.3.0",
"#progress/kendo-angular-l10n": "^1.0.5",
"#progress/kendo-data-query": "^1.1.0",
"#progress/kendo-drawing": "^1.4.0",
"#progress/kendo-theme-default": "^2.43.2",
"angular2-jwt": "^0.2.3",
"angular2-moment": "^1.7.0",
"angular2-toaster": "^4.0.1",
"animate.css": "3.5.2",
"awesome-bootstrap-checkbox": "1.0.0",
"bootstrap": "4.0.0-beta",
"cldr-data": "^32.0.0",
"core-js": "^2.4.1",
"font-awesome": "4.7.0",
"glyphicons-halflings": "1.9.0",
"ng2-redux": "^5.1.2",
"ngx-bootstrap": "2.0.0-beta.5",
"pace": "git://github.com/HubSpot/pace.git#v0.7.7",
"popper.js": "1.12.5",
"redux": "^3.7.2",
"reflect-metadata": "0.1.10",
"rxjs": "^5.5.0",
"tassign": "^1.0.0",
"widgster": "0.0.3",
"zone.js": "^0.8.4"
There was an issue with the DropDownList losing the value on blur, but it is fixed in the latest version of the DropDowns package:
DOCS Changelog
Upgrading to the latest versions of the Kendo UI for Angular packages should resolve the described problem.

Resources