Empty spritemap file

[Santana1053]

After updating to v3.0.0, my spritemap file only contains an empty svg tag.

<svg xmlns="http://www.w3.org/2000/svg"/>

I assume this is somehow related to the svgo changes.

[Applelo]

Weird because I didn't have any issue with my test demo folder. Even by fetching the package from npm. Can you provide a reproduction ?

[haleyngonadi]

@Santana1053 Did you figure this one out? I'm experiencing the same issue.

I figured this out. For me, I had to pass the glob as an array; so

VitePluginSvgSpritemap(['resources/icons/*.svg']) instead of VitePluginSvgSpritemap('resources/icons/*.svg')

[Applelo]

@haleyngonadi Weird, I didn't touch this part + I tried with a glob string and didn't have any issue 🤔

[haleyngonadi]

@Applelo Maybe it is related to how our projects are setup? I downloaded the repo, and it worked fine as is, but not in my project, so weird!

[Applelo]

@haleyngonadi Can you share a reproduction ? Or any clue (type of project...) to help me to reproduce the issue ?

[haleyngonadi]

@Applelo My project is a Laravel project. I think because my directories are deeply nested, the glob pattern was not working as expected!

[nakashu]

Had the same/similar issue.
Resolved it by using path.resolve

import path from "path";
VitePluginSvgSpritemap(path.resolve(__dirname, "./public/assets/*.svg"), {...}

Project is an almost clean install of react 19.0.0 using typescript.

Adding package.json, tsconfig and package.json for reference
tsconfig.json
package.json
vite.config.json - renamed to json, because github was unhappy with .ts :)

[Applelo]

I tried with a vanilla react template from ViteJS with your vite config, no problem for me. Does this happen on dev, build or both ?
@nakashu What is your OS? Windows, MacOS or Linux ?

[nakashu]

@Applelo

Linux

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.1 LTS
Release:        24.04
Codename:       noble

node - v22.12.0
pnpm - 9.6.0

For me it's not really a problem. I tried the path solution it worked and I moved on.
I just seen the issue and tough, maybe it will help, to pinpoint the problem if it is real in react or something.

Will be working with it next days, so will try with different 'paths . vs ./ vs / ... etc etc.
Will let you know, if it work without the path.resolve

[Santana1053]

I tried both path.resolve and wrapping the file string in an array but neither fix the issue for me on Windows.

[nakashu]

@Santana1053
If you are not using WSL (you definitely should), try changing the forward slashes / to backwards \ ones
Colleague of mine had problem with paths like this before he switched to WSL.

Windows does it differently :D