You can configure your Yarn project to use Gemfury as the primary source of npm packages. To start, commit a .yarnrc configuration to the root directory of your project:
# PROJECT_DIR/.yarnrc registry "https://npm.fury.io/USERNAME/" Subsequently, each collaborator would locally authenticate using their Gemfury credentials before running yarn commands:
npm config set always-auth true npm login --registry=https://npm.fury.io/USERNAME/ It is important to include a trailing slash in the registry URL, otherwise yarn may incorrectly connect to our registry.
…
You can configure your JavaScript project to use Gemfury as the primary source of packages. To start, commit a .npmrc configuration to the root directory of your project:
# PROJECT_DIR/.npmrc registry=https://npm.fury.io/USERNAME/ Subsequently, each collaborator would locally authenticate using their Gemfury credentials before running npm commands:
npm login --registry=https://npm.fury.io/USERNAME/ It is important to include a trailing slash in the registry URL, otherwise npm may incorrectly connect to our registry.
Blended-index registry The npm.
…
You can configure your Lerna project to publish packages to your Gemfury account. To start, authenticate into your registry with your personal credentials:
npm login --registry=https://npm.fury.io/USERNAME/ It is important to include a trailing slash in the registry URL, otherwise npm may incorrectly connect to our registry.
Once you’ve successfully logged in, you can publish with:
lerna publish --registry=https://npm.fury.io/USERNAME/ Lerna works with either npm.fury.io or the blended index endpoint npm-proxy.fury.io
…