Skip to content
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

feat(wasm): migrate to unjs/unwasm #2037

Merged
merged 2 commits into from
Dec 29, 2023
Merged

feat(wasm): migrate to unjs/unwasm #2037

merged 2 commits into from
Dec 29, 2023

Conversation

pi0
Copy link
Member

@pi0 pi0 commented Dec 28, 2023

πŸ”— Linked issue

closes #1952

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme, or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Migrate to unjs/unwasm for the future development of stable wasm support.

All tests are now enabled. (vercel-edge only works with inlined variant have to see why later. also pending for their response...)

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@pi0 pi0 marked this pull request as ready for review December 28, 2023 22:30
@pi0 pi0 merged commit 1aec53e into main Dec 29, 2023
5 checks passed
@pi0 pi0 deleted the feat/unwasm branch December 29, 2023 00:27
@pi0 pi0 mentioned this pull request Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stable wasm support
1 participant