Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. App Packaging & Development
  3. Error while update npm-package

Error while update npm-package

Scheduled Pinned Locked Moved Solved App Packaging & Development
4 Posts 3 Posters 2.0k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      R Offline
      roru2k20
      wrote on last edited by
      #1

      Good morning,

      on my WSL-Ubuntu also on my VPS I get an error while I would like to update an app with cloudron-cli.

      It said to me, that I should update the npm package of cloudron-cli

      sudo npm install -g cloudron@4.13.1
      
      changed 121 packages, and audited 122 packages in 4s
      
      13 packages are looking for funding
        run `npm fund` for details
      
      2 vulnerabilities (1 moderate, 1 high)
      
      To address issues that do not require attention, run:
        npm audit fix
      
      Some issues need review, and may require choosing
      a different dependency.
      
      Run `npm audit` for details.
      
      ----
      sudo npm audit fix --force
      ----
      
      npm WARN using --force Recommended protections disabled.
      npm ERR! code ENOLOCK
      npm ERR! audit This command requires an existing lockfile.
      npm ERR! audit Try creating one first with: npm i --package-lock-only
      npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file
      
      npm ERR! A complete log of this run can be found in:
      npm ERR!     /root/.npm/_logs/2022-01-22T06_06_38_189Z-debug-0.log
      

      I have no clue what can I do to solve this problem.

      nebulonN 1 Reply Last reply
      0
      • R roru2k20

        Good morning,

        on my WSL-Ubuntu also on my VPS I get an error while I would like to update an app with cloudron-cli.

        It said to me, that I should update the npm package of cloudron-cli

        sudo npm install -g cloudron@4.13.1
        
        changed 121 packages, and audited 122 packages in 4s
        
        13 packages are looking for funding
          run `npm fund` for details
        
        2 vulnerabilities (1 moderate, 1 high)
        
        To address issues that do not require attention, run:
          npm audit fix
        
        Some issues need review, and may require choosing
        a different dependency.
        
        Run `npm audit` for details.
        
        ----
        sudo npm audit fix --force
        ----
        
        npm WARN using --force Recommended protections disabled.
        npm ERR! code ENOLOCK
        npm ERR! audit This command requires an existing lockfile.
        npm ERR! audit Try creating one first with: npm i --package-lock-only
        npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file
        
        npm ERR! A complete log of this run can be found in:
        npm ERR!     /root/.npm/_logs/2022-01-22T06_06_38_189Z-debug-0.log
        

        I have no clue what can I do to solve this problem.

        nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #2

        @roru2k20 are you by any chance running the npm install command withing a repository which contains a package.json or so?

        Also which nodejs and npm versions are you using?

        Further it is not clear to me, if the install or the audit fix fails. The latter should not be run when installing the cli, this is something you would run as a developer developing the package. We are updating the cli package as we see fit, not all automatic security warnings issued by npm are relevant, so no worries.

        mehdiM R 2 Replies Last reply
        0
        • nebulonN nebulon

          @roru2k20 are you by any chance running the npm install command withing a repository which contains a package.json or so?

          Also which nodejs and npm versions are you using?

          Further it is not clear to me, if the install or the audit fix fails. The latter should not be run when installing the cli, this is something you would run as a developer developing the package. We are updating the cli package as we see fit, not all automatic security warnings issued by npm are relevant, so no worries.

          mehdiM Offline
          mehdiM Offline
          mehdi
          App Dev
          wrote on last edited by
          #3

          @nebulon said in Error while update npm-package:

          not all automatic security warnings issued by npm are relevant

          I would even say : basically no automatic security warning issued by npm is relevant...

          1 Reply Last reply
          0
          • nebulonN nebulon

            @roru2k20 are you by any chance running the npm install command withing a repository which contains a package.json or so?

            Also which nodejs and npm versions are you using?

            Further it is not clear to me, if the install or the audit fix fails. The latter should not be run when installing the cli, this is something you would run as a developer developing the package. We are updating the cli package as we see fit, not all automatic security warnings issued by npm are relevant, so no worries.

            R Offline
            R Offline
            roru2k20
            wrote on last edited by
            #4

            Thanks @mehdi and @nebulon

            My problem solved by deleting the package-lock.json. After that I can update this app and all works good.

            Thank you very much.

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search