Skip to content

[Bug?]: Unable to add jsdoc from Github master branch #5208

Open
@cowwoc

Description

@cowwoc

Self-service

  • I'd be willing to implement a fix

Describe the bug

yarn add "jsdoc@https://github.com/jsdoc/jsdoc" returns:

➤ YN0000: ┌ Resolution step
➤ YN0013: │ jsdoc@https://github.com/jsdoc/jsdoc.git#commit=c6e463a8885b72d82de3f483c913e77e91167c0d can't be found in the cache and will be fetched from GitHub
➤ YN0013: │ jsdoc@https://github.com/jsdoc/jsdoc.git#commit=c6e463a8885b72d82de3f483c913e77e91167c0d can't be found in the cache and will be fetched from the remote repository
➤ YN0058: │ jsdoc@https://github.com/jsdoc/jsdoc.git#commit=c6e463a8885b72d82de3f483c913e77e91167c0d: Packing the package failed (exit code 1, logs can be found here: C:\Users\Gili\AppData\Local\Temp\xfs-1a6ba548\pack.log)
➤ YN0000: └ Completed in 26s 34ms
➤ YN0000: Failed with errors in 26s 36ms

Where pack.log contains:

Packing jsdoc@https://github.com/jsdoc/jsdoc.git#commit=c6e463a8885b72d82de3f483c913e77e91167c0d from sources
Using npm for bootstrap. Reason: found npm's "package-lock.json" lockfile

npm WARN deprecated [email protected]: This functionality has been moved to @npmcli/fs

added 1025 packages, and audited 1026 packages in 6s

90 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Looking at the log, I don't see any indication of what caused a failure

To reproduce

await packageJsonAndInstall({
});

await expect(yarn(`add`, `jsdoc@https://github.com/jsdoc/jsdoc`)).rejects.not.toThrow(`Command failed`);

(I haven't used Sherlock before so the above repro steps might not work)

Environment

System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
  Binaries:
    Node: 19.4.0 - ~\AppData\Local\Temp\xfs-fd24c4d5\node.CMD
    Yarn: 3.3.1 - ~\AppData\Local\Temp\xfs-fd24c4d5\yarn.CMD
    npm: 9.2.0 - C:\Program Files\nodejs\npm.CMD

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingreproducibleThis issue can be successfully reproduced

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions