Hugo

Switching this from a bug to an enhancement since having the above data doesn't crash the app any more due to #102

Update: stores are a v3 concept I'm not 100% sure how we can detect/list them if someone else has any ideas feel free to comment.

@KevinBatdorf how about using https://www.github.com/alpine-collective/alpinejs-devtools/tree/master/packages%2Fshell-chrome%2Fsrc%2Fdevtools-background.js Does that have access to storage? Since it's creating the panel I'm thinking it might be able to send it some data

Otherwise in https://www.github.com/alpine-collective/alpinejs-devtools/tree/master/packages%2Fshell-chrome%2Fsrc%2Fbackground.js You've got access to all the "tabs" (using `Object.values(ports)`) so you could loop through the tabs and send a message to all devtools instances

> @HugoDF I looked into this finally and it's actually an issue with the simulator. The sync settings work fine using the actual devtools. > > So what that means...

> Yeah we can stub out some defaults for basic testing and show an error message. The error message we're getting is "Error: Cannot read property 'sync' of undefined" from...

🤔 so the way to do that is either to add it to the `init` message payload (which is handled in `handshake`), not sure where it originates from though If...

Here's the relevant code in Alpine, if we can hook into `CustomEvent` or `el.dispatchEvent` that could work https://github.com/alpinejs/alpine/blob/3c3e8b801a7b00a982dd54290cf656f051e915d9/src/component.js#L369

> When you say hook in, do you mean monkey-patching the prototype? Pretty much hahaha Otherwise we would have to read the DOM and parse custom event names since I...

@ryangjchandler Agreed re- the refactor. It turns out that it's possible to overwrite a magic property 👀 , so we can inject some code that will replace `$dispatch` and send...