You may want to check out previewjs.com (disclaimer I'm the author) although it's unfortunately not getting much love or attention lately, my kids are using all of that.
Unless I completely misunderstood the post, a function that calls another function with effects will indeed be "infected". That is, unless the effect ends up being local (such as passing a mutable reference to a local variable).
It's early days and you might find that Preview.js can be a little difficult to set up in a large, complex project (working on improving that now) but please send through any feedback on the GitHub repo or Discord server, much appreciated!
This was originally an extension for Visual Studio Code to preview React components directly in your IDE (that's still available too, as well as for IntelliJ now).
I've since gotten feedback that it's a useful alternative to Storybook, which people often find frustratingly slow, so I decided to build a CLI version as well.
React Preview is not yet open source (I'll probably end up switching to an open core model at some point) but it's based on ViteJS (which is significantly faster than webpack). It also uses the TypeScript Compiler API to resolve types and automatically generate valid props, so you don't need to configure custom stories like you would with Storybook (although that's supported too).
I've been working on React Preview for a few months. It's currently only available for Visual Studio Code, but an IntelliJ/WebStorm and CLI versions are also in the works and coming soon (you can subscribe to be notified at https://signup.reactpreview.com).
The plan is for React Preview to be a freemium product. The current features are all free, with more advanced paid features coming soon (e.g. integration with Storybook, mosaic of all your components, preview in multiple viewports, etc).
A bit of self-promotion: I've been building something similar but without the visual editing, integrating directly in your VS Code editor (and soon IntelliJ/WebStorm too). See https://reactpreview.com for more info.
I was frustrated with people missing emails/slack messages about GitHub pull requests.
I built a browser extension that shows a notification pop-up and updates the extension badge whenever you get a new pull request. Then I proceeded to convince my colleagues to use it.
For any Googlers out there, this is the same thing as CL Monitor, but for GitHub. I used to maintain CL Monitor back in the days (although I didn't invent it).
I really like seeing efforts being made in this direction. For the last few years I've been using git-town.com, which works quite well but I often end up having to work around it (especially when I have diamond-shaped branch dependencies, e.g. to refactor two independent things before implementing a small feature on top). I'll have to try this instead and compare!
Indeed, that's why you'd want to use a solution like Git LFS to avoid bloating your repo. Basically, it only stores a link to the image, which is stored separately.
I'd encourage you to try Git LFS, it's a very simple extension to Git. It only takes a couple of minutes to set up if you use GitHub, and I suspect other platforms are similar :)
I'd recommend reading "The Laws of Human Nature" by Robert Greene. It talks about this.
My interpretation from the book: it's a perfectly natural feeling, but it doesn't mean you have to act on negative destructive instincts. There are ways to channel this energy into more productive behaviours (e.g. by using it to challenge yourself).