Alessio Gravili

> The IDE related issues can mostly be addressed by mapping over the final type, e.g. [totaltypescript.com/concepts/the-prettify-helper](https://www.totaltypescript.com/concepts/the-prettify-helper) Didn't know about that type, I'll give it a try! Got some very...

Still reproducible in 0.22.0

Fixed by https://github.com/payloadcms/payload/pull/13619 - the lexicalHTML field is now supported in client-side live preview!

Closing as duplicate of https://github.com/payloadcms/payload/issues/5285

Including Prism in @lexical/markdown caused a messed up issue for us where Node would randomly exit the process if @lexical/markdown was imported dynamically (or any dynamically imported module in the...

This issue actually occurred outside of a bundler. It was a straightforward script executed using node, tsx or swc. Interestingly, it worked perfectly within a bundler. The problem is frustratingly...

I think this code was written [before those exports were exported from `@lexical/utils`](https://github.com/facebook/lexical/pull/5831). Some modules were manually copy and pasted from the shared package. Can definitely be updated now

> The root cause is collecting all promises of all fields and then using Promise.all(). Here the runtime waits for the slowest promise and executes the micro tasks in their...

https://github.com/AlessioGr/lexical/blob/2adbe542f79cb952acc6ff1ab1b85fd4ad0a53cf/packages/lexical-playground/src/App.tsx#L163 That's how I use 2 editors on one page. This is relevant for me, as I need to be able to have multiple fully functional lexical editors on one...

This is how we got it to work for both running and debugging ```json "jestrunner.jestCommand": "pnpm exec cross-env NODE_OPTIONS=\"--experimental-vm-modules --no-deprecation\" node 'node_modules/jest/bin/jest.js'", "jestrunner.debugOptions": { "runtimeArgs": ["--experimental-vm-modules", "--no-deprecation"] } ``` Hope...