Repository navigation
Maintenance #45
Description
Hey everyone
Since we use this project and the maintainer did not respond for a while I went ahead and forked this project here. (npm)
I've incorporated various fixes/ideas from issues and pull requests to vhtml while rewriting the code for readability, adding more tests and a benchmark. I also tried to improve the documentation according to some questions/concerns that have been raised here on vhtml.
Feel free to send pull requests or create issues over there, and we will do our best to respond to them.
Keep in mind that the fork intentionally makes a few breaking changes, which is also why I bumped the major version number.
Activity
TimDaub commentedon Oct 21, 2025
@developit would make more sense to put this repo to archived mode as the memory leak hasn't been fixed and since it is pretty critical. When used on larger pages the memory leak puts up to 200-500kb of data into memory on every render which makes this code entirely unusable and a drag to the application. My understanding is that stringjsx has solved this but moving the sanitized flag on the child property. In my mind, this avoids any kind of global memory leak. It can make sense to just put this repo in archive mode and then leave the issue here up if you don't feel save to recommend stringjxs
xueelf commentedon Jan 5, 2026
It wasn't until today that I accidentally came across this issue... Actually, about a year ago, I also developed the inact project because vhtml couldn’t be used with bun. It's a pure
jsx‑runtimethat can be easily integrated with TypeScript, ESBuild or Rollup, hope it helps.