-
Notifications
You must be signed in to change notification settings - Fork 350
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
Add WASM compilation target #2250
Comments
I don't know that we can realistically ship this until April 2026 when Node.js 20 leaves LTS, since we're required by our compatibility policy to continue supporting LTS Node.js releases and npm isn't smart enough to install different packages for different SDK versions. It's also currently an open question whether WASM actually provides any performance benefits, or how feasible it would be to wrap it with a JS API. One possibility is that we replace the embedded host with WASM as a way of reducing cross-process overhead, but that's also contingent on the runtime performance being comparable with a native executable. Another is that we use the embedded host infrastructure for the main Sass release as a way of exposing the JS API with minimal additional wrapping. |
I spent some time today doing a bit of preliminary investigation of this. Here are some issues I've identified, in no particular order:
If anyone is interested in helping with this effort, the best place to put your energy in the short term would be migrating |
Now that Dart supports WASM as a compilation target, produce a version of dart-sass compiled to WASM for distribution (compatible with NodeJS 21+): https://dart.dev/web/wasm
The text was updated successfully, but these errors were encountered: