angular/cli: 1.5.0 - 1.6.0
angulat/core: 5.0.0
After update angular and angular/cli versions I get error "TypeError: Cannot read property 'pointers' of undefined".
If I use the 1.4.* version with angular 4, everything works fine
Using your repro, I had to first remove implements AfterViewInit from src/app.component.ts because it was not implemented correctly.
Then while running npm run ng -- serve --prod --sm I was able to see this error:
mouse.js:24 Uncaught TypeError: Cannot set property 'pointerId' of undefined
Then I updated versions to latest ones ("@angular/cli": "1.6.2", "devextreme": "17.2.4" and "devextreme-angular": "17.2.4") and the error went away. I'm not sure where the problem was but latest versions seems to have fixed it.
@filipesilva it is not working on my side( Can you re-open the issue?
Thanks for getting back to me, I'm reopening. I tried to reproduce with a newer version of uglify-es because it seems it's causing problems in https://github.com/angular/angular-cli/issues/8997. I now see Uncaught TypeError: Cannot set property 'pointerId' of undefined even with updated versions of other packages.
Can you please tell me what do you see on your machine when you run npm ls uglify-es?
For now you can run this command to use an older version of uglify-es where the error does not occur:
npm i [email protected] --save-exact && rm -rf package-lock.json node_modules && npm i && npm ls uglify-es
The result of the command execution:
-- @angular/[email protected]
-- [email protected]
-- [email protected]
Thanks for the workaround!
Have been debugging this for a couple of hours and the best I can say is that the class inheritance mechanism that devextreme uses breaks down when passed through [email protected].
https://github.com/mishoo/UglifyJS2/issues/2663 might be related, I noticed some of that function inlining in the code I was investigating.
The bug causing these problems is reported with repros at https://github.com/mishoo/UglifyJS2/issues/2663.
I'm going to close this issue in favor of #8997 since the problem is the same.
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._
Most helpful comment
For now you can run this command to use an older version of
uglify-eswhere the error does not occur: