Sandboxing when used in browser about docx-templates HOT 9 CLOSED

@vdechef @mathe42 ok, then I will try to disable the sandbox when using the library within a web worker, thanks!

from docx-templates.

I'm no security expert, sorry… But your approach certainly looks interesting.

from docx-templates.

v3.0.0 might help you in this. The new hook for running JS may allow you to implement such a solution.

from docx-templates.

@guigrpa hi, I have tried using the library within a web worker but it complains that document is not present (of course it's present only in the main app context). Are there any polyfills to have this library work in a web worker? I would like to avoid an annoying 3 seconds screen freeze when a document is generated. Thanks!

from docx-templates.

@GiordanoArman I used to have it working in webworker. It was 2 years ago but it worked. I don't recall having to use dedicated polyfills.

from docx-templates.

The vm-Polyfill for browsers (included in the browser bundle) uses iframes to create a sandbox. When running in a worker this is not possible so you have to disable the sandbox. But with the workers you are isolated so you are in a sandbox so no Problems expected (in most cases)

from docx-templates.

Same as for Deno see https://github.com/guigrpa/docx-templates#deno-usage

from docx-templates.

maybe it could be helpful for other developers to mention explicitly in the docs that the sandbox needs to be disabled in order to use the library within a web worker?

from docx-templates.

@GiordanoArman good idea. Added a note on this. See c24690f

Let me know if I missed anything.

from docx-templates.