Below is my bitbucket-pipelines.yml file
npm ERR! Linux 5.15.0-1026-aws
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.14.4
npm ERR! npm v3.10.10
npm ERR! path /opt/atlassian/pipelines/agent/build/node_modules/.staging/@types/eslint-scope-de087609/package.json
npm ERR! code ENOTDIR
npm ERR! errno -20
npm ERR! syscall open
npm ERR! ENOTDIR: not a directory, open '/opt/atlassian/pipelines/agent/build/node_modules/.staging/@types/eslint-scope-de087609/package.json'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /opt/atlassian/pipelines/agent/build/npm-debug.log
Hi @Tejas Patil and welcome to the community.
I found a similar issue reported in the issue tracker of the repository for npm cli:
Based on the comments in that post, the issue may be related to a library on package.json whose version may not be compatible with the version of npm and node you are using.
The Dockerhub image gambtho/awscli_node:latest that you use as a build container has node v6.14.4 and npm v3.10.10, which are both quite old versions. If you want to keep using this Dockerhub image, you can check the suggestion posted here in order to figure out which library may be causing the issue:
Another thing you can try is using a different Docker image that has more recent versions of node v6.14.4 and npm v3.10.10. You can debug this locally with Docker first so that you don't consume your Pipelines build minutes, and try different Docker images using the following guide until you resolve this error:
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.