nandi95

> @ls-urs-keller one possibility is that qs could throw if it encounters a non-primitive when stringifying arrayFormat comma, but maybe there's something useful to be done instead. This is a...

What tailwind doesn't have is a shimmer animation, that could be added here maybe? https://codepen.io/maoberlehner/pen/bQGZYB

@saadeghi I imagine this can be closed as it's pretty easy to make with the `join` utility.

> Hi @nandi95, thanks for good looking and useful plugin. Are there any updates for VUE 3 support? Hi @markosole It's a slow progress, you can see the latest changes...

Testing coverage plan now scrapped to release quicker. Hopefully testing will come later 🤞

vue 3 support is now available under the tag 2.0.0-alpha.1 ```shell npm i [email protected] ``` [documentation is still in progress](https://github.com/nandi95/vue-toastify/pull/34/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R1), but the jsdoc/typescript should show the documentation and give an...

You could work around it by doing logic in the `page:transition:finish` hook

So if I hook into the `'app:chunkError'` then my plugin will be called after plugin `'nuxt:chunk-reload'`? Meaning by the time I hook in, page errors have been handled by the...

It seems that this hook will be called on page chunk error too. How would I differentiate between lazy loaded components and pages?

so the current "workaround" set `vite.build.target` to the desired target? Is that the equivalent of the proposed feature? Or that wouldn't include the dependencies?