@datamitsu/datamitsu-linux-arm64 0.0.3-alpha-4 → 0.0.3-alpha-6

package/README.md

@@ -97,9 +97,21 @@ By default, `cache clear` clears only the current project's cache, which include
 
 Use `--all` to clear caches for all projects. Use `--dry-run` to preview what would be deleted without actually deleting anything.
 
-## Using Project Cache in Configurations
+## Template Placeholders
 
-Tools that maintain their own cache (e.g., `tsc` with `--incremental`) can use `facts().projectCachePath` to store cache files in the correct location:
+Tool arguments and paths in configurations support template placeholders that are resolved at execution time:
+
+| Placeholder   | Resolves To                             | Example                     |
+| ------------- | --------------------------------------- | --------------------------- |
+| `{cwd}`       | Per-project working directory           | `"{cwd}/src"`               |
+| `{root}`      | Git repository root                     | `"{root}/.config"`          |
+| `{toolCache}` | Per-project, per-tool cache directory   | `"{toolCache}/tsbuildinfo"` |
+| `{file}`      | Single file path (per-file scope tools) | `"{file}"`                  |
+| `{files}`     | Space-separated file list               | `"{files}"`                 |
+
+### Using Project Cache in Configurations
+
+Tools that maintain their own cache (e.g., `tsc` with `--incremental`) can use the `{toolCache}` placeholder to store cache files in the correct location:
 
 ```ts
 tsc: {
@@ -110,7 +122,7 @@ tsc: {
         "--noEmit",
         "--incremental",
         "--tsBuildInfoFile",
-        tools.Path.join(facts().projectCachePath, "tsbuildinfo"),
+        "{toolCache}/tsbuildinfo",
       ],
       command: "tsc",
       globs: ["**/*.ts", "**/*.tsx"],
@@ -122,9 +134,27 @@ tsc: {
 
 This ensures that:
 
-1. Tool caches are stored in a dedicated location (`~/.cache/datamitsu/projects/{hash}/cache/`)
-2. `cache clear` correctly cleans up tool caches alongside lint/fix results
-3. Tool caches don't pollute `node_modules` or other project directories
+1. Tool caches are isolated per project and per tool (`~/.cache/datamitsu/projects/{hash}/cache/{projectPath}/{toolName}/`)
+2. In monorepos, each project gets its own cache namespace (e.g., `cache/packages/frontend/tsc/`, `cache/packages/backend/tsc/`)
+3. Repository-scope tools use `cache/{toolName}/` (no project path component)
+4. `cache clear` correctly cleans up tool caches alongside lint/fix results
+5. Tool caches don't pollute `node_modules` or other project directories
+
+### Facts API vs Templates
+
+The `facts()` function provides platform and environment information for conditional logic in configs:
+
+- `facts().os`, `facts().arch` - Platform detection
+- `facts().isInGitRepo`, `facts().isMonorepo` - Git state
+- `facts().packageName`, `facts().binaryCommand`, `facts().binaryPath` - Binary info
+- `facts().env` - Environment variables
+
+All path references use template placeholders instead. The following facts fields have been removed (breaking change):
+
+- `facts().cwd` - use `{cwd}` template
+- `facts().gitRoot` - use `{root}` template
+- `facts().projectRoot` - use `{root}` template
+- `facts().projectCachePath` - use `{toolCache}` template
 
 ## Examples
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@datamitsu/datamitsu-linux-arm64",
-  "version": "0.0.3-alpha-4",
+  "version": "0.0.3-alpha-6",
   "description": "The Linux ARM64 binary for datamitsu, configuration management and binary distribution tool",
   "repository": {
     "type": "git",