Menci / Menci/vite-plugin-wasm
Support status for vite-plugin-wasm and testing env
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 431
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
I was trying to uderstand where vite-plugin-wasm is supported.
The testing environment is here: https://github.com/Jerboas86/vpw-test-env
I tried different frameworks:
- svelte (CSR)
- sveltekit (SSR)
In different scopes:
- Window scope
- Worker scope
- Worklet scope (audioworklet)
- Nodejs scope (vitest)
And with different web browers:
- Chrome 108
- Firefox 108
- Gnome web (aka Epiphany) 43
Results
Chrome
| Svelte | Sveltekit | |
|---|---|---|
| Window | ✅ | ❗ |
| Worker | ✅ | ❗ |
| Worklet | ❗ | ❗ |
| Vitest | ❗ | ❗ |
Firefox
| Svelte | Sveltekit | |
|---|---|---|
| Window | ✅ | ❗ |
| Worker | ❗ | ❗ |
| Worklet | ❗ | ❗ |
| Vitest | ❗ | ❗ |
Gnome web
| Svelte | Sveltekit | |
|---|---|---|
| Window | ✅ | ❗ |
| Worker | ✅ | ❗ |
| Worklet | ❗ | ❗ |
| Vitest | ❗ | ❗ |
opened issues:
and opened PR:
I would suggest to:
- update the readme to reflect current support
- and open issue for audioworklet support
The testing can also be extended if it is valuable, let me known.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the README and the linked vpw-test-env results, then compare them with issues 18 and 4 and pull request 16. Done means documenting the current support matrix accurately and, if still needed, filing the audioworklet support issue; confirm whether the existing Vitest work changes the results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- build-system, testing-qa, web-dev
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100