Publish a new release? - Githubissues

damianstasik / vite-svg

Use SVG files as Vue components with Vite

MIT License

105 stars 14 forks source link

Publish a new release? #64

Open jnbooth opened 2 years ago

jnbooth commented 2 years ago

The latest release of this package on NPM was 9 months ago. Currently, this issue (solved Sep 30) has prevented me from using vite-plugin-react-svg since we switched to SSR. It would be great if that change could be published to NPM so we could go back to using this plugin.

ThenTech commented 2 years ago

Bump, also running into this, the NPM version is outdated.

bdougie commented 2 years ago

FWIW, I have a shareable release workflow that would automate on merge.

marek-sed commented 2 years ago

bump, also running into this

quolpr commented 2 years ago

Bump, I have the same issue

quolpr commented 2 years ago

@visualfanatic could you release?

quolpr commented 2 years ago

@visualfanatic could you, please, release?

szympajka commented 2 years ago

Bump :(

serg06 commented 2 years ago

I found a workaround:

yarn add https://gitpkg.now.sh/visualfanatic/vite-svg/packages/vite-plugin-react-svg?7e1571bf0636b2f341d1e66c23e8e264e64cc156

That link points directly to the current latest commit in the Github repo.

EDIT: I suggest you just switch to vite-plugin-svgr instead, since:

It fixes this issue.
It allows you to pass className to the svg element.
It's much more recent.

guguji5 commented 2 years ago

Same issue with https://github.com/visualfanatic/vite-svg/issues/73

mateusvahl commented 1 year ago

Bump