Sam Blowes

Same issue for me, kind of makes this plugin a bit useless.

Compiling the shared config to JS and importing it works fine, untill you need to import another package,~ ```ts import IconsResolver from 'unplugin-icons/resolver' export const components = { // relative...

> Just remembered of [jiti](https://github.com/unjs/jiti), and it seems to have the [mechanism](https://github.com/unjs/jiti/blob/e44a2679cc3f3f529fbd81668e51bedcd20b74f9/src/jiti.ts#L276-L319) we need to programmatically load the config, and addresses my previous comment's concern. `jiti` however seems to have...

I have this issue too @ekqt s suggestion is the only one working for me , but we shouldnt have to use absolute

I too have this issue The images are in the `.output/public` dir  ``` image: { dir: 'public/images', } ``` But IPX throws 404 when using `build`, but works fine...

It seems it only breaks when using a custom dir, even if its a subfolder of public

For most of you here, Id suggest you move your images to the root of the `public` dir and retest. That worked for me.

I also have this issue in WebStorm but it may be due to Volar support there being experimental, adding explicit imports is working just fine.

Fwiw, @chakAs3 has [mentioned in discord](https://discord.com/channels/486522875931656193/1090204816300593162) that this should fix an issue with the templates, > Simply having multiple `` blocks in the template : `` would cause this. (this...

> Hi @blowsie the bug is related to source decorator, check the repo i made for you forked from yours https://github.com/chakAs3/unexpected-closing-tag-issue let me know so i can work on merging...