Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Pipeline ignoring .npmrc


I'm having a problem that is getting me crazy. I have a node project that use pnpm. Inside, near the package.json and at the root level there's a .npmrc file with a private registry defined. Well... running "pnpm install" the .npmrc file is ignored. I have to include a config set into the pipeline script to make everything work. Why the .npmrc file is ignored? Any clue on this?

This is the pipeline: 

image: node:16.15

depth: full

pnpm: $BITBUCKET_CLONE_DIR/.pnpm-store

- step:
name: Build, test and SonarClound Analysis
- pnpm

- curl -f | node - add --global pnpm@7
- pnpm install
- pnpm run build:main
- pnpm run test:main


1 answer

0 votes
Patrik S Atlassian Team May 05, 2022

Hello @Jorge Vázquez ,

Welcome to Atlassian Community!

From the behaviour you reported, it seems more to be an issue with the framework you are currently using (npm) and it's own configuration, rather than with Pipelines itself, as we are just providing the container environment for your build scripts commands to be executed. That said, if you clone the repository and run the build in your local machine for the same commit, you will likely reproduce the same behavior.

With that in mind, I would have the following suggestions:

  • Add the below command before executing pnpm install in order to list the files in the build directory and check if the .npmrc is indeed there :
    ls -la
  • Checking if the .npmrc is using the correct syntax to define a custom registry, as per pnpm official documentation :
  • Check if the packages you are downloading have a scope configured, because as per nodejs's registry documentation  :
    The registry URL used is determined by the scope of the package (see scope). If no scope is specified, the default registry is used, which is supplied by the registry config parameter

Hope that helps! Let me know if you have any question.

Thank you, @Jorge Vázquez !

Kind regards,

Patrik S

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events