@point-seven-studio/jq-deck 0.3.1 → 0.3.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.
- package/README.md +6 -0
- package/dist/index.mjs +784 -123
- package/dist/jq-deck.mjs +855 -158
- package/dist/types/cli.d.ts +4 -0
- package/dist/types/page.d.ts +2 -1
- package/dist/types/presence.d.ts +38 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -89,6 +89,12 @@ console.log(overview.headline)
|
|
|
89
89
|
- Everything each tool lists as a limit applies here: jq-agents depends on Claude Code internals and samples resources on macOS only; a mailbox has no access control.
|
|
90
90
|
- Every page load reads again. With many repositories the Overview runs the setup check on each, which takes a moment.
|
|
91
91
|
|
|
92
|
+
## Links to the other tools
|
|
93
|
+
|
|
94
|
+
The served page has a bar at the bottom with a link to each of the other JQ tools. A tool that is running on this machine is a link to the port it is really on. One that is not says "not running" and gives the command that starts it. The team board is a link when `~/.jq/config.json` holds a `"team"` line with its address, and says "not set up" otherwise.
|
|
95
|
+
|
|
96
|
+
How a page knows what is running, without a network call: while a tool serves its page it keeps a small note in `~/.jq/running/` (the tool, its port, its process id), and removes it when it stops. The other pages read those notes and ignore one whose process is gone. The bar is as of the last page load. A page written with `--html`, or shown inside JQ Deck, has no bar.
|
|
97
|
+
|
|
92
98
|
## Related tools
|
|
93
99
|
|
|
94
100
|
- [jq-deck-server](https://www.npmjs.com/package/@point-seven-studio/jq-deck-server): the same view for a team, across machines.
|