Kendo-angular: Execute build prod failed with grid filters

[nlgi]

I'm submitting a...

• Bug report

Current behavior

In chrome console, on pages with grid and filters enabled, I get the error "i.a.merge is not a function"
No problem with grid without filters.
Only with build prod, in the main bundle js file.

Minimal reproduction of the problem with instructions

+-- @agm/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @angular/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]

Browser:

• Chrome (desktop) version 63

System:

• TypeScript version: 2.6.2
• Node version:6.10.1
• Platform: Windows

Many thanks for any help!

[kotva006]

I get this same exact issue, though i haven't been able to reproduce it outside of our build.

[kotva006]

We found a work around by turning off the build optimizer (--build-optimizer=false)
Try adding that flag to your ng build to see if it helps.

[nlgi]

Yes, working with --build-optimizer=false (and @progress/[email protected])

[tsvetomir]

Should be working after updating to the latest package versions, see #1244

[nlgi]

It's not working with 2.0.1.
Ok with --build-optimizer=false

Many thanks for your feedback

[tsvetomir]

Please make sure that all packages are at the latest versions and you don't get "UNMET PEER DEPENDENCY" errors on "npm install".

You can use npm-check-updates to automatically take the latest version:

npm install -g npm-check-updates
ncu -u -f /^@progress/

[nlgi]

yes I'm using ncu (awesome package!)
"All dependencies match the latest package versions :)"
No "UNMET PEER DEPENDENCY".

I tried to delete node_modules folder and reinstall: same error.

[tsvetomir]

Can you check the RxJS usage in your project? Particularly global operators should be replaced with pipeable operators.

Also, can you paste the output from npm ls --depth 0 just to double check?

[tsvetomir]

One last thing, remove package-lock.json and reinstall the packages if you haven't tried that already.

[nlgi]

Oh! Looks like it was package-lock.json.

Many thanks!