How to update from a nightly build to an official release

[georgecaocoder]

I found that neither npm i -g @vybestack/llxprt-code@latest nor npm i -g @vybestack/llxprt-code can update from the nightly build to the latest official release.

[acoliver]

you're confounding a few problems here
without the -g you're installing it locally
then with the -g you're installing it globally
so when you type llxprt --version -- which llxprt is getting executed.

so literally type "which llxprt"

then try npm uninstall -g @vybestack/llxprt-code
then type which llxprt

if you still have it (and itdoesn't say not found) maybe at some point you did sudo npm i -g @vybestack/llxprt-code
so you'll have to do
sudo npm uninstall -g @vybestack/llxprt-code

then you can either reinstall it without sudo or with.

[acoliver]

here is chatgpt's much longer version of what I said:

George – the screenshot helps, thanks.

What’s happening here is that your llxprt on $PATH is still the nightly global install, while the 0.5.0 you’re installing is ending up in a different place (or only locally in the test project). Installing into ./node_modules doesn’t touch the global binary.

Try this sequence:

1. See which llxprt you’re actually running

which llxprt
ls -l "$(which llxprt)"

2. See where npm is putting global packages

npm config get prefix

If which llxprt points somewhere that doesn’t live under the npm config get prefix directory, you’ve got two different Node installations (e.g. system Node vs nvm), and you’re updating one while running the other.

To force a clean switch back to the release:

Remove any global install in the active prefix

npm uninstall -g @vybestack/llxprt-code

Optional: clear shell hash if you use bash/zsh

hash -r 2>/dev/null || true

Sanity check – this should now fail or show nothing

which llxprt || echo "llxprt not found (expected)"

Reinstall the official release

npm install -g @vybestack/[email protected]

llxprt --version

If llxprt --version still shows the nightly string after that, it means there’s another llxprt earlier on your $PATH (from a different Node prefix or from Homebrew). In that case:
• Remove that other install (npm uninstall -g @vybestack/llxprt-code in that Node, or brew uninstall llxprt-code if you used Homebrew), or
• Adjust your $PATH so the prefix from npm config get prefix comes before the old one.

As a quick workaround you can also sanity-check the release without touching your global install:

npx @vybestack/[email protected] --version

That should report the non-nightly 0.5.0 even if your global llxprt is still on a nightly.

[acoliver]

note @georgecaocoder this is an NPM and unix paths issue more than a llxprt issue so this will apply generally to other tools you use.

[georgecaocoder]

Thank you for your patient response. I later found that I had two Node versions in my PATH; after removing the old one, the update succeeded.