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
Describe the bug
Currently, if we set up Font Awesome 6 with the Pro version, it will run smoothly without any issues. However, since it's a premium package, it requires a subscription and the token needs to be provided into the .npmrc file. If the token is not provided, it will default to the free version. The issue arises when someone without the premium package pushes a commit with the free version, causing the static file to be overwritten and removing the premium Font Awesome package and icons.
Steps to Reproduce
We may want to use the .gitignore file in order to prevent pushing that scss file?
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, if we set up Font Awesome 6 with the Pro version, it will run smoothly without any issues. However, since it's a premium package, it requires a subscription and the token needs to be provided into the .npmrc file. If the token is not provided, it will default to the free version. The issue arises when someone without the premium package pushes a commit with the free version, causing the static file to be overwritten and removing the premium Font Awesome package and icons.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: