Asman Umbetov

have the similar issue after updating plugins, had to remove `cmp-nvim-ultisnips` from the plugin list im running neovim version v0.7.2 [link](https://s3.us-west-2.amazonaws.com/secure.notion-static.com/628a17a6-1a1e-4c68-928e-316d1d5351dc/init.vim?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIAT73L2G45EIPT3X45%2F20220812%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20220812T085638Z&X-Amz-Expires=86400&X-Amz-Signature=0ab9064d78c5e1eaf8322d0893561e60ff05101d017107db4d088974759b931a&X-Amz-SignedHeaders=host&response-content-disposition=filename%20%3D%22init.vim%22&x-id=GetObject) to my vim.init

sure, actually no steps are needed to reproduce, in my case the error happens any time I try typing anything in the insert mode or altering the text in any...

Hey @quangnguyen30192, i switched completely to vsnip for the time being, so I won't help with debugging, sorry. but here's my init.vim configuration, sorry for the broken link, didn't know...

Hi! Are there any updates regarding this issue? I've ran into this issue `2.2.6` and it seems to be relevant on the latest patch too. Also, to add to the...

btw seems like the demo is broken and has the same issue on the `--gradient-with-var`

@georgianafilote-pxo As far as I can tell this issue is solely related to the Jest's compilation process and the way it transforms the code before running it. I don't think...

@georgianafilote-pxo that's pretty incredible what you did. It does look like the tests differ on the execution level. That's weird that there's such variation between using userEvent and fireEvent, i...

@alexandru-apostu-praxedo can confirm on my side that there is an improvement in performance. without overrides my tests ran 391.7s, with overrides – 330.8 which equates to aprox. 15% improvement, which...

@alexandru-apostu-praxedo hey, i actually wanted to add on to my previous comment. This 15% improvement wasn't real, i added `overrides` property to my package.json, but since i use yarn it...

@Yuiai01 it seems to have something to do with automatic batching in React 18 or more specifically lack thereof in React 17. You pointed out correctly that it works with...