Keillion
Keillion
https://drive.google.com/file/d/1LHM75cUZSoKH2I8d79dK4Wr0DHVynF6T/view?usp=sharing \(share removed\) Please try this zip. Node.js as server.
I will continue to try to solve it perfectly after vacation (one week left). It is expected to be time-consuming and require research compilation and detailed usage for emsdk. I...
I believe you have received a response from our technical support. For the completeness of this issue, I still put the [zip package](https://drive.google.com/file/d/15LDKEH1tvov3KZYmwoxU3uoJ62Icms2V/view?usp=sharing) that solves the problem here. Here I...
@AntoineTat1 No eval required. Require `wasm-unsafe-eval`, not `unsafe-eval`. 1. If you use public CDN, ensure ```js import { CoreModule } from "dynamsoft-core"; CoreModule.engineResourcePaths.rootDirectory = "https://cdn.jsdelivr.net/npm/[email protected]/" ``` 2. If you self...
@AntoineTat1 I am not too familiar with nextjs. I found that I need to bypass the inline script generated by nextjs itself in order to continue my testing. Do you...
@AntoineTat1 OK, I know, just allow inline for this time 😂 .
https://github.com/dynamsoft-rd-0/dbrjs-mass-samples/blob/master/nextjs-csp/next.config.mjs I use this CSP. `wasm-unsafe-eval` is required. It works well when `npm run build` + `npm run start`.
In `script-src`, I use `unsafe-inline` because of Next.js. Our SDK only require `wasm-unsafe-eval`. As long as it is based on wasm technology, this is unavoidable. In `style-src`, we can also...
I observed that `Nest.js` is a backend framework. To bypass style `unsafe-inline`, depends on your front-end. Please check this commit https://github.com/dynamsoft-rd-0/dbrjs-mass-samples/commit/fb8cfa562f1aed30d888fcb968884b7e4e88c0c3 Key code: `await CameraView.createInstance()` Or you use [esay-barcode-scanner](https://github.com/Dynamsoft/easy-barcode-scanner/blob/main/src/index.ts#L180): `EasyBarcodeScanner.scan(uiElement:...
For algorithm-intensive applications, wasm is important, and the performance achieved with pure js will be unacceptable. So we have no plan to remove `wasm-unsafe-eval`. Related Discussions: https://stackoverflow.com/a/37177219 And our wasm...