BitSquare/ansiblings
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

[chore] commit id display on version
Publish snapshot / snapshot (push) Successful in 1m26s
Details

Browse Source
This commit is contained in:
Benjamin Diedrichsen
2026-07-29 13:00:10 +02:00
parent ea08e76a2f
commit 1ba1c2a32a
17 changed files with 589 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/nopy/README.md
+4 -4
View File
@@ -302,12 +302,12 @@ All three are unioned and scanned the same way. A directory is a cube when it ho
#### Cube packages
A cube package is an ordinary npm package that ships cube directories and points at them from its own `package.json`:
A cube package is an ordinary npm package that ships its cubes in a `cubes/` directory at its root. That is the whole contract — no nopy-specific `package.json` field is required. A bundle whose cubes live elsewhere (compiled into `dist/cubes`, say) overrides the location:
```json
{
"name": "@bitsquare/cubes-core",
"nopy": { "cubes": ["./cubes"] }
"name": "@acme/cubes-web",
"nopy": { "cubes": ["./dist/cubes"] }
}
```
@@ -321,7 +321,7 @@ pnpm add -D @bitsquare/cubes-core
{ "cubePackages": ["@bitsquare/cubes-core"] }
```
Naming a package is a statement that cubes are expected from it, so anything wrong is an error that aborts the run rather than a silent skip: the package is not installed, it declares no `nopy.cubes`, or an entry points at a directory that does not exist or lies outside the package.
Naming a package is a statement that cubes are expected from it, so anything wrong is an error that aborts the run rather than a silent skip: the package is not installed, it has neither a `cubes/` directory nor a `nopy.cubes` override, its `nopy.cubes` is malformed, or an entry points at a directory that does not exist or lies outside the package.
#### Ids are claimed globally