YePA - ePUB Processing in-browser

[fundef1]

(it's a bit lonely in the S&T section, so let's kick things off)
first off, have no react,typescript dev background, this was an experiment in more ways than one.
AI engine: (mostly) gemini free tier with some deepseek. (I find claude to be better, but not meaningfully so for this experiment)

YePA

• goal: build an ePUB processing "app" - plenty of (node.)js code availble, not inventing the wheel here
• twist: do it all in-browser
• bonus points: UI goodies (in YePA)

the good : it works!
can't stress this enough: it works, it works, it works! without dyad this would not exist.

• the really good: adding UI goodies
  (not sure how much of this is gemini vs dyad) I found it remarkable easy to add niceties. just ask, iterate (i.e. ask again), there's a creative flow I appreciate. SVG filters on random background icons with changing profiles - who could be bothered with that!
• the not so good: dyad ui - it's a bit of a mess: just stick it somewhere ... it's a bit of an acquired taste IMHO.

the bad

• removing something cleanly is much harder than adding piece-meal. Often it tries to do too much, i.e. I found myself typing: do this, but also don't do this and this and that...
• (cfr. the twist) once in a while a multi file edit would result in the introduction of a back-end service, library changes, ... undo the lot, every time
• deploy to gh-pages, router was missing resulting in a fake 404. sending me (and gemini) on a wild goose chase with convoluted fixes to very easily solved problems...

the ugly : the dyad workflow accept/reject -> test -> undo (-> git revert ...)

• i'm sorely missing a testing workflow - i tried adding tests, but accepting a change then seeing the results in preview then undo-ing doesn't work for me.
• code base context: this is fundamentally broken. i understand there's a paid feature, but this just plain bad design.

improvements: (my 0.02 euros)

• accept/reject is meaningless without proper test - make test/reqs a prime citizen
• rethink the workflow: a simple diff would do a lot, a comment on where in the wall of code a change was made with what purpose (like you know, a meaningful comment ;-) )
• redesign the "code base content" feature, e.g. in the code view?
• protect parts of the design/architecture (maybe AI_RULES.md could be helpful here, didn't try that one)

anyway, all in all it was fun whipping this up. feedback welcome (for bugs, just as dyad).