The NPM Pack action is used to build NPM packages for publishing to a registry.
Name
A friendly name for this action (will be displayed in the actions workflow area).
Enabled
Determines if this action will be run within the relevant stage.
Target Directory
Where to install the package. Relative paths will be anchored to the workspace folder.
Package Location Type
The type of package location. This can be a directory, file, URL or definition which describes the location of the npm package to build.
Package Folder
This input box is displayed if you choose Directory for the Package Location Type. Enter the path to the folder which contains the package.json file describing the package.
Package File
This input box is displayed if you choose File for the Package Location Type. Enter the path to a gzipped tarball containing the NPM package to build.
Package URL
This input box is displayed if you choose Url for the Package Location Type. Enter the Url to a gzipped tarball or Git repository containing the NPM package to install. You can enter a http or https URL or one of the following special URL formats for accessing Git repositories.
<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:/]<path>[#<commit-ish>]
where protocol is one ofgit
,git+ssh
,git+http
, orgit+https
<githubname>/<githubrepo>[#<commit-ish>]
orgithub:<githubname>/<githubrepo>[#<commit-ish>]
for installing packages from github.com repositoriesgist:[<githubname>/]<gistID>[#<commit-ish>]
for installing packages uploaded to gist.github.combitbucket:<bitbucketname>/<bitbucketrepo>[#<commit-ish>]
for installing packages from bitbucket.org repositoriesgitlab:<gitlabname>/<gitlabrepo>[#<commit-ish>]
for installing packages from gitlab.com repositories
where <commit-ish>
indicates a commit hash, branch or tag name. This defaults to master.