This repository was archived by the owner on Jun 22, 2026. It is now read-only.
Repository navigation
Conversation
Clarified usage for Next.js (SSR disabled), Vite + React, and UMD builds. Emphasized client-side only usage to avoid WASM errors.
This branch has not been deployed
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR adds a new section to the documentation explaining how to use Fhenix.js
in client-side frameworks like Next.js and React (Vite) to avoid errors related
to the WebAssembly file (tfhe_bg.wasm).
Changes include:
These changes should help developers avoid common WASM import errors
and make Fhenix.js integration smoother in modern frontend frameworks.