You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a pipeline it used to work fine but now suddenly npm install fails. Any help on fixing this would be great
Below is the sample of the error stack
"npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-a10b2afc/src'
npm WARN tar ENOENT: no such file or directory, open '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-0d3768eb/operators/zipAll.d.ts'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-0d3768eb/src'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-d5c47b0a/_esm2015'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-a10b2afc/_esm2015'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-0d3768eb/src'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-d5c47b0a/_esm5'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-a10b2afc/_esm5'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-0d3768eb/src'
npm WARN tar ENOENT: no such file or directory, open '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-d5c47b0a/LICENSE.txt'
npm WARN tar ENOENT: no such file or directory, open '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-a10b2afc/LICENSE.txt'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-0d3768eb/src'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-d5c47b0a/src'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-a10b2afc/src'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-0d3768eb/_esm2015'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-0d3768eb/_esm5'
npm WARN tar ENOENT: no such file or directory, open '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-0d3768eb/LICENSE.txt'
npm WARN tar ENOENT: no such file or directory, lstat '/opt/atlassian/pipelines/agent/build/node_modules/.staging/rxjs-0d3768eb/src'"
Figured out, it was happening because of a package being removed or de-linked from a repo.
How did you figure out the package that was causing the issue? I am facing the same error as you have mentioned above and would be useful to understand how you found the package causing the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried installing locally with the --verbose flag on, that gave me error which was the package being removed in the npm repo. I use private repo not public NPM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How did you fix the issue? Did you have to manually remove the package somehow?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.