Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • S seismic-dms-service
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 49
    • Issues 49
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Domain Data Management Services
  • Seismic
  • Seismic DMS Suite
  • seismic-dms-service
  • Merge requests
  • !386

fix: npm ci command fails

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Sid Stenersen requested to merge slb/ss/npm-ci into master Apr 27, 2022
  • Overview 2
  • Commits 1
  • Pipelines 1
  • Changes 1

Fixed: npm ci command fails

@dsouzawalter described it like this:

Hi @varunmanohar @DiegoMolteni IBM integration test job is failing as npm ci is failing with following error:

_npm ERR! npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing. npm ERR! npm ERR! Invalid: lock file's debug@3.2.6 does not satisfy debug@4.3.4 npm ERR! Missing: debug@3.2.7 from lock file npm ERR! Missing: debug@3.2.7 from lock file npm ERR! Missing: debug@3.2.7 from lock file npm ERR! npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/logs/2022-04-26T23_04_42_571Z-debug-0.log ./tests/e2e/run_e2e_tests.sh: line 176: ./node_modules/newman/bin/newman.js: No such file or directory

Same error can be observed for Azure test job. I'm commenting on this MR as I noticed the error after this MR was merged.

This SO answer mentions that npm ci requires package-lock.json for it to work. https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwie4ZLFkLH3AhVvplYBHfQPAZQQrAIoAHoECAIQAQ&url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F47480617%2Fnpm-how-to-actually-use-package-lock-json-for-installing-based-on-locked-versi&usg=AOvVaw1sF5zQM11Yx8qpeZedAlh\_

FYI @anujgupta Thanks.

Edited Apr 27, 2022 by Sid Stenersen
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: slb/ss/npm-ci