![]() ![]() If a global configuration is provided for Font Awesome Pro, it is possible to use per-project configuration for projects that require Font Awesome Free, so that the lock files are not overwritten with references to the Private npm Repository. It is recommended to use per-project npm configuration. The specific command to do this depends on the package manager you are using ( yarn or npm). When switching from the Private Repository to the Public Repository, remove the currently installed Font Awesome packages from the lock file. Switching from Private to Public Repository (and vice versa) If your application needs to use the Public Repository, ensure that the above configuration is not set. For relative path: yarn add file./. Make sure that the environment variable is available and readable by the package manager, this may be the cause ofĪuthentication issues on remote servers. 1 1 asked at 7:59 michalczukm 10k 6 40 47 Add a comment 4 Answers Sorted by: 331 For yarn version < 2.x Yarn requires prefix file: for local packages. It is recommended to store the token in an environment variable in order to avoid to commit it in a public repository. If your application needs to use the private repository, ensure that credentials are set: npm example output
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |