Vlad Fedosov
Vlad Fedosov
Hello! I think it's on the roadmap, and personally I wanted to work on it if no one takes it on first.
This one is in progress: #5747 #5830
**Development plan (v1, MVP):** - [x] Scaffold a new [cross-browser web extension](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Build_a_cross_browser_extension) which works with Firefox, Chrome, Edge, and Safari. #5747 - [x] Port the existing inline ASCI Lexical state...
Hi! Thanks for the input here. I think toolbar and all other components really depend on React for UI rendering, so while it's possible to do similar UI in vanilla...
Can you provide some example of Lexical/Blazor integration? W/o toolbar of course. If it can be an interactive sandbox - would be awesome.
Also pls elaborate on how usage of preact here (3kb of code) would be worse then some custom written JS to manipulate DOM
This is great! Can you pls add a test for this fix? To prevent regression
Short summary here of my research done in https://github.com/facebook/lexical/pull/5920: - `tsup` doesn't work well because: - It repeats the copyright header a lot (once per source file that was rolled...
So likely some custom solution (probably based on `rollup-plugin-ts`) needed here
Yeah, I got TS errors as ESNext is more strict comparing to the target lexical uses now. Not all packages had them, but `lexical` did