You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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