repo-blueprint 0.1.2 → 0.1.3

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "repo-blueprint",
3
- "version": "0.1.2",
4
- "description": "Generate a zoomable, dependency-layered architecture map of a code repository by static analysis.",
3
+ "version": "0.1.3",
4
+ "description": "A clearer way to see how a repository is built. Maps TypeScript and Python codebases into dependency layers you can zoom through.",
5
5
  "license": "MIT",
6
6
  "author": {
7
7
  "name": "Mo Ganji"
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  A clearer way to see how a repository is built. repo-blueprint maps a codebase into layers, with each part placed above its dependencies. Detail is handled by zoom: the top level shows packages, and zooming in reveals folders, then files.
4
4
 
5
- ![TanStack Query mapped with repo-blueprint](https://raw.githubusercontent.com/MohGanji/repo-blueprint/v0.1.2/media/demo.gif)
5
+ ![TanStack Query mapped with repo-blueprint](https://raw.githubusercontent.com/MohGanji/repo-blueprint/main/media/demo.gif)
6
6
 
7
7
  - Works with TypeScript, JavaScript and Python, monorepos included
8
8
  - Draws imports, RPC and HTTP calls, events, and external systems such as databases and queues
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "repo-blueprint",
3
- "version": "0.1.2",
4
- "description": "Generate a zoomable, dependency-layered map of a code repository by static analysis.",
3
+ "version": "0.1.3",
4
+ "description": "A clearer way to see how a repository is built. Maps TypeScript and Python codebases into dependency layers you can zoom through.",
5
5
  "author": "Mo Ganji <mo@ganji.me>",
6
6
  "license": "MIT",
7
7
  "repository": {
@@ -14,13 +14,13 @@ The skill runs the `repo-blueprint` npm package, pinned to the version it was wr
14
14
  One-time build, writes the HTML and prints its path plus a summary:
15
15
 
16
16
  ```bash
17
- npx -y repo-blueprint@0.1.2 build <repo> --open
17
+ npx -y repo-blueprint@0.1.3 build <repo> --open
18
18
  ```
19
19
 
20
20
  Live mode, serves the page and rebuilds it when source files change (run it in the background; it keeps running until stopped):
21
21
 
22
22
  ```bash
23
- npx -y repo-blueprint@0.1.2 watch <repo> --open
23
+ npx -y repo-blueprint@0.1.3 watch <repo> --open
24
24
  ```
25
25
 
26
26
  Keep the pinned version as written, even if a newer one exists: the same commit and the same version always produce the same page, so users can compare blueprints over time.