Files
llama.cpp/ui/apps/chat/alias/package.json
T
Aleksander Grygier a693a5f66f ui: llama-chat publish drops the registry check, bin paths without ./ (#32543)
* ui: llama-chat publish waits for the registry, bin paths without ./

The first publish of @ggml-org/llama-chat took about four minutes to show
up on the registry, so the 60 seconds the check after publishing waited
failed a release that had gone through. It now waits up to ten minutes.

npm normalizes "./bin/cli.js" to "bin/cli.js" on publish and warns that
the bin was "invalid and removed", which reads as if the command was
dropped. Both package.json files now give the paths as npm writes them.

Assisted-by: Claude (Opus 5.5 Medium)

* ui: drop the registry check after llama-chat publishes

npm publish already fails when the registry refuses a package, and the
check after it only failed a release that had gone through, while npm
was still processing it. Nothing waits on the registry any more.

Assisted-by: Claude (Opus 5.5 Medium)
2026-11-18 15:29:54 +01:00

34 lines
716 B
JSON

{
"name": "llama-chat",
"version": "0.1.0",
"description": "npx llama-chat: runs Llama Chat, the chat app for llama.cpp. Same as npx @ggml-org/llama-chat.",
"keywords": [
"llama.cpp",
"llama-server",
"llm",
"chat",
"local-ai"
],
"license": "MIT",
"repository": {
"type": "git",
"url": "git+https://github.com/ggml-org/llama.cpp.git",
"directory": "ui/apps/chat/alias"
},
"homepage": "https://github.com/ggml-org/llama.cpp/tree/master/ui/apps/chat#readme",
"bugs": "https://github.com/ggml-org/llama.cpp/issues",
"type": "module",
"bin": {
"llama-chat": "cli.js"
},
"files": [
"cli.js"
],
"engines": {
"node": ">=20"
},
"dependencies": {
"@ggml-org/llama-chat": "0.1.0"
}
}