Hello. I agree that the documentation on how to build the addon with FontAwesome Pro is almost non-existent.
Initially, I had thought about code generation as a process that we ran internally before each release (which is true in the case of FontAwesome Free) but now I realize those instructions should be well documented and simple enough so that users are able to rebuild the component with the Pro icons. I’ll look into it.
Hello. I refactored the code generation process and included instructions in the README file. Please take a look and let us know (either here or through GitHub issues) if there is something to fix or that can be improved. (I don’t have Font Awesome Pro to test, but I understand its sources are similar to the free ones, then the same generation process should be able to produce an enhanced version of the enums).