A follow-up to "The 5.2 kB editor I had to write because nothing else fit."
Shipping a package to npm is one thing. Actually using it in the production app it was built for is a different exercise entirely. You find the edge cases nobody would catch in unit tests, because they only show up when the code touches real data, real forms, and a real design system with its own opinions.
This is the follow-up to the first post about ng-text-editor-lite, the sub-6-kB Angular WYSIWYG editor I built when nothing else fit the shape of what we needed. The editor is live now. It's handling task descriptions, comments, and log entries across the app. And along the way, I hit four issues that weren't obvious from the docs, weren't obvious from the code, and would have saved me a couple of afternoons if someone had written them down.
So here they are. Written down.
Issue 1: "No value accessor for form control" and the reactive forms trap
