@pancake-pos/app-cli 2026.1.5 → 2026.1.6

package/README.md

@@ -4,10 +4,13 @@ The `pos-app` command for Pancake POS apps: `login`, `dev`, `check`, `build`, `d
 
 ```bash
 npx @pancake-pos/app-cli login --shop 123 --token <token>   # from POS › Settings › Advanced › Custom apps › Connect CLI
-npx pos-app dev
-npx pos-app deploy
+npm run dev      # in an app created by create-pos-app (scripts call pos-app)
+npm run deploy
+npx @pancake-pos/app-cli versions   # any command, from anywhere
 ```
 
+Do not run `npx pos-app`: the `pos-app` package on npm is not published by Pancake, and npx downloads it outside an installed project.
+
 Docs: https://pos.pages.fm/developers/apps/en (English), https://pos.pages.fm/developers/apps (Tiếng Việt). For AI tools: https://pos.pages.fm/developers/apps/llms-full.txt.
 
 Part of Pancake POS Apps. Use is limited to building apps for Pancake POS.

package/dist/cli.js

@@ -16,7 +16,7 @@ var __export = (target, all) => {
 
 // src/api.ts
 async function apiRequest(credentials, method, path, body) {
-  if (!credentials.token) throw new ApiError(401, "Ch\u01B0a \u0111\u0103ng nh\u1EADp: ch\u1EA1y `pos-app login` tr\u01B0\u1EDBc");
+  if (!credentials.token) throw new ApiError(401, 'Ch\u01B0a \u0111\u0103ng nh\u1EADp: ch\u1EA1y l\u1EC7nh \u1EDF n\xFAt "K\u1EBFt n\u1ED1i CLI" tr\xEAn trang \u1EE8ng d\u1EE5ng tu\u1EF3 bi\u1EBFn c\u1EE7a POS (npx @pancake-pos/app-cli login \u2026)');
   const headers = { Authorization: `Bearer ${credentials.token}`, Accept: "application/json" };
   let payload;
   if (body instanceof FormData) payload = body;
@@ -1147,7 +1147,7 @@ var CLI_VERSION;
 var init_version = __esm({
   "src/version.ts"() {
     "use strict";
-    CLI_VERSION = true ? "2026.1.5" : JSON.parse(readFileSync(new URL("../package.json", import.meta.url), "utf8")).version;
+    CLI_VERSION = true ? "2026.1.6" : JSON.parse(readFileSync(new URL("../package.json", import.meta.url), "utf8")).version;
   }
 });
 
@@ -1589,7 +1589,7 @@ function createTools(ctx) {
   let dev = null;
   const devLog = [];
   const shop = () => {
-    if (!ctx.shop) throw new Error("Missing shop: start the server with --shop <shop_id> or run pos-app login --shop <shop_id>");
+    if (!ctx.shop) throw new Error("Missing shop: start the server with --shop <shop_id> or run npx @pancake-pos/app-cli login --shop <shop_id>");
     return ctx.shop;
   };
   const get = (path) => apiRequest(ctx.credentials, "GET", `/shops/${shop()}/${path}`);
@@ -1967,7 +1967,7 @@ async function run(argv, io = defaultIo) {
     const credentials = readCredentials();
     const shopOf = () => {
       const shop = str2(flags.shop) ?? credentials.shop;
-      if (!shop) throw new Error("Thi\u1EBFu --shop <shop_id> (ho\u1EB7c l\u01B0u b\u1EB1ng `pos-app login --shop`)");
+      if (!shop) throw new Error("Thi\u1EBFu --shop <shop_id> (ho\u1EB7c l\u01B0u b\u1EB1ng `npx @pancake-pos/app-cli login --shop`)");
       return shop;
     };
     switch (command) {

package/docs/llms-full.txt

@@ -259,21 +259,21 @@ npx @pancake-pos/app-cli login --shop 123 --token <token>
 Then run:
 
 ```bash
-npx pos-app dev              # watch and build, serve at http://localhost:5174
+npm run dev                  # watch and build, serve at http://localhost:5174
 ```
 
 On the same management page, click **Development mode** and enter `http://localhost:5174` (see [Manage apps › Development mode](/developers/apps/en/manage-apps#development-mode)). While it is on, POS loads the app from `localhost` **in your browser only**; everyone else in the shop keeps using the active version. When you edit code, POS reloads the extensions without reloading the page. Use Chrome or Edge: Safari may block an `https` page from loading `http://localhost`.
 
-In development mode, `pos.api` can call the Open API only after the app has been uploaded at least once (`npx pos-app deploy`, no activation needed), and it uses the `access` of the latest uploaded version. Deploy again after changing `access`. After each such deploy, reload the POS page so POS gets a new token.
+In development mode, `pos.api` can call the Open API only after the app has been uploaded at least once (`npm run deploy`, no activation needed), and it uses the `access` of the latest uploaded version. Deploy again after changing `access`. After each such deploy, reload the POS page so POS gets a new token.
 
 Development mode runs against the real data of the open shop, so try a test shop first. To see the app as a staff member with narrow permissions, deploy and activate it on a test shop and sign in with that account.
 
