Anthony Fu
Anthony Fu
I heard it's easier to remove the directly `types` field, and TypeScript would search for it automatically
At this line: https://github.com/nuxt/icon/blob/1b28ec2a0e01d39229ded06c4584f984f428caab/src/module.ts#L359 While `parseSVGContent` correctly parsed svg data with the root attributes, `convertParsedSVG` discarded them. At the interface of `IconifyIcon`, it doesn't have a field to represent custom...
We might need to add a DevTools tab for it. Or do you mean to get them from at the runtime?
If runtime, you can try https://iconify.design/docs/icon-components/vue/list-icons.html
@pi0 Implemented the async `jiti.import` (https://github.com/unjs/jiti/pull/158/commits/eddf1f582ec1b7acfe234b6280b1c540f5172477) and let unbuild's mjs stub using it (https://github.com/unjs/unbuild/pull/300/commits/f3d5a566c844bfc4a9d504d5f4857a7cc2d7bfd3) for vite/vitest env. WDYT?
I guess it would be more like an optimization? The original `?marco` seems still work at runtime, I guess if could just fallback to the runtime one when didn't get...
Use https://github.com/antfu/nip for now
PR welcome, thanks!
I guess we could just support `:customize="false"` and `:customize="null"` instead of introducing a new prop?
What would be the API looks like in your mind?