[FEATURE REQUEST] Remove Font-Awesome from compiled css
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)
Thanks for the request, Benjamin. Actually, we have already an open issue about this argument here, so I close this one
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.
Issue #1877
[FEATURE REQUEST] Custom styles that add/remove custom classes?
Currently, all the style manager values that you change for an element simply update a <style> tag inline in the HTML. Is it possible to ch...
Issue #425
How to render external js file in our custom plugins
Hello, I am creating a slider plugins but its not working. because. I am not able to find how i can add or use external scripts and css fil...
Issue #1234
Template Problems with GrapesJS
Some templates just don't load well. Very simple templates do load properly, but there seems to be a problem with templates with more funct...
Issue #1242
[FEATURE REQUEST]: JSON to HTML parsing
Is there any support for JSON to HTML rendering, so that we can get control over the content to be published in the newsletter or webpage....
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.