@mahameru/cli 0.0.2 → 0.0.4

package/README.md

@@ -39,6 +39,8 @@ Some commands also rely on these project dependencies:
 - `typescript` for the compile step in the `build` command
 - `tsc-alias` to rewrite path aliases after compilation
 
+For application source aliases, prefer `tsconfig.json` paths such as `@/*`. Do not rely on `package.json#imports` for `src/**` files that must run from `dist/` in production.
+
 ## Usage
 
 ### Development
@@ -76,10 +78,21 @@ This command will:
 
 - run `tsc --project tsconfig.json`
 - run `tsc-alias -p tsconfig.json`
+- fail if compiled `dist/**/*.js` files still contain unresolved `@/` or `#/` specifiers
 
 ### Start
 
-The `mahameru start` command is not implemented yet, so it cannot be used for production runtime at the moment.
+Run the production server from the compiled `dist/` output:
+
+```bash
+mahameru start
+```
+
+This command will:
+
+- load `dist/mahameru.config.js`
+- run the Mahameru application using `dist/`, `dist/modules`, and `dist/routes`
+- expect all application path aliases to have been rewritten during `mahameru build`
 
 ## Quick Workflow
 
@@ -87,7 +100,8 @@ This CLI is focused on the basic development workflow:
 
 1. Use `mahameru dev` during local development.
 2. Use `mahameru build` to produce the TypeScript build output.
-3. Make sure `mahameru.config.ts` exists in the project root so `dev` can run correctly.
+3. Use `@/*` path aliases in `tsconfig.json` when you want non-relative imports inside `src/`.
+4. Run `mahameru start` after a successful build to verify the production output.
 
 ## Notes