Issue #5352šŸ’¬ AnsweredOpened August 31, 2023by rozek0 reactions

Uncaught SyntaxError: Unexpected token '{' at CanvasView.ts:590:12

Quick answerby rozek

that's interesting: defining a separate function and defining the component type as described in the docs works as designed. But it still sounds strange, that an inline function produces a syntax error in the exported HTML...

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 1.56.20 Chromium: 115.0.5790.171 (Offizieller Build) (arm64)

Reproducible demo link

none

Describe the bug

I have a component type with a script

      Editor.DomComponents.addType('HTMLView',{
        model: {
          defaults: {
             script () { console.log('Hi!'); runScript.call(this) },
            ...

When previewing a project using a component of this type, GrapesJS creates the following HTML

<div class="gjs-js-cont"><div data-id="ij6k"><script>
      setTimeout(function() {
        var item = document.getElementById('ij6k');
        if (!item) return;
        (function(){
script () {
              console.log('Hi!'); runScript.call(this)
;}.bind(item))({})
      }, 1);</script></div></div>

If you inspect this output carefully, you will see that the inner script () { is not properly closed.

I've already tried to find some workarounds but did not succeed yet. But I will try further as this problem turns out to be a blocker...

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (3)

rozek• August 31, 2023

that's interesting: defining a separate function

function script () { console.log('Hi!'); runScript.call(this) }

and defining the component type as described in the docs

      Editor.DomComponents.addType('HTMLView',{
        model: {
          defaults: {
             script,
            ...

works as designed.

But it still sounds strange, that an inline function produces a syntax error in the exported HTML...

artf• September 3, 2023

@rozek good catch, will fix for the next release

ClaudeCode• May 17, 2026

Thanks for reporting this, @rozek.

The issue with Uncaught SyntaxError: Unexpected token '{' at CanvasView.ts:590:12 appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order — make sure components are fully loaded before you interact with them

  2. Use the editor's event system — listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) — this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.

Browse premium plugins →

Related tutorials

In-depth guides on the same topic.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.