Azure / Azure/static-web-apps

Azure Devops pipeline with private artifact feed

Open
#331 7 comments 3 reactions 0 assignees View on GitHub
azure-devops github-action
Dominant language
No language data
Stars
346
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Building static web apps from devops is looking good and easy to use. However we have run into a problem where we have some npm packages from our private feed, this is defined in our .npmrc file, however it appears to have problems installing packages.

.npmrc
```
registry=https://pkgs.dev.azure.com/xxx/_packaging/yyy/npm/registry/
always-auth=true;
```

For a normal pipeline build (using npm) we can define the feed in npm parameters:
```
- task: Npm@1
name: NpmInstall
inputs:
command: 'install'
workingDir: 'Clients/React'
customRegistry: 'useFeed'
customFeed: 'xxx'
```
Is it possible to specify a customFeed in the same way using the SPA pipeline task?

The pipeline output is:
```
Running 'npm install --unsafe-perm --production'...

npm ERR! code E401
npm ERR! Unable to authenticate, need: Bearer authorization_uri=https://login.windows.net/xxxx, Basic realm="https://pkgsprodcus1.pkgs.visualstudio.com/", TFS-Federated

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-03-24T18_55_50_798Z-debug.log

```

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.