Alice Pote

Just a quick update on this, I just opened a small PR (#3627) which fixes a bit of diagnostic handling code where we were accessing a property on a possibly-undefined...

Hi all! The Stencil team has confirmed that this is a bug and ingested it into our internal ticketing system for prioritization and so on. I can promise that when...

@benjamin-t-frost if you have one handy is there any chance you could provide a code sample where the `setTimeout` workaround _doesn't_ work? If not no worries :)

I have been looking into this issue and I believe I've figured out what's going on. Essentially, in certain cases `componentDidLoad` can fire before the DOM elements associated with a...

Hello @samshareski! Thanks for filing this issue and for providing a helpful reproduction. I can confirm that the bug you described is happening, and after a bit of investigation I'm...

@tarqwara hello there! I know it's been quite a while since you opened this issue, but I wanted to ask if you were seeing this error outside of running with...

Hey thanks for providing that repro! I did notice that the relevant objects are being logged to the console, which I believe will prevent them from getting garbage collected (see...

I think #3607 is a separate issue I _think_, although unfortunately I still haven't had time to fully dig into it, so I don't think it is dev server specific....

Hello all, I just published a dev build of Stencil with a possible fix for this issue. You can install it like this: ```sh npm install --save-dev @stencil/[email protected] ``` it...

Hey @oscargm, I just opened a PR (#4435) to port the fix to v2 and published a [dev build](https://www.npmjs.com/package/@stencil/core/v/2.22.3-dev.1685477255.0a23805) based on that change - if you have a spare minute...