Skip to content

npm integrity checksum error when installing @zoon/puphpeteer from GitHub tarball #8

@AbdelElrafa

Description

@AbdelElrafa

When trying to install @zoon/puphpeteer using a direct GitHub tarball URL, npm fails with an integrity checksum error. The package is being installed as a dependency in a Laravel project that uses Puppeteer for browser automation.

Error Details

npm ERR! code EINTEGRITY
npm ERR! sha512-gk5Htsn0tpr2Zavj46HD+V/8NXORhYfSXh+V+n9vVfeZ4MAWAuze6MEhb95myN0oeK8UrrhoT8IQirMaggVfbQ== integrity check
npm ERR! sha512-gk5Htsn0tpr2Zavj46HD+V/8NXORhYfSXh+V+n9vVfeZ4MAWAuze6MEhb95myN0oeK8UrrhoT8IQirMaggVfbQ== integrity checksum failed when using sha512: wanted sha512-gk5Htsn0tpr2Zavj46HD+V/8NXORhYfSXh+V+n9vVfeZ4MAWAuze6MEhb95myN0oeK8UrrhoT8IQirMaggVfbQ== but got sha512-CVK/nnyjrMo8nkrTbkIvRkJA4ZGKR2+aM1aloNxSi2kp1Pc0UwbcWA+h9FXnubPAt5YcGF6OPDk8g8Rrca+bxg==

Environment

  • OS: macOS 24.5.0 (darwin)
  • Node.js: 20.12.2
  • npm: 10.5.0
  • Package Manager: npm

Package.json Configuration

{
  "dependencies": {
    "@zoon/puphpeteer": "https://github.com/zoonru/puphpeteer/tarball/zoon"
  }
}

Steps to Reproduce

  1. Create a new project or add the dependency to an existing project
  2. Add "@zoon/puphpeteer": "https://github.com/zoonru/puphpeteer/tarball/zoon" to package.json dependencies
  3. Run npm install
  4. Observe the integrity checksum error

Expected Behavior

The package should install successfully from the GitHub tarball URL without integrity checksum errors.

Actual Behavior

npm fails with an EINTEGRITY error, indicating that the downloaded tarball's checksum doesn't match the expected checksum.

Additional Context

This appears to be related to the @zoon/rialto package (which is a dependency of @zoon/puphpeteer) as the error mentions integrity checksum failures. The issue seems to occur specifically when installing from GitHub tarball URLs rather than from the npm registry.

Workarounds Attempted

  • Clearing npm cache (npm cache clean --force)
  • Deleting node_modules and package-lock.json
  • Using different npm versions
  • The error persists across multiple attempts

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions