mirror of
https://github.com/zama-ai/fhevm-solidity.git
synced 2026-04-17 03:00:47 -04:00
ade634a945
* docs: rename tfhe to fhe * docs: renaming all function names in the docs and library names * docs: update all mentions of TFHE * docs: tfhe-rs stays the same * docs: tfhe-rs stays the same * docs: rename repo * docs: fix renaming after merge conflicts * docs: resolve issues
74 lines
2.7 KiB
Markdown
74 lines
2.7 KiB
Markdown
# Common webpack errors
|
|
|
|
This document provides solutions for common Webpack errors encountered during the development process. Follow the steps below to resolve each issue.
|
|
|
|
## Can't resolve 'tfhe_bg.wasm'
|
|
|
|
**Error message:** `Module not found: Error: Can't resolve 'tfhe_bg.wasm'`
|
|
|
|
**Cause:** In the codebase, there is a `new URL('tfhe_bg.wasm')` which triggers a resolve by Webpack.
|
|
|
|
**Possible solutions:** You can add a fallback for this file by adding a resolve configuration in your `webpack.config.js`:
|
|
|
|
```javascript
|
|
resolve: {
|
|
fallback: {
|
|
'tfhe_bg.wasm': require.resolve('tfhe/tfhe_bg.wasm'),
|
|
},
|
|
},
|
|
```
|
|
|
|
## Buffer not defined
|
|
|
|
**Error message:** `ReferenceError: Buffer is not defined`
|
|
|
|
**Cause:** This error occurs when the Node.js `Buffer` object is used in a browser environment where it is not natively available.
|
|
|
|
**Possible solutions:** To resolve this issue, you need to provide browser-compatible fallbacks for Node.js core modules. Install the necessary browserified npm packages and configure Webpack to use these fallbacks.
|
|
|
|
```javascript
|
|
resolve: {
|
|
fallback: {
|
|
buffer: require.resolve('buffer/'),
|
|
crypto: require.resolve('crypto-browserify'),
|
|
stream: require.resolve('stream-browserify'),
|
|
path: require.resolve('path-browserify'),
|
|
},
|
|
},
|
|
```
|
|
|
|
## Issue with importing ESM version
|
|
|
|
**Error message:** Issues with importing ESM version
|
|
|
|
**Cause:** With a bundler such as Webpack or Rollup, imports will be replaced with the version mentioned in the `"browser"` field of the `package.json`. This can cause issues with typing.
|
|
|
|
**Possible solutions:**
|
|
|
|
- If you encounter issues with typing, you can use this [tsconfig.json](https://github.com/zama-ai/fhevm-react-template/blob/main/tsconfig.json) using TypeScript 5.
|
|
- If you encounter any other issue, you can force import of the browser package.
|
|
|
|
## Use bundled version
|
|
|
|
**Error message:** Issues with bundling the library, especially with SSR frameworks.
|
|
|
|
**Cause:** The library may not bundle correctly with certain frameworks, leading to errors during the build or runtime process.
|
|
|
|
**Possible solutions:** Use the [prebundled version available](./webapp.md) with `@fhevm/sdk/bundle`. Embed the library with a `<script>` tag and initialize it as shown below:
|
|
|
|
```javascript
|
|
const start = async () => {
|
|
await window.fhevm.initFhevm(); // load wasm needed
|
|
const instance = window.fhevm
|
|
.createInstance({
|
|
kmsContractAddress: "0x9D6891A6240D6130c54ae243d8005063D05fE14b",
|
|
aclContractAddress: "0xFee8407e2f5e3Ee68ad77cAE98c434e637f516e5",
|
|
network: window.ethereum,
|
|
gatewayUrl: "https://gateway.sepolia.zama.ai/",
|
|
})
|
|
.then((instance) => {
|
|
console.log(instance);
|
|
});
|
|
};
|
|
```
|