bdbch
bdbch
Should this only live on `extension-bold`? I guess every extension would have it's own test run which we can run through with turbo?
I'm not that sure about vitest for now since we already use Cypress for E2E and integration tests. I think with Cypress we should also be able to test smaller...
True, didn't think about this. I'll add back the zeed fallback if the document is not available but I guess this will also cause the issues from #4089 to pop...
Closing this for now as we'd probably do this via another html parser.
Would love to hear some feedback or thoughts on this.
The biggest issue about this is that we don't only do the dynamic require for async reasons but also to avoid overwriting the global process variable of NodeJS (which happy-dom...
I think the only way to make those work in esm environments is to **not use require but import**. But that will require us to go async as dynamic imports...
I thought about it again and I don't see another way than either. a. making the function async which in turn would also make `generateJSON` and `generateHTML` async. b. don't...
I will check again if there's no other way except making it async (for example another happy-dom package that doesn't nuke node internals lol). Last resort will probably be a...
Okay I'm working on it right now - doing my final tests. Current implementation looks like this - the default `@tiptap/html` import will **only** be used for client side environments...