Mike Diarmid

@Method-X @sslotsky had the same issue here using next.js and SSR - I've worked around this issue by importing as follows: ```javascript let CodeMirror = null; if (typeof window !==...

It's still actively used on React Native Firebase for our testing there, but I've got no time myself to be actively develop it sorry

Blocked on https://github.com/firebase/firebase-android-sdk/issues/3398

Right so I got it 'working' with some patches to the following (highlighted code = added by me): 1) `./pkg/analyzer/lib/src/summary2/default_value_resolver.dart`:  That fixed the above issue (for some reason `elementNodes[element]`...

> It seems that there is too much context. What code do you try to analyze, on which the analyzer crashes? @scheglov Sorry I know it's a lot of information...

> The specific code change in `_scopeFromElement` hints that maybe there is some issue with `hashCode` of `Element`s. We do have some tricks there, but I cannot immediately say why...

Ok so after @scheglov's comment I went debugging element hashCodes, the `Element` is in the nodes list but doesn't find it based on `hashCode`, so I added some debugging and...

> I'm not 100% sure, but the extra empty component in `ElementLocation` might be the name of the unnamed constructor. I got side tracked here and patched to see if...

> Yep, I'm pretty sure it's Element and `hashCode` issues, just struggling to figure out why still 😅 currently looking at js_helpers primitives for hashCode computation since there was a...

Update: Tried Flutter `3.19.0-0.1.pre` (with Dart `3.3.0`) this morning (https://github.com/dart-lang/sdk/issues/54075 was the cause of me not being able to build beta - deleting my .dart_tool directories above the SDK root...