@pathmx/path 0.5.0 → 0.5.2

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.
Files changed (2) hide show
  1. package/README.md +35 -18
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -1,30 +1,47 @@
1
1
  # `@pathmx/path`
2
2
 
3
- > This package is the current proof-of-concept implementation. The replacement
4
- > authoring and composition contract is being shaped in
5
- > [Path plugin](../../apps/pathmx-site/paths/work/path.design.md).
3
+ Ordered learning-path semantics for PathMX applications. It recognizes
4
+ `*.path.md` Sources and projects their linked lists into stable, nested steps.
6
5
 
7
- The Path semantic owner for the Paths product family. `PathPlugin` contributes
8
- the `path` Source schema; the same package projects viewer-readable Path
9
- Sources into ordered, nested steps with stable ids and guarded cycles.
6
+ ## Install
10
7
 
11
- Use the Plugin directly when composing a product without the full Paths preset:
8
+ Add the package to an existing PathMX project:
9
+
10
+ ```sh
11
+ bun run pmx plugins add path
12
+ ```
13
+
14
+ Activate it with a repository Plugin:
12
15
 
13
16
  ```ts
17
+ // plugins/path.plugin.ts
14
18
  export { default } from "@pathmx/path"
15
19
  ```
16
20
 
17
- `projectPath()` and `pathStepIds()` expose the Path structure to downstream
18
- systems. An unlabeled step derives its id from the href, so inserting Blocks
19
- does not orphan Completion; author `@step.<id>` when identity must survive a
20
- destination change. `rollupPathCompletion()` maps stable Path leaves onto a separately
21
- composed `@pathmx/completion` reader. `PathCompletionContributor` declares
22
- stable leaf `path/<step-id>` manual keys to the canonical Action; aggregate
23
- branches remain derived from their children:
21
+ Most applications should install [`@pathmx/paths`](https://www.npmjs.com/package/@pathmx/paths)
22
+ instead. That preset includes Path, Completion, and Player with the correct
23
+ release versions.
24
24
 
25
- ```ts
26
- CompletionPlugin({ contributors: [PathCompletionContributor] })
25
+ ## Author a Path
26
+
27
+ Create a `*.path.md` Source whose unordered list links define the steps:
28
+
29
+ ```md
30
+ # Web foundations
31
+
32
+ - [Introduction](./introduction.md)
33
+ - [HTML](./html.md)
34
+ - [Practice](./html-practice.md)
35
+ - [CSS](./css.md)
36
+ ```
37
+
38
+ Step ids are derived from their links. Give a step an explicit id when its
39
+ identity must survive a destination change:
40
+
41
+ ```md
42
+ - [@step.introduction Introduction](./welcome.md)
27
43
  ```
28
44
 
29
- `@pathmx/paths` supplies that composition. Completion is an optional peer;
30
- installing Path alone does not install or activate it.
45
+ Plugin authors can use `projectPath()` to resolve a viewer-readable Path tree,
46
+ `pathStepIds()` to inspect local step ids, and `rollupPathCompletion()` to
47
+ combine a projected Path with a composed Completion reader.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@pathmx/path",
3
3
  "description": "Ordered learning-path semantics for PathMX applications.",
4
- "version": "0.5.0",
4
+ "version": "0.5.2",
5
5
  "license": "SEE LICENSE IN LICENSE.md",
6
6
  "repository": {
7
7
  "type": "git",
@@ -21,7 +21,7 @@
21
21
  "bun": ">=1.4.0"
22
22
  },
23
23
  "peerDependencies": {
24
- "@pathmx/completion": "^0.5.0",
24
+ "@pathmx/completion": "^0.5.2",
25
25
  "@pathmx/core": "^0.5.0"
26
26
  },
27
27
  "peerDependenciesMeta": {