Issue #3759πŸ’¬ AnsweredOpened September 8, 2021by throne19863 reactions

Uncaught TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.

Quick answerby throne1986❀ 1

I solved the issue for future reference first I removed this function : editor.on("component:add", (model, argument) => { if (model.getName() === "Image") { modal.setContent(ModalImages); } }); I replaced with this function editor.Commands.add('open-assets', { run(editor, sender, opts = {}) { dispatch(setIsOpen(true))...

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

chrome new version

Reproducible demo link

https://codesandbox.io/s/grapejs-reactjs-forked-zqnqo?file=/src/Editor.js

Describe the bug

How to reproduce the bug?

  1. Just drag and drop image block to canvas
  2. also drag and drop custom image block to canvas can be found on landing pages block

Live demo : https://codesandbox.io/s/grapejs-reactjs-forked-zqnqo?file=/src/Editor.js

What is the expected behavior?

When the user drops custom image block, default image block, or double-clicking any image on canvas instead of opening the default modal image uploader I want to open my custom react-modal

What is the current behavior?

Now when the user drops the image on canvas or doubles click the image for replacing the image it opens up the default image uploader,

If is necessary to execute some code in order to reproduce the bug, paste it here below:

    import React, { useState, useEffect } from "react";
    import grapesjs from "grapesjs";
    import block from "grapesjs-blocks-basic";
    import ModalImages from "./ModalImages";
    
    
    const Editor = () => {
      const [editor, setEditor] = useState(null);
    
      function imageBlock(editor) {
        editor.BlockManager.add("image-block", {
          label: '<i class="fa fa-picture-o" aria-hidden="true"></i>',
          type: "image",
          content: '<image src="" />',
          category: {
            id: "image-block",
            label: "image-block",
            open: true
          },
          selectable: true,
          render: ({ model, className }) => `<div class="${className}__my-wrap">
          ${model.get("label")}
          Image
        </div>`
        });
      }
    
      useEffect(() => {
        const editor = grapesjs.init({
          container: "#editor",
          storageManager: false,
          blockManager: true,
          plugins: [block, imageBlock]
        });
    
        const bm = editor.BlockManager;
        editor.on("load", () => {
          editor.BlockManager.render([
            bm.get("image-block").set("category", "Landing Pages")
          ]);
          editor.BlockManager.getCategories().each((ctg) => ctg.set("open", false));
        });
    
        let modal = editor.Modal;
    
        editor.on("component:add", (model, argument) => {
          console.log("model", model);
          if (model.getName() === "Image") {
            modal.setContent(ModalImages);
          }
        });
    
        setEditor(editor);
      }, []);
    
      console.log("editor", editor);
      return (
        <>
          <div id="editor"></div>
        </>
      );
    };
    
    export default Editor;

Code of Conduct

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

Answers (4)

throne1986β€’ September 9, 2021
Code SnippetTEXT
I solved the issue  for future reference

first I removed this function :

        editor.on("component:add", (model, argument) => {
              if (model.getName() === "Image") {
                modal.setContent(ModalImages);
              }
            });

  
I replaced with this function

        editor.Commands.add('open-assets', {
             run(editor, sender, opts = {}) {
                dispatch(setIsOpen(true)); // open my custom asset manager
                opts.target.set('src', customImgUrl) // set image url
            }
        })

This replaced the default asset manager with my custom react modal asset manager
artfβ€’ September 9, 2021

when you run editor.command.run('open-assets') you have to pass options, eg.

editor.command.run('open-assets', {
 target: editor.getSelected(),
})
throne1986β€’ September 10, 2021
Code SnippetTEXT
@artf  I solved the issue it was about closure problem , the solution just passing the URL as options as follows

          editor.Commands.run("open-assets", {
              target: editor.getSelected()
              url: imageUrl
            });
        
         editor.Commands.add("open-assets", {
              run(editor, sender, opts = {}) {
                dispatch(setIsOpen(true));
                console.log("imageUrl", opts.url);
                opts.target.set("src", opts.url);
              }
            });

U can close the issue , again thank you so much for this library god bless ya
ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @throne1986.

Great question about Uncaught TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.. The recommended approach with Canvas is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

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.