-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resvg
compatibility
#20
Comments
Working on #23, i hope it can help to support resvg-js sooner. |
Amazing, thank you! The demo looks good, I'll test further with Nuxt OG Image and make a new issue if there are any further issues. |
(keeping this open to not forget, might move to single tracker issue, finally we have to help upstream packages like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
unwasm: 0.3.7
node: 18.18.0
Reproduction
https://stackblitz.com/edit/stackblitz-starters-rugrtg?file=package.json
Describe the bug
Resvg requires calling initWasm before using it in a WASM context. This function only takes the module as non-initialized module. Unwasm will always initialize the module.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: