Konstantin Komelin
Konstantin Komelin
@issam-seghir Why not parse5: ^8.0.0? Did you try it?
Got it @issam-seghir. Thanks. Makes sense
@nwalters512 Thank you for reporting. I need some time to reproduce the issue and confirm back. As for using `dompurify` in the browser, I guess you'd have the same result...
Hey @nwalters512 , I used your first script to calculate time and heap for a regular `isomorphic-dompurify` calls: ``` 1000 calls -> 0.604 ms, heap 92.0 MB 2000 calls ->...
@nwalters512 No, no, I greatly appreciate your findings. It's important. Let's keep it open. It's absolutely fair that you chose dompurify+jsdom fix. Business goals have top priority. I'd like to...
Tested regular `isomorphic-dompurify` calls with `await new Promise((resolve) => setImmediate(resolve));` in every loop, the heap usage improved greatly but the latency was slowly growing: ``` 1000 calls -> 2.212 ms,...
Thanks for reporting @ieedan. It's a well-known issue. Check out this one for possible solutions https://github.com/jsdom/jsdom/pull/3963 Basically, make sure that your Node version is the latest minor/patch release of your...
Thanks for reporting @riungemaina !
Thanks for reporting @felixlublasser . I've tried to reproduce the issue with the native Astro builder (not Vite) but couldn't. Can you share the Astro+Vite template which you used, so...
@felixlublasser That's good to know. Thanks. It will help me reproduce