vue-fragment
vue-fragment copied to clipboard
a very candide fragment component for Vue.js
Vue-Fragment is a great bridge between Vue 2 and 3, however it took a lot of effort to get it to work with snapshot testing. So I'm posting this here...
More of a question than an issue, but basically the title. Just wondering if it's possible to turn off these comments for production, or if they're integral to functionality: ...
Type declarations are on the repo but not on npm, making the package not usable with typescript when installing from npm.
I'm trying to use the fragment plugin with my TypeScript Vue app created with Vue CLI: import { Vue, Component } from 'vue-property-decorator'; import Fragment from 'vue-fragment'; @Component({ components: {...
Published package doesn't seem to include typings. Can we have those published as well?
Getting this error when using: vue 2.6.12 vue-fragment: 1.5.1 and (from readme): ``` import Fragment from 'vue-fragment'; Vue.use(Fragment.plugin); ``` 
This library definitely needs unit tests. For starters, I encourage all to list here known use-cases (both working and non-working).
Minimal repro: https://codesandbox.io/s/vue-fragment-slot-ckird 1. Click button to show content 2. Click button to remove content 3. not all children are removed & this error occurs: `"NotFoundError: Failed to execute 'removeChild'...
When i check website on https://validator.w3.org/ there is an error occurs: > Attribute fragment not allowed on element div at this point. `` Maybe change fragment attribute by data-fragment?
It would be useful to support something like `v-html` for fragments. Unfortunately that directive does not work with this component.