Issue #4042πŸ’¬ AnsweredOpened January 2, 2022by sanjanaadeshra0 reactions

Icons are not loading when loading within an angular application

Quick answerby sanjanaadeshra

I was able to resolve this issue by adding font awesome icons css directly to the grape.min.css file. I am not sure why that had to be done since the CSS was being imported already, its working with that workaround, but it would be better if a cleaner solution can be suggested.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome

Reproducible demo link

https://stackblitz.com/edit/angular-dei45q?file=src%2Fapp%2Fapp.component.ts

Describe the bug

Added an attached image to give an idea of what the editor looks like

What is the expected behavior? Need to load the grapejs ediotr

What is the current behavior? Editor loads, but none of the icons are visible.

Code of Conduct

  • I agree to follow this project's Code of Conduct Screenshot 2022-01-02 at 3 48 52 AM (2)

Answers (3)

sanjanaadeshraβ€’ January 3, 2022

I was able to resolve this issue by adding font awesome icons css directly to the grape.min.css file. I am not sure why that had to be done since the CSS was being imported already, its working with that workaround, but it would be better if a cleaner solution can be suggested.

artfβ€’ January 4, 2022

Your demo doesn't seem to load, and the grapesjs version you're using there is quite outdated (0.14.15). Please upgrade and next time open the new bug issue relative to the latest version.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @sanjanaadeshra.

The issue with Icons are not loading when loading within an angular application appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order β€” make sure components are fully loaded before you interact with them

  2. Use the editor's event system β€” listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) β€” this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

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.