Issue #5618πŸ’¬ AnsweredOpened January 15, 2024by Ashwinvalento0 reactions

Old Component script is not deleted on Import. Resulting in duplicate scripts

Quick answerby artf

Reimporting directly JS as a component was never possible, so it's treated as a new one.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Edge v120.0.2210.121

Reproducible demo link

https://codepen.io/ashwinvalento/pen/jOJMPqx

Describe the bug

If we have set config.parser.optionsHtml.allowScripts: true and create a component with a script, Then when we import code using the grapesjs-preset-webpage plugin, the script tag is duplicated.

How to reproduce the bug?

In the Demo link (https://codepen.io/ashwinvalento/pen/jOJMPqx)

  1. Drop the "Duplicate Script Block" to the canvas. (This component has a script)
  2. Click on the Import code option. Notice that there is only 1 script block of the "Duplicate Script Block"
  3. Click import button.
  4. Again click on the Import code option and notice that there are 2 blocks now.

What is the expected behavior? When import is clicked, the script of the previously imported component should be removed automatically and new code should be imported

What is the current behavior? Old script is not removed and new script is added which creates a duplicate. As a result, the component script exeutes multiple times

Code of Conduct

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

Answers (3)

artfβ€’ January 16, 2024

Reimporting directly JS as a component was never possible, so it's treated as a new one.

Ashwinvalentoβ€’ January 17, 2024

Is there any way we can identify scripts of existing components and delete them on import? we wont be able to remove all the script tags since we would need to retain the scripts added manually.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @Ashwinvalento.

Great suggestion about Old Component script is not deleted on Import. Resulting in duplicate scripts! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior.

Using the event system:

editor.on('component:update', (component) => {
  // your logic here
});

Alternative approaches:

  • Listen to selector:add for CSS selector changes
  • Use selector:custom for custom rules
  • Tap into the change:* events for fine-grained tracking
  • Build a plugin that extends the editor with this capability

Making it official: If this feature would benefit many users, consider opening a formal Feature Request on the GrapesJS repo with:

  • A detailed use case
  • Code example showing the desired behavior
  • Why this matters for your workflow

The core team is receptive to well-motivated feature requests backed by real use cases.

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.