Thank you for testing it out and sharing the screenshots!

I’ve run some performance tests using Vitest Bench, and SnapDOM was faster. I also created a few manual demos, and SnapDOM won in both speed and accuracy.

That said, I still need to run more real-world tests. So, thanks again for your help!

I added to README the npm / yarn reference. Thanks!

Yes it capture elements with css animations in theirr current frame. It isnt't work for animted gifs. And I have to test js animations engines

Looks cool, somebody should make a package that puts a nice API around it. However seems that those APIs are only in Chrome now, not Firefox or Safari.

Hi! Insaw this API when I was starting to work on snapDOM but I thought it was not ok for my needs so I discarded it. Regarding other API it would be great if View Transitions API could exposed the old view in a future

I was upset about the size of generated svg file because at first all styles were inlined in each element. So I created a function to make mini css classes (.c1, c2, c3,...) So the final size is quite small.

Not only screenshots, but also actual results. As I understand the short description, this tool allows to transform a website's current visual state into an SVG.

Not tested yet

Its a bit out of scope right now, but I thing it would be possible using some external libraries such as jsPDF or svg2pdf.js

Thank you for the suggestion!

Sincerely, I don't know if snapdom would work on a browser extension. I've never tested it on this scenery

Yes they are so good. But in my case I need to work only on the client side

It is pretty the same idea. There are many good solutions like dom-to-imge-more: the battle tested html2canvas, dom-to-image, modern-screenshot, etc. SnapDom is focused on avoiding long-taks whenever is possible because was designed to a zoomble UI engine that needs the capture doesnt affect the transition. But this is the first public version and there many things to adjust.