Closed pioz closed 2 years ago
Prop X didn't not match
error is prevalent in NextJs - but yea, FontAwesome should make sure they are not causing it.
As a workaround, importing the component dynamically might solve your problem.
@robmadole could you please take a look?
Hey @pioz I think we've got a fix for this. I'll try to get a release out for react-fontawesome
as soon as I can.
@pioz I released 0.1.18 which includes the ability to set maskId
. Can you give this a try?
@robmadole I've tried
<FontAwesomeIcon fixedWidth icon={faGithub} mask={faCircle} maskId="github" size="2x" transform="shrink-6" />
but doesn't work. I don't know if this is the correct way to use the new maskId
prop.
@pioz I think we'll need a reproducible test case at this point. Can you provide that?
Ok, can you share a link on Codepen where I can use the <FontAwesomeIcon/>
component? I don't know how to do it 🥺.
@pioz you can use anything you like. A GitHub repo, a downloadable .zip. It doesn't have to be a codepen.
Ok, I've re-updated fontawesome, and the react warning has gone. Sorry, last time I thought I was using the latest version, it wasn't.
When I add this line of code in my React component using NextJS v12.0.10
in Chrome console I get this warning:
If I remove the
mask
prop I get no warnings. I know this is only a warning, but is there a way to avoid it?