epiq 0.6.8 → 0.6.10
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/dist/index.js +46 -46
- package/dist/mcp.js +49 -49
- package/package.json +2 -2
- package/readme.md +13 -17
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "epiq",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.10",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"description": "EPIQ - CLI based issue tracker",
|
|
@@ -29,7 +29,7 @@
|
|
|
29
29
|
},
|
|
30
30
|
"scripts": {
|
|
31
31
|
"build": "tsc --noEmit",
|
|
32
|
-
"build:npm": "node source/scripts/write-version.mjs && rm -rf ./dist && esbuild source/Index.tsx --bundle --packages=external --platform=node --format=esm --target=node18 --minify --outfile=dist/index.js --banner:js='#!/usr/bin/env node' && esbuild source/mcp/
|
|
32
|
+
"build:npm": "node source/scripts/write-version.mjs && rm -rf ./dist && esbuild source/Index.tsx --bundle --packages=external --platform=node --format=esm --target=node18 --minify --outfile=dist/index.js --banner:js='#!/usr/bin/env node' && esbuild source/mcp/index.ts --bundle --packages=external --platform=node --format=esm --target=node18 --minify --outfile=dist/mcp.js --banner:js='#!/usr/bin/env node'",
|
|
33
33
|
"build:sea:bundle": "node source/scripts/write-version.mjs && rm -rf ./dist && esbuild source/Index.tsx --bundle --platform=node --format=cjs --target=node18 --minify --outfile=dist/sea.cjs",
|
|
34
34
|
"build:sea": "node --build-sea source/config/sea-config.json",
|
|
35
35
|
"build:publish": "npm run build:npm",
|
package/readme.md
CHANGED
|
@@ -8,16 +8,6 @@ Issue tracking is a core part of software development, but it often becomes a pa
|
|
|
8
8
|
|
|
9
9
|
With great attention to user ergonomics and developer experience, epiq makes project management painless and friction free.
|
|
10
10
|
|
|
11
|
-
```
|
|
12
|
-
███████╗██████╗ █ █╗ ██████╗
|
|
13
|
-
██╔════╝██╔══██╗█ █║██╔═══██╗
|
|
14
|
-
█████╗ ██████╔╝█ █║██║ ██║
|
|
15
|
-
██╔══╝ ██╔═══╝ █ █║██║▄▄ ██║
|
|
16
|
-
███████╗██║ █ █║╚██████╔╝
|
|
17
|
-
╚══════╝╚═╝ ╚══╝ ╚═══▀▀╝
|
|
18
|
-
🫡 Never leave your terminal!
|
|
19
|
-
```
|
|
20
|
-
|
|
21
11
|
## What is epiq?
|
|
22
12
|
|
|
23
13
|
Epiq is a vim-inspired issue tracker that brings project management into the terminal. It renders directly in ASCII and persists state as an immutable distributed event log, versioned and synchronized through Git.
|
|
@@ -149,15 +139,21 @@ Clear all filters with `:filter clear`
|
|
|
149
139
|
|
|
150
140
|
Epiq provides a MCP (Model Context Protocol) server for agents to interact with, making it easy to plug into modern agent frameworks.
|
|
151
141
|
|
|
152
|
-
To register Epiq with MCP-compatible clients (e.g. Claude Desktop), add it as a server using the `epiq-mcp` binary. Example configuration
|
|
142
|
+
To register Epiq with MCP-compatible clients (e.g. Claude Desktop), add it as a server using the `epiq-mcp` binary. Example configuration in your `~/.claude.json`:
|
|
153
143
|
|
|
154
144
|
```json
|
|
155
|
-
{
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
145
|
+
"mcpServers": {
|
|
146
|
+
...
|
|
147
|
+
"epiq": {
|
|
148
|
+
"command": "npx",
|
|
149
|
+
"args": [
|
|
150
|
+
"-y",
|
|
151
|
+
"-p",
|
|
152
|
+
"epiq",
|
|
153
|
+
"epiq-mcp"
|
|
154
|
+
]
|
|
160
155
|
}
|
|
156
|
+
...
|
|
161
157
|
}
|
|
162
158
|
```
|
|
163
159
|
|
|
@@ -171,7 +167,7 @@ Epiq uses Git in the background - no manual Git commands are required. Running `
|
|
|
171
167
|
|
|
172
168
|
## Conflict Avoidance & Data Integrity
|
|
173
169
|
|
|
174
|
-
Epiq is designed to provide robustness in a distributed, Git-backed environment where multiple users may update state concurrently. Instead of mutating shared files, Epiq uses an event-sourced model to
|
|
170
|
+
Epiq is designed to provide robustness in a distributed, Git-backed environment where multiple users may update state concurrently. Instead of mutating shared files, Epiq uses an event-sourced model to prevent merge conflicts and make concurrent changes predictable.
|
|
175
171
|
|
|
176
172
|
### Event-sourced state
|
|
177
173
|
|