You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Feature request.
We're trying to upgrade to FA 5 in our app. We've bought the PRO icon set, and have the zip ready - however here we've hit a bump. The docs only mention using the private NPM package if you want to use the PRO icons. What happens if you'd prefer to use self-hosted version? Is that possible/on the roadmap?
Describe the solution you'd like
Ability to use self-hosted icons, instead of pulling them from private NPM registry.
The text was updated successfully, but these errors were encountered:
@jbandura / @netes can you talk a bit about why. Are you not running ember-cli, or not using NPM?
Sure. The first thing is reliability - today we had a few 500 coming from the https://npm.fontawesome.com during builds so it makes us think what if we have "emergency" build with some hotfix and this occurs? I'm on the side that the less external services we depend on - the better.
Second thing is, that you need every developer to set the token in the ENV variable. It's not a problem with a few devs, but with the bigger teams - it's just inconvenient.
Is your feature request related to a problem? Please describe.
Feature request.
We're trying to upgrade to FA 5 in our app. We've bought the PRO icon set, and have the zip ready - however here we've hit a bump. The docs only mention using the private NPM package if you want to use the PRO icons. What happens if you'd prefer to use self-hosted version? Is that possible/on the roadmap?
Describe the solution you'd like
Ability to use self-hosted icons, instead of pulling them from private NPM registry.
The text was updated successfully, but these errors were encountered: