Versions Compatibility Table

index

• Angular-Slickgrid & Slickgrid-Universal compatibility
• ngx-translate compatibility
• Build Warnings (Angular >=8.x)
• Angular >=12.x with WebPack 5 polyfill error

---

Angular-Slickgrid and Slickgrid-Universal

Whenever you want to update your Angular-Slickgrid, you should also always update any Slickgrid-Universal package you might have at the same time as your Angular-Slickgrid and you should be fine. If you have problem, below is a list of compatible versions.

Why do Angular-Slickgrid and Slickgrid-Universal versions go hand in hand?

It's not on purpose and I believe the biggest reason is because Angular-Slickgrid extends (GridOption) interface from Slickgrid-Universal and TypeScript seems to be detecting invalid types and throwing a bunch of errors when they're not updated on the same day, I never figured out a way to avoid these TypeScript errors.

Angular-Slickgrid	Slickgrid-Universal	Angular requirement	Migration Guide	Release Date
6.6.2	3.6.0	16+
6.5.1	3.5.1	16+
6.4.0	3.4.2	16+
6.3.1	3.3.2	16+
6.1.0	3.1.0	16+
6.0.1	3.0.1	16+	[Migration Guide to v6.x]	2023-07-01
5.6.4	2.6.4	14+
5.5.1	2.5.0	14+
5.4.1	2.4.1	14+
5.3.0	2.3.0	14+
5.2.2	2.2.2	14+
5.1.3	2.1.3	14+
5.1.1	2.1.1	14+
5.0.2	2.0.0	14+	Migration Guide to v5.x	2022-10-17
4.3.1	1.4.0	13+
4.2.7	1.3.7	13+
4.1.4	1.2.6	13+
4.0.0	1.1.1	13+	Migration Guide to v4.x	2021-12-11
3.3.2	0.19.2	12+	Migration Guide to v3.x	2021-07-2

ngx-translate Compatibility

If you are facing any issues with ngx-translate library while building your Angular Project. You need to make sure that @ngx-translate/core is part of your dependencies, that is also true even when using a single Locale, that is because it is a peerDependency of Angular-Slickgrid. The reason is because, we use @Optional() TranslateService in the lib and for that to work, we still need it to be installed, but don't worry it should still be removed by the tree shaking process after a running a production build. See their version compatibility table below

Angular Version	@ngx-translate/core
13+ (Ivy only)	14+
10-13	13+
8-9	12+
7	11+

---

ngcc Build Warnings (Angular >=8.0 && <16.0)

You might get warnings about SlickGrid while doing a production build, most of them are fine and the best way to fix them, is to simply remove/ignore the warnings, all you have to do is to add a file named ngcc.config.js in your project root (same location as the angular.json file) with the following content (you can also see this commit which fixes the Angular-Slickgrid-Demos prod build):

module.exports = {
  packages: {
    'angular-slickgrid': {
      ignorableDeepImportMatchers: [
        /assign-deep/,
        /dequal/,
        /slickgrid\//,
        /flatpickr/,
      ]
    },
  }
};

Angular 12 with WebPack 5 - how to fix polyfill error

Since Angular 12 switched to WebPack 5, you might get some new errors and you will need to add some polyfills manually to get the Excel Builder (Excel Export) to work.

The error you might get

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

Steps to fix it

1. npm install stream-browserify
2. Add a path mapping in tsconfig.json:

{
  ...
  "compilerOptions": {
    "paths": {
      "stream": [ "./node_modules/stream-browserify" ]
    },

3. Add stream (and any other CJS deps) to allowedCommonJsDependencies in your angular.json config:

"options": {
  "allowedCommonJsDependencies": [
    "autocompleter",
    "dompurify",
    "excel-builder-webpacker",
    "fetch-jsonp",
    "flatpickr",
    "slickgrid",
    "stream"
  ],
],