I may be wrong but, speaking off the top of my head, react-markdown and its requirements (remark-gfm right now, but adding more features require additional packages) are increasing considerably the final bundle size.
We should assess if this is still the solution we want, or if, instead, we use something based on lexical. Why lexical? Because it's a framework to create text editors that we're using on our scaffold for the WYSIWYG of markdown texts in descriptions, and it's lightweight and very versatile.
Note: before starting replacing one with the other, a conscientious search should be done in order to find any existing markdown rendering package based on lexical (something we failed on when we created the editor on ui-scaffold, since there are existing packages that could have worked).
I may be wrong but, speaking off the top of my head, react-markdown and its requirements (remark-gfm right now, but adding more features require additional packages) are increasing considerably the final bundle size.
We should assess if this is still the solution we want, or if, instead, we use something based on lexical. Why lexical? Because it's a framework to create text editors that we're using on our scaffold for the WYSIWYG of markdown texts in descriptions, and it's lightweight and very versatile.
Note: before starting replacing one with the other, a conscientious search should be done in order to find any existing markdown rendering package based on lexical (something we failed on when we created the editor on ui-scaffold, since there are existing packages that could have worked).