and theres a ./docs/package.json that contains some dependencies.
On a dev machine, a yarn install on top level works perfectly fine (no need for ./docs/.npmrc even - it gets found in the ancestor) and installs all dependencies. The yarn.lock URLs show the repository from the .npmrc correctly both in top-level as well as in ./docs.
But in Azure Pipelines the task (both 2.0 and the 3.0 preview) produce an error:
Are you reporting a bug or a feature request ?
Description
Top level
package.json
has:and theres a
./docs/package.json
that contains some dependencies.On a dev machine, a
yarn install
on top level works perfectly fine (no need for./docs/.npmrc
even - it gets found in the ancestor) and installs all dependencies. Theyarn.lock
URLs show the repository from the.npmrc
correctly both in top-level as well as in./docs
.But in Azure Pipelines the task (both 2.0 and the 3.0 preview) produce an error:
Expected behavior
No error, like on dev machine.
Reproduction
Start of the step, and a bit of top level project output:
...Omitting the stuff that works, then the sub-project starts (note that the .npmrc was found in top level path):
System information
VSTS or TFS:
Agent:
OS:
Yarn version: 1.22.5
Node version: 12