Skip to content

Wasm build, set-up various features - #30

Draft
rektide wants to merge 3 commits into
bnkc:mainfrom
rektide:feature/wasm
Draft

Wasm build, set-up various features#30
rektide wants to merge 3 commits into
bnkc:mainfrom
rektide:feature/wasm

Conversation

@rektide

@rektide rektide commented Nov 26, 2025

Copy link
Copy Markdown

Implements #29, building a wasm module usable from node.js and the browser. Uses a small package.json with a build script to do the building.

Also could use:

  • docs
  • github actions / workflow to run at build
  • npm release flow

Bikesheds

  • I let the AI go a bit wild with Cargo features. How do we feel about what we have?
  • Domain validation's validate_deliverability has a no-op if not feature=dns. Is there some other way we might want to handle this?
  • Is there some better place/name for the wasm entrypoint validate_email_wasm than lib.rs?

- 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
rektide marked this pull request as draft November 26, 2025 01:01
@rektide
rektide force-pushed the feature/wasm branch 2 times, most recently from 3f85df2 to e32c5b3 Compare November 26, 2025 01:05
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.

1 participant