@mahameru/cli 0.0.11 → 0.0.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -1
- package/dist/index.js +629 -416
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -65,6 +65,9 @@ This command will:
|
|
|
65
65
|
- load `mahameru.config.ts`
|
|
66
66
|
- apply default config values when they are not provided
|
|
67
67
|
- run the Mahameru application from the current project
|
|
68
|
+
- watch `src/**` and `mahameru.config.ts`, then restart the dev server automatically when files change
|
|
69
|
+
|
|
70
|
+
This is server-side auto reload for development. It does not provide browser HMR or module replacement inside the running app.
|
|
68
71
|
|
|
69
72
|
### Build
|
|
70
73
|
|
|
@@ -98,7 +101,7 @@ This command will:
|
|
|
98
101
|
|
|
99
102
|
This CLI is focused on the basic development workflow:
|
|
100
103
|
|
|
101
|
-
1. Use `mahameru dev` during local development.
|
|
104
|
+
1. Use `mahameru dev` during local development and let it auto-restart on file changes.
|
|
102
105
|
2. Use `mahameru build` to produce the TypeScript build output.
|
|
103
106
|
3. Use `@/*` path aliases in `tsconfig.json` when you want non-relative imports inside `src/`.
|
|
104
107
|
4. Run `mahameru start` after a successful build to verify the production output.
|
|
@@ -107,3 +110,4 @@ This CLI is focused on the basic development workflow:
|
|
|
107
110
|
|
|
108
111
|
- If `mahameru.config.ts` is missing, the CLI will stop and show an error.
|
|
109
112
|
- If `tsx`, `typescript`, or `tsc-alias` are not installed in the project, the related command will fail.
|
|
113
|
+
- `mahameru dev` ignores changes inside `dist/` and `node_modules/`.
|