# The FontAwesome Pro token is read from the environment rather than committed.
# This file ships inside the dist archive that satis/Packeton builds for
# `composer create-project`, and those archives are served over plain HTTP to
# anyone who can reach the host - a literal token here would be published.
#
# Export FONTAWESOME_TOKEN in the shell that runs npm install, or set it as a
# CI secret. npm expands ${VAR} in .npmrc from the process environment only -
# it does not read .env - so a compose file or entrypoint has to pass it
# through to the container. Alternatively put the token in ~/.npmrc, which npm
# merges with this file and which never leaves the machine.
@fortawesome:registry=https://npm.fontawesome.com/
//npm.fontawesome.com/:_authToken=${FONTAWESOME_TOKEN}
