Issue #5297πŸ’¬ AnsweredOpened August 10, 2023by FahemAhmad0 reactions

GetJS not working

Quick answerby artf

The getJs returns the JS of your component model (the one you would place inside model.defaults.script), not the component view. Please read carefully Components & JS

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 115.0.5790.171 (Official Build) (64-bit)

Reproducible demo link

https://codesandbox.io/s/1r0w2pk1vl?file=/index.html

Describe the bug

How to reproduce the bug?

  1. ... Add this form type and form block

What is the expected behavior? ... On getJS, i want the relevant js code inside the editor, i am not sure if my expectation is correct, if it is not, please let me know how can i achieve this

What is the current behavior? ... getJS({component}) is returning empty strings ''

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

// yourcode here
  Components.addType(typeForm, {
    isComponent: (el) => el.tagName == "FORM",

    model: {
      defaults: {
        tagName: "form",
        droppable: ":not(form)",
        draggable: ":not(form)",
        attributes: { method: "post" },
        traits: [
          {
            type: "select",
            name: "method",
            options: [
              { value: "get", name: "GET" },
              { value: "post", name: "POST" },
            ],
          },
          {
            name: "action",
          },
        ],
      },
    },

    view: {
      events: {
        submit: async function (this: any, e: Event) {
          const formData = new FormData(e.target as HTMLFormElement);
          const formValues: any = {};
          formData.forEach((value, key) => {
            formValues[key] = value;
          });

          let res = await api.post("/projects/testing", formValues);
          console.log("res", res);
        }, // Bind the function to the current context
      } as any,
    },
  });


// storage manager code  onStore: (data: any, editor: any) => {
          const pagesHtml = editor.Pages.getAll().map((page: any) => {
            const component = page.getMainComponent();

            console.log("component", editor.getJs({ component }));
            return {
              title: page.id,
              html: editor.getHtml({ component }),
              css: editor.getCss({ component }),
              js: editor.getJs({ component }),
            };
          });

          return { id: projectId, data, pagesHtml };
        },
      },

@ar

Code of Conduct

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

Answers (2)

artfβ€’ August 11, 2023

The getJs returns the JS of your component model (the one you would place inside model.defaults.script), not the component view. Please read carefully Components & JS

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @FahemAhmad.

Great question about getJS not working. The recommended approach with StyleManager 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.