Wasm build, set-up various features #30
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add feature flags for conditional compilation (python, polars, wasm, dns) - Make dependencies optional for WASM compatibility - Add conditional DNS resolution with 'dns' feature - Enable building for WebAssembly targets
rektide
force-pushed
the
feature/wasm
branch
2 times, most recently
from
3f85df2 to
e32c5b3
Compare
rektide
force-pushed
the
feature/wasm
branch
from
e32c5b3 to
c35b11e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implements #29, building a wasm module usable from node.js and the browser. Uses a small
package.jsonwith abuildscript to do the building.Also could use:
Bikesheds
validate_deliverabilityhas a no-op if not feature=dns. Is there some other way we might want to handle this?validate_email_wasmthanlib.rs?