Custom component styles are not applied after deletion and re-addition

I'm facing a similar issue, where the re-added component has the correct styles property: <img width="1112" height="17" alt="Image" src="https://github.com/user-attachments/assets/474011c4-b1be-48df-9aa8-14c3dcdfc68d" /> But if I use the "View Code" button, the CSS was not injected, in my case they...

@mdmontesinos your usage is not correct, styles has to be defined at the component definition, and it's not expected to change. Also, it's wrong to use IDs for component definition if the component is expected to be reused, the ID will be recreated, rely on classes, especially for styles. But the r...

@artf I'm using an ID because there will always be a single instance of that component in my project. My use case is that a component is designed externally to be used as a "background" and then imported into projects that use it. Therefore, when the external component is updated, I need to also up...

This is a common issue encountered when defining static, type-level styles directly within a custom component's styles property in GrapesJS. The behavior you're observing is not strictly a bug in GrapesJS's core functionality, but rather a consequence of how its internal style manager optimizes and...