Issue #5135πŸ’¬ AnsweredOpened May 22, 2023by duclet0 reactions

Incorrect type definition for StyleManager.addProperty

Quick answerby SachinPuthiyoth

Seems like the type definition in StyleManagerConfig.sectors is unchanged : https://github.com/GrapesJS/grapesjs/blob/5c890449a52f526bc480d6dc649ff5e01ec59140/src/stylemanager/config/config.ts#L8 Shouldn't we be updating this to use PropertyTypes as in : https://github.com/GrapesJS/grapesjs/blob/5c890449a52f526bc480d6...

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

All

Reproducible demo link

None

Describe the bug

How to reproduce the bug?

  1. Per the definition here: https://github.com/GrapesJS/grapesjs/blob/dev/src/style_manager/index.ts#L304, you should be providing the options as options for PropertyProps.
  2. However, PropertyProps as defined here: https://github.com/GrapesJS/grapesjs/blob/dev/src/style_manager/model/Property.ts#L9, does not have such a property. This is causing the TS compiler to complain.

What is the expected behavior? Definition should exists.

What is the current behavior? Definition is missing.

Code of Conduct

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

Answers (2)

SachinPuthiyothβ€’ January 12, 2024

Seems like the type definition in StyleManagerConfig.sectors is unchanged : https://github.com/GrapesJS/grapesjs/blob/5c890449a52f526bc480d6dc649ff5e01ec59140/src/style_manager/config/config.ts#L8 Shouldn't we be updating this to use PropertyTypes as in : https://github.com/GrapesJS/grapesjs/blob/5c890449a52f526bc480d6dc649ff5e01ec59140/src/style_manager/index.ts#L86 Opened an issue here - https://github.com/GrapesJS/grapesjs/issues/5613 Shall I raise a PR for the same?

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @duclet.

Great question about Incorrect type definition for StyleManager.addProperty. 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.