-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
using the PRO icons #234
Comments
You have installed the old and deprecated icon package. Please check this documentation to learn how to install and use correct packages. Note that you'll need to configure your Also you should use specific |
Hi there, I have installed the pro now and works as you explained. Thanks for pointing that out. I do have angular 9 so compatibility should work with ng add @fortawesome/[email protected] ? Anyways, thank you for everything. |
Yes, |
Hi, how would you go about using the pro icons when you are behind a corporate proxy? |
@nephi5 It's impossible to answer your question without more details. Please open a new issue and describe step by step what you're doing and what is the error message you receive. Normally everything should just work as long as |
Hi @devoto13 - thanks for the quick answer. Our company does not use blacklists, they white-list only a handful of domains. They won't allow a domain like |
@nephi5 Well, Pro packages are only available from But I still don't completely understand what you're trying to do. What exactly do you mean by "point to those resources"? Do you want a direct link to download an NPM package? |
`angular-fontawesome` abuses `@schematics/angular` instead of re-implementing some AST manipulations. The problem is that source file is parsed by the workspace's TypeScript version (3.7.5 in this case), but `@schematics/angular` bundles TypeScript 3.8.3 and assumes that AST was produced by 3.8.3. The AST is incompatible, hence the crash. The solution is to use TypeScript bundled with `@schematics/angular` to parse the source file instead of using workspace's version. Fixes FortAwesome#237 Fixed FortAwesome#234
`angular-fontawesome` abuses `@schematics/angular` instead of re-implementing some AST manipulations. The problem is that source file is parsed by the workspace's TypeScript version (3.7.5 in this case), but `@schematics/angular` bundles TypeScript 3.8.3 and assumes that AST was produced by 3.8.3. The AST is incompatible, hence the crash. The solution is to use TypeScript bundled with `@schematics/angular` to parse the source file instead of using workspace's version. Fixes #237 Fixed #234
Describe the problem
I have done the installation and everything works as expected, however, I cannot get the Pro to work as well.
I followed this guide https://github.com/FortAwesome/angular-fontawesome
My pro folder looks like this though.
As you can see, I have the pro-solid folder, but no ref to the acorn icon.
I have also tried a new ng add @fortawesome/[email protected]
And end up with this screen.
Why would this be?
The text was updated successfully, but these errors were encountered: