Skip to content

Slack init command doesn't use packageManager from package.json #170

@malewis5

Description

@malewis5

Description

When running the slack init command the CLI doesn't use the packageManager defined by the user in package.json. This causes it to hang and reinstall all dependencies using npm.

Version

v3.5.1

OS Info

ProductName:            macOS
ProductVersion:         15.5
BuildVersion:           24F74
Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:49 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6000

Steps to reproduce:

Share the commands to run, source code, and project settings:

  1. Run slack init -v in your project.
  2. View logs to see npm is used.
  3. Command takes a long time.

Expected result:

  1. Slack CLI detects packageManager
  2. Slack CLI runs commands using this packageManager
  3. If @slack/cli-hooks are already installed the command takes milliseconds.

Actual result:

Image

npm is used and the command takes very long

Requirements

  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:bolt-jsRelated to github.com/slackapi/bolt-jsdiscussionM-T: An issue where more input is needed to reach a decision

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions