Tomas Rimkus

Also, here are few recommendations to improve initial app load time: * Use gzip compression * Set "cache-control" and "expires" headers: ``` cache-control: max-age=31536000 expires: Sat, 16 May 2020 09:38:43...

> And from my understanding even if we import libraries without targetting the specific destination, it should be handled by tree-shaking automatically, isn't it? It should but with DevExtreme Angular...

@StevenFewster Try to make the same test with textbox or some other smaller component. And no, Tree Shaking is not supported according to one of the developers. See issue #353.

@OmniAndy you have to import everything from "devextreme-angular" library using long paths ("devextreme-angular/ui/(control name)" or similar) from specific sub-folders, no matter if it's UI module, component or "DxServerTransferStateModule". If you...

@OmniAndy we also use the data grid (and many other widgets), but we don't generate separate vendor.js - everything's included in main.js. The output looks like this: ``` $ ng...

@OmniAndy here is the config we use: ``` "production": { "fileReplacements": [ { "replace": "src/environments/environment.ts", "with": "src/environments/environment.prod.ts" } ], "optimization": true, "outputHashing": "all", "sourceMap": false, "extractCss": true, "namedChunks": false, "aot":...

That's not only scheduler issue. There are a lot of other DX Angular components which have this problem. A simple workaround is to use arrow function, so you can still...

Maybe you should try binding text property? ```html ```

There seems to be some issue when the elements with box-shadow are not nested in other elements.

@niklasvh Here is an example which is a bit more relevant to me and not only shows issues with box-shadow rendering but also a regression since RC1 with border rendering:...