Replies: 1 comment
-
You should replace the built-in browser parser #5232 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Trying to set it up so node can render the html etc from the grapesjs JSON we store from the editor (based on the comments in #3672 ). I can get things to work with the headless config option if I don't try to use any custom component types. (I get errors for the types not being found, but I get basic html output.)
When I add a call to
editor.DomComponents.addType
I start getting errors related to document being undefined in BrowserParserCss method. I don't see a way to get the grapes import to use an alternate document (like from JSDOM).Is it possible to use custom Component Types server side, or am I just wasting my time.
Beta Was this translation helpful? Give feedback.
All reactions