Arvis Lācis

Some related issues (not really same thing as discussed here but, anyways): - https://github.com/bmewburn/vscode-intelephense/issues/1934 - https://github.com/bmewburn/vscode-intelephense/issues/2113

@WebVPF @bennothommo I think this is not related to Winter 1.2.0, I also got this error today when doing simple `composer update` on Winter 1.1.8 installation so my guess is...

I am not 100% sure but this may be related to: - https://github.com/twigphp/Twig/pull/3704 - https://github.com/twigphp/Twig/issues/3703 So the fix is already deployed and should be fine soon..., I will let you...

@bennothommo Ok, looks like problem still persists. Same happens when I tried to update (`composer update`) my Winter 1.1.8 dev installation.

@LukeTowers No, I am using mostly my own, custom components and some from Winter CMS plugins, not the ones @WebVPF mentioned.

Something a bit weird is going on... because I did `composer update` once again today and it works fine now (so far no error in pages), without any changes in...

Here is additional update on this issue: My coworker experienced same issue after setting up the same project I used with clean composer update. After a little investigation we found...

@LukeTowers My guess it's issue with doctrine/cache or twig/twig...

But it's interesting that sometimes also doing `composer update` on the stable .lock file doesn't causes problems anymore and everything works fine also with latest Twig etc. versions.

Some backtracking information (may be useful for someone to make PR or test things) - mentioned code part which may contain problem for this issue was introduced in https://github.com/wintercms/winter/commit/970d5622c0deeaeef38c618b42d43b82499fd7f2 as...