Andrew Boyd

@jmikrut Our team ran into the same issue. Our attempt to address it can be seen in PR #3

Update, @formkit/auto-animate itself now has over 1300 stars on Github.

We're seeing this issue too. A lighthouse audit of our site seems to trigger the error reliably. Lighthouse logs an error under "Best Practices" saying that errors were logged to...

~~It's verbose, but until this is fixed you can track it yourself with a `ref` and assign to the button directly. https://formkit.link/00a9b1e102c8d18e9976ac48053a9ed7~~ Luan's solution below is much cleaner, use that!

@GustavoFenilli - so there's s lot going on with how we have to parse the raw files and build them inside an iframe to get the Vue3 code examples to...

Ok @GustavoFenilli this took some doing and I don't love they way it needed to be done, but you can now access the loaded components in the playground via direct...

Perhaps in the future I can sniff out `.vue` import statements in the `.js` files and rewrite them if they're local files to be variables. So: ``` import test from...

That's right. It's pretty much what we're doing already. We load the editor contents as raw text files and splice them into a `srcdoc` for the iframe vue. Because we...

@GustavoFenilli - the restructure needs more time in the oven. Had to revert for now due to unintended side-effects across the docs site. I'll re-open this issue.

@imRHB Does your `tailwind.config.js` include your `theme.js` file in the `content` array? Tailwind has to be told which files are going to contain Tailwind classes so it knows which ones...