Daniel

Awesome, thanks for the update!

Same issue here. Seems like some recent changes caused this to happen. My build outpus now all get thrown into `/dist/src/{main.js, ....}`

This should be fixed with the next major version release. You can try it out by installing `@phosphor-icons/vue@next`.

Since the a new major version of the library is in the works that uses a very different build system (Vite 4) this issue should be solved. Feel free to...

@brlodi I've found that if you build a library with the `preserveModules` option set to true in Rollup, vue is able to treeshake the components. So it seems vue has...

Hi there, since I've started working on the library again and there are some new icons in the pipeline, we'll soon be deploying a new major of the it. You...

Hi there, we're working on the next version of this library with native support for vue3. You can try out the newest release by running `npm install @phosphor-icons/vue@next`. Please note...

Hi there, since I've started working on the mainline library again, we'll soon be deploying a major rework of it. You can install a preview by running `npm install @phosphor-icons/vue@next`...

@edbond88 You can just simply remain on version 1.4.x . Version 2.x.x only works with vue3. As long as you don't update the library from "phosphor-vue" to "@phosphor-icons/vue" you should...

Hi @Lewitje thanks for opening this issue. It's currently not possible to import a icon manifest that links a icon name to the actual component. What you can do, and...