Issue #1648💬 AnsweredOpened December 11, 2018by gimzani0 reactions

Remove Font-Awesome from compiled css

Quick answerby artf

Thanks for the request, Benjamin. Actually, we have already an open issue about this argument here, so I close this one

Read full answer below ↓

Question

Hello - quick suggestion:

I'd suggest removing font-awesome from the minified css file.

The reason for this is that many developers are using node - and there is a conflict with loading the font files where it says "OTS parsing error: invalid version tag".

If instead you declare that grapes requires a separate install of font-awesome you get several benefits:

  • No conflicts using node
  • The developer can decide which version of font-awesome they want to use.
  • The developer can store the css wherever they like

Just a thought.

Cheers!

Answers (2)

artfDecember 12, 2018

Thanks for the request, Benjamin. Actually, we have already an open issue about this argument here, so I close this one

lock[bot]December 12, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

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.