open_safety VS dom-expressions

Malware delivered as an email with a link to a zip file containing a .js file is one of the most common methods of delivery, right behind word macros. The "map the .js extension to notepad.exe" is a common security trick with a measurable, immediate drop in malware in large orgs. You can deploy it via GPO or InTune.

Personal promotion, I built this as a better alternative:

https://github.com/technion/open_safety

Note the built in .js parser hasn't basically ever updated, if you're writing for this you're writing like you're targetting IE5.

Allow me to reference my own workaround for those vectors:

https://github.com/technion/open_safety

https://github.com/technion/open_safety

The time I've spent on the Github actions is substantively higher than the time I've spent on the .rs files. Of course you can't "test actions before commit" in the way you can actual code, so I kept having to make branches, make 15 commits like "try action fix again", followed by squashing them all down and merging.

The template core, which is in https://github.com/ryansolid/dom-expressions/tree/main/packages/dom-expressions This template core manages the DOM and SSR-related APIs that is usually hidden from the user. This core is also "cloned" into the SolidJS repo via Rollup.

Revised my comment. However, I'm required to use Babel for: https://github.com/ryansolid/dom-expressions/tree/main/packages/babel-plugin-jsx-dom-expressions and a couple other small plugins.

Solid's transform seems fairly time consuming and difficult to maintain to me, though maybe it isn't, I'm not familiar with that code or with writing Babel transforms in general, you decide.

vuerx-jsx is using Vue's reactivity system (@vue/reactivity) with Solid's DOM renderer. Both offer blazingly fast performance, (much) faster than their original usage.

Solid is great, you can also use it with hyper dom expressions: https://github.com/ryansolid/dom-expressions