@vizejs/vite-plugin-musea 0.350.2 → 0.352.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.mjs +6 -2
- package/dist/index.mjs.map +1 -1
- package/package.json +4 -4
package/dist/index.mjs
CHANGED
|
@@ -3268,8 +3268,12 @@ function generateManifestModule(artFiles) {
|
|
|
3268
3268
|
* the SFC pipeline handles both, which is what the issue asks for — the variant
|
|
3269
3269
|
* is compiled the same way the enclosing SFC is:
|
|
3270
3270
|
*
|
|
3271
|
-
* :disabled="items[0]!.isValid" -> disabled: items
|
|
3272
|
-
* @u="(f: File | null) => …" -> onU: (f) => file
|
|
3271
|
+
* :disabled="items[0]!.isValid" -> disabled: $setup.items[0].isValid
|
|
3272
|
+
* @u="(f: File | null) => …" -> onU: (f) => $setup.file = f
|
|
3273
|
+
*
|
|
3274
|
+
* The generated module render function receives setup state through Vue's
|
|
3275
|
+
* proxy-unwrapped `$setup` argument, so refs intentionally do not retain an
|
|
3276
|
+
* explicit `.value` access in this output mode.
|
|
3273
3277
|
*/
|
|
3274
3278
|
/**
|
|
3275
3279
|
* Rebase the art file's `<script setup>` for a virtual module.
|