[bug]: problems using socket security cli

Open
#1,517 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
nodejs, typescript
Domain
cli, security

Research direction

Start by reproducing the installation under nvm with the commands reported in the issue, then inspect the CLI's package and installation entry points. Compare the scoped and unscoped installs and check why which socket does not resolve. Done means a supported install creates a working socket command and the behavior is covered by a verified reproduction or test.

Written by the indexing model from the issue text.

Description

Hi, I'm on nvm and I can install any node version I want, and tried installing the cli through a number of versions. When I install socket-cli (npm i g socket or with the scoped package, it doesnt create the symlink needed to alias socket. Is this a known bug? I've tried running the install command in a pure shell and it still cant find the symlink which socket.

Dominant language
TypeScript
Stars
317
Forks
65
Avg merge
1h 26m
Merged PRs (30d)
30

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SocketDev/socket-cli

All issues in SocketDev/socket-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.