pulsar -p install not working on windows 11 for me

[Jovansam]

I have two computers with W11 -- one enterprise (fresh install) and the other home. Both do not register the pulsar -p install command and any help on this will be highly appreciated as I would like to use the Hydrogen package and terminal install is currently the only way to get it work.

Other commands do register, however. As an example, running pulsar --version returns:

Pulsar  : 1.118.2024062806
Electron: 12.2.3
Chrome  : 89.0.4389.128
Node    : 14.16.0

```pulsar --help`` also works

 Pulsar Editor v1.118.2024062806

Usage:
  pulsar
  pulsar [options] [path ...]
  pulsar file[:line[:column]]

One or more paths to files or folders may be specified. If there is an
existing Pulsar window that contains all of the given folders, the paths
will be opened in that window. Otherwise, they will be opened in a new
window.

A file may be opened at the desired line (and optionally column) by
appending the numbers right after the file name, e.g. `pulsar file:5:8`.

Paths that start with `atom://` will be interpreted as URLs.

Environment Variables:

  ATOM_DEV_RESOURCE_PATH  The path from which Pulsar loads source code in dev mode.
                          Defaults to `~/github/atom`.

  ATOM_HOME               The root path for all configuration files and folders.
                          Defaults to `~/.pulsar`.

Options:
  -d, --dev                      Run in development mode.  [boolean]
  -f, --foreground               Keep the main process in the foreground.  [boolean]
  -h, --help                     Print this usage message.  [boolean]
  -l, --log-file                 Log all output to file when running tests.  [string]
  -n, --new-window               Open a new window.  [boolean]
      --profile-startup          Create a profile of the startup execution time.  [boolean]
  -r, --resource-path            Set the path to the Pulsar source directory and enable dev-mode.  [string]
      --safe                     Do not load packages from ~/.pulsar/packages or ~/.pulsar/dev/packages.  [boolean]
      --benchmark                This option is no longer supported.  [boolean]
      --benchmark-test           This option is no longer supported.  [boolean]
  -t, --test                     Run the specified specs and exit with error code on failures.  [boolean]
  -m, --main-process             Run the specified specs in the main process.  [boolean]
      --timeout                  When in test mode, waits until the specified time (in minutes) and kills the process (exit code: 130).  [string]
  -w, --wait                     Wait for window to be closed before returning.  [boolean]
      --clear-window-state       Delete all Pulsar environment state.  [boolean]
      --enable-electron-logging  Enable low-level logging messages from Electron.  [boolean]
  -a, --add                      Open path as a new project in last used window.  [boolean]
  -p, --package                  Delegate all commands to Pulsar's package management. Run with --package for more details  [boolean]
  -v, --version                  Show version number  [boolean]

[savetheclocktower]

Does ppm --version do anything when you run it?

[Jovansam]

I get the following

~  ppm --version
Sorry! This is a transitional tool that should have been replaced during the last update.   If you see this message, something must have gone wrong.  Re-trying to update now. If this keeps happening please re-install the State Tool as described here: https://www.activestate.com/products/platform/state-tool/
█ Installing State Tool Package Manager

The State Tool lets you install and manage your language runtimes.

ActiveState collects usage statistics and diagnostic data about failures.
By using the State Tool Package Manager you agree to the terms of ActiveState’s Privacy Policy,
available at: https://www.activestate.com/company/privacy-policy

• Installing State Tool to "..." ✔ Done

█ State Tool Package Manager Installation Complete

State Tool Package Manager has been successfully installed.
Microsoft Windows [Version 10.0.22631.3810]
(c) Microsoft Corporation. All rights reserved.

[savetheclocktower]

Oof. That suggests that you have another tool called ppm. This may or may not be the reason that pulsar -p isn't working for you.

@confused-Techie, do you have any ideas?

[Daeraxa]

It should be possible to execute the binary directly shouldn't it? Comme ça:

~ > ./AppData/local/Programs/Pulsar/resources/app/ppm/bin/apm --version
ppm  2.7.0
npm  6.14.19-pulsar1-1
node 16.0.0 x64
pulsar 1.118.0
python 3.10.1
git 2.39.0.windows.1
visual studio 2019

Not sure if we are missing vital info calling it that way or not though, like passing env vars or something.

If it is OK to do that then it could just be alias'd directly to another command.

[confused-Techie]

So this is something I've seen on Windows before, and haven't had the time to track down. pulsar -p sometimes doesn't pass the logged console messages properly from ppm causing the output to be empty, even though the command is still running. In which case I usually recommend as a temporary fix usage of ppm directly, which is why on Windows we recommend ensuring it's on the PATH as well.

But because you seem to have another tool installed titled ppm you really have two options:

• If you don't use this other "State Tool Package Manager" you could remove it from your PATH.
• Otherwise like @Daeraxa recommends calling it directly from the executable will work, even if a little annoying to type out. But should be fully functional