Skip to content

npx command suddenly stopped working #192

Closed

Description

@MdeBruin93

All of a sudden the command doesn't seem to work anymore?

Image

This is the contents of the log file:

0 verbose cli C:\Program Files\nodejs\node.exe C:\Users\micha\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
1 info using npm@11.10.1
2 info using node@v25.2.1
3 silly config load:file:C:\Users\micha\AppData\Roaming\npm\node_modules\npm\npmrc
4 silly config load:file:C:\Projects\mdblogic\.npmrc
5 silly config load:file:C:\Users\micha\.npmrc
6 silly config load:file:C:\Users\micha\AppData\Roaming\npm\etc\npmrc
7 verbose title npm exec github:bradygaster/squad
8 verbose argv "exec" "--" "github:bradygaster/squad"
9 verbose logfile logs-max:10 dir:C:\Users\micha\AppData\Local\npm-cache\_logs\2026-03-04T22_59_19_769Z-
10 verbose logfile C:\Users\micha\AppData\Local\npm-cache\_logs\2026-03-04T22_59_19_769Z-debug-0.log
11 silly logfile done cleaning log files
12 silly packumentCache heap:4496293888 maxSize:1124073472 maxEntrySize:562036736
13 verbose stack Error: could not determine executable to run
13 verbose stack     at getBinFromManifest (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\libnpmexec\lib\get-bin-from-manifest.js:17:23)
13 verbose stack     at exec (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\libnpmexec\lib\index.js:211:15)
13 verbose stack     at async Npm.exec (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\lib\npm.js:209:9)
13 verbose stack     at async module.exports (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\lib\cli\entry.js:67:5)
14 verbose pkgid @bradygaster/squad@0.8.21-preview.1
15 error could not determine executable to run
16 verbose cwd C:\Projects\mdblogic
17 verbose os Windows_NT 10.0.26200
18 verbose node v25.2.1
19 verbose npm  v11.10.1
20 verbose exit 1
21 verbose code 1
22 error A complete log of this run can be found in: C:\Users\micha\AppData\Local\npm-cache\_logs\2026-03-04T22_59_19_769Z-debug-0.log

Activity

  1. bradygaster commented on Mar 5, 2026

    @bradygaster
    Collaborator

    Thanks for reporting this! 🙏

    Good news: CLI installation and npx usage have been significantly improved in recent releases. Here are a couple of things to try:

    1. Try
      pm install -g @bradygaster/squad-cli for a fresh global install
    2. Update to the latest version if you're on an older release

    If you're still hitting issues, I'd love to help! Could you reopen with:

    • Your squad --version and Node version
    • The full error output you're seeing

    We're here to help make Squad work smoothly for you. 💙

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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