Skip to content

Socket npm timeout #793

@chabb

Description

@chabb

I'm using the safe-npm feature of the socket cli
When I run npm i, socket npm always fails with a timeout error. This always happens for the same package chalk

12660 silly placeDep node_modules/@mobi/rwc-cli/node_modules/tsconfig-paths-webpack-plugin ansi-styles@4.3.0 OK for: chalk@4.1.2 want: ^4.1.0
12661 verbose stack Error: Unexpected Socket API error
12661 verbose stack     at #handleApiError (/Users/francoischabby/.local/share/nvm/v22.20.0/lib/node_modules/socket/dist/vendor.js:28430:20)
12661 verbose stack     at #createBatchPurlGenerator (/Users/francoischabby/.local/share/nvm/v22.20.0/lib/node_modules/socket/dist/vendor.js:28407:47)
12661 verbose stack     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
12662 error Unexpected Socket API error

I've tried to only put chalk in my package.json, then it works.

We've a very large project, so maybe this timeout is a general thing ? If yes, is there a way to bump it ?

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