Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Now that Tailwind CSS is using Oxide and Lightning CSS, it is no longer possible to run Tailwind CSS in the browser. This is primarily a problem for websites like StackBlitz and uiverse.io that allow users to create and share web projects in the browser. Having a Tailwind CSS WASM module would allow these websites to continue to support the latest version of Tailwind CSS.
Possible use-cases for a Tailwind CSS WASM module are:
Approach
For now, I copy-pasted the existing node module code and ported it from
napi
towasm-bindgen
. I would like to add additional features later.To Do
@tailwindcss/oxide-wasm
)package.json
&README.md
for it