-While you write code, an editor with the ESLint extension shows problems as you type. Run `npx pos-app check` to validate the manifest as well.
+While you write code, an editor with the ESLint extension shows problems as you type. Run `npm run check` to validate the manifest as well.
 
 ## 4. Build and upload
 
 ```bash
-npx pos-app deploy
+npm run deploy
 ```
 
 This command:
@@ -420,7 +420,7 @@ The `pos-app` command (and the MCP server) needs a token to upload apps to the s
 
 Development mode lets you try the code you are writing inside real POS without affecting anyone else.
 
-1. On your machine, run `npx pos-app dev` in the app folder (served at `http://localhost:5174` by default).
+1. On your machine, run `npm run dev` in the app folder (served at `http://localhost:5174` by default).
 2. Click **Development mode**, enter the **Dev server address** and click **Enable development mode**.
 
 ![The Development mode dialog](/static/developers/apps/manage/en/dev-mode.webp)
@@ -651,8 +651,8 @@ and a "Send reminder" button that calls https://crm.example.com/api/remind. Read
 - [ ] Modules in `extensions/` use no real DOM, UI libraries or CSS.
 - [ ] No tokens, API keys or secrets in code.
 - [ ] Errors and loading states are handled.
-- [ ] `npx pos-app check` reports no errors.
-- [ ] Tested with `npx pos-app dev` (an account with the Settings permission), then deployed to a test shop and tried with a narrow-permission staff account.
+- [ ] `npm run check` reports no errors.
+- [ ] Tested with `npm run dev` (an account with the Settings permission), then deployed to a test shop and tried with a narrow-permission staff account.
 
 ## Sample AGENTS.md
 
@@ -677,10 +677,11 @@ Docs: https://pos.pages.fm/developers/apps/llms-full.txt (read before changing c
 - Catch errors on every API call; handle 403 and 429.
 
 ## Commands
-- npx pos-app dev: try in POS (turn on Development mode on the custom apps management page); POS reloads when code changes.
+- Run the CLI through the npm scripts below, or as `npx @pancake-pos/app-cli <command>` (login, versions, mcp). Never run `npx pos-app`: the `pos-app` package on npm is not Pancake's, and npx downloads it when the project is not installed.
+- npm run dev: try in POS (turn on Development mode on the custom apps management page); POS reloads when code changes.
 - npx eslint .: check the code after every change; do not add eslint-disable to silence rules.
-- npx pos-app check: validate the manifest and code; fix every error before deploying.
-- npx pos-app deploy: build, validate the manifest, upload a new version.
+- npm run check: validate the manifest and code; fix every error before deploying.
+- npm run deploy: build, validate the manifest, upload a new version (options after --, for example npm run deploy -- --message "...").
 - With the pos-app MCP server: get_target/list_shop_meta/sample_context before writing code, check_app after every change, get_errors after testing in POS, deploy when done (uploads an inactive version; an admin activates it). For a platform bug or a missing feature: draft a report, show it to the user, and call send_feedback only after they agree.
 ````
 
@@ -2662,7 +2663,13 @@ const pos = await connect({ timeout: 10_000 });
 
 Every command accepts `--json` for machine-readable output (CI, scripts, the MCP server).
 
-The `pos-app` command is available once `@pancake-pos/app-cli` is installed, so `npx pos-app …` works inside the project folder. Outside a project, call it by package name: `npx @pancake-pos/app-cli <command>`. The `pos-app` package on npm is not published by Pancake.
+How to run the CLI:
+
+- **In a project** created by `create-pos-app`: `npm run dev`, `npm run check`, `npm run build`, `npm run deploy`. Put options after `--`, for example `npm run deploy -- --message "Fix the debt box"`.
+- **Other commands, or from anywhere:** `npx @pancake-pos/app-cli <command>`, for example `npx @pancake-pos/app-cli versions`. In an installed project this uses the project's own version.
+- **Short command everywhere:** install globally with `npm i -g @pancake-pos/app-cli`, then run `pos-app <command>`.
+
+Do not run `npx pos-app`: the `pos-app` package on npm is not published by Pancake. Outside an installed project, npx downloads and runs that package.
 
 Activation and rollback happen on the [custom apps page](/developers/apps/en/manage-apps) in POS, so an admin always approves permissions before an app runs.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pancake-pos/app-cli",
-  "version": "2026.1.5",
+  "version": "2026.1.6",
   "description": "pos-app command for Pancake POS apps: login, dev, check, build, deploy, versions and an MCP server for AI tools",
   "license": "UNLICENSED",
   "type": "module",
@@ -24,6 +24,6 @@
     "esbuild": "^0.28.2",
     "eslint": "^10.12.0",
     "fflate": "^0.8.3",
-    "@pancake-pos/eslint-plugin": "2026.1.5"
+    "@pancake-pos/eslint-plugin": "2026.1.6"
   }
 }

package/runtime/frame.js

@@ -37,5 +37,5 @@ window.addEventListener("message", (event) => {
     else if (data?.t === "kill") kill(data.instance);
   };
 });
-window.parent.postMessage({ t: "frame-ready", protocol: PROTOCOL_VERSION, runtime: "2026.1.5" }, "*");
+window.parent.postMessage({ t: "frame-ready", protocol: PROTOCOL_VERSION, runtime: "2026.1.6" }, "*");
 //# sourceMappingURL=frame.js.map