nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pipelines node 8 broken

Ergun Polat_8l8s6q

Hi,

I am trying to use node version 8.1.2, but I am getting the following erorr

gyp WARN EACCES user "nobody" does not have permission to access the dev dir "/usr/local/lib/node_modules/@angular/cli/node_modules/node-sass/.node-gyp/8.1.2"

Here is my config

image: node:8.1.2

pipelines:
  default:
    - step:
        script:
          - cd pipeline
          - apt-get update && apt-get install -y npm libcairo2-dev libjpeg62-turbo-dev libpango1.0-dev libgif-dev build-essential g++
          - npm install --global node-pre-gyp
          - npm install --global @angular/cli
          - npm install && npm cache clean
          - export BRANCH="$BITBUCKET_COMMIT"
          - npm run build-prod
          - chmod +x install.sh && ./install.sh

  branches:
    master:
      - step:
          script:
            - cd pipeline
            - apt-get update && apt-get install -y npm libcairo2-dev libjpeg62-turbo-dev libpango1.0-dev libgif-dev build-essential g++
            - npm install --global node-pre-gyp
            - npm install --global @angular/cli
            - npm install && npm cache clean
            - export BRANCH="latest"
            - npm run build-prod
            - chmod +x install.sh && ./install.sh

options:
  docker: true

If anyone can help that would be much appricated.

Accepted answers

Philip Hodder

There was a bug introduced to npm 5. @Ergun Polat I've found three potential work arounds for you.

1. Use a node:7.* image. (This uses npm 4.x)

2. Running "npm install @angular/cli" (without --global) before running it again with the global flag seems to also work.

3. Upgrade the npm version to at least 5.1.0.

The issue is with npm version 5.0.x. This is the issue to follow:

https://github.com/npm/npm/issues/16766

Which is referenced by:

https://github.com/nodejs/docker-node/issues/423

https://github.com/nodejs/docker-node/issues/424

This issue should be fixed in npm 5.1.0 (the node docker image is still on npm 5.0.3).

Fix: https://github.com/npm/npm/commit/58be2ec596dfb0353ad2570e6750e408339f1478

Release: https://github.com/npm/npm/releases/tag/v5.1.0

All comments

xtjhin

At what command does your build fail at?

Ergun Polat_8l8s6q

I've added the log

Building: /usr/local/bin/node /usr/local/lib/node_modules/@angular/cli/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ '/usr/local/bin/node',
gyp verb cli   '/usr/local/lib/node_modules/@angular/cli/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using node-gyp@3.6.2
gyp info using node@8.1.2 | linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` succeeded python2 /usr/bin/python2
gyp verb check python version `/usr/bin/python2 -c "import platform; print(platform.python_version());"` returned: "2.7.9\n"
gyp verb get node dir no --target version specified, falling back to host node version: 8.1.2
gyp verb command install [ '8.1.2' ]
gyp verb install input version string "8.1.2"
gyp verb install installing version: 8.1.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp WARN EACCES user "undefined" does not have permission to access the dev dir "/root/.node-gyp/8.1.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/@angular/cli/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '8.1.2' ]
gyp verb install input version string "8.1.2"
gyp verb install installing version: 8.1.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 8.1.2
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/@angular/cli/node_modules/node-sass/.node-gyp/8.1.2
gyp WARN EACCES user "undefined" does not have permission to access the dev dir "/usr/local/lib/node_modules/@angular/cli/node_modules/node-sass/.node-gyp/8.1.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/@angular/cli/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '8.1.2' ]

Philip Hodder

There was a bug introduced to npm 5. @Ergun Polat I've found three potential work arounds for you.

1. Use a node:7.* image. (This uses npm 4.x)

2. Running "npm install @angular/cli" (without --global) before running it again with the global flag seems to also work.

3. Upgrade the npm version to at least 5.1.0.

The issue is with npm version 5.0.x. This is the issue to follow:

https://github.com/npm/npm/issues/16766

Which is referenced by:

https://github.com/nodejs/docker-node/issues/423

https://github.com/nodejs/docker-node/issues/424

This issue should be fixed in npm 5.1.0 (the node docker image is still on npm 5.0.3).

Fix: https://github.com/npm/npm/commit/58be2ec596dfb0353ad2570e6750e408339f1478

Release: https://github.com/npm/npm/releases/tag/v5.1.0

Ergun Polat_8l8s6q

@Philip Hodder Thanks for providing me these solution. Option 1 is our current solution. We will wait for the node docker image release of 5.1.0 before moving to node8. Thanks

Ryan OConnell

@Philip Hodder

We are experiencing the same issue but can not downgrade to node 7.*
Do you have instructions on how to use npm 5.1.0 with pipelines
I tried adding the line below at the start of my script but that did not work
- npm install -g npm@5.1.0

We use image: node:8.11.1

Thanks

Ryan

Philip Hodder

Hi Ryan

When did it start breaking, and what's the error message you're getting?

Thanks,

Phil

Yoga M

We were using node 10.0.0 and was facing this issue. We fixed it by replacing node v10 with v8.11.1.

Jack_opb5cf

Thanks for sharing this, Yoga! Downgrading the node version really helped clear up the issue on my end too. It’s like adding the right tint to your setup for a smoother dev experience.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

bitbucket-pipelines