tglider 0.1.0 → 0.2.0
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 +8 -27
- package/dist/index.js +1 -1
- package/dist/release-metadata.json +5 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,8 +2,6 @@
|
|
|
2
2
|
|
|
3
3
|
TGlider is a semantic TypeScript and JavaScript MCP server for code navigation, workspace intelligence, dependency topology, diagnostics, and refactoring.
|
|
4
4
|
|
|
5
|
-
TGlider packages include release metadata and expire 30 days after their release date. Update to the latest `tglider` package when the server warns that the build is close to expiry. Preview builds are available on the `alpha` dist-tag.
|
|
6
|
-
|
|
7
5
|
## Requirements
|
|
8
6
|
|
|
9
7
|
- Node.js 24 or newer.
|
|
@@ -25,20 +23,15 @@ Use the stable package for normal MCP client configuration:
|
|
|
25
23
|
}
|
|
26
24
|
```
|
|
27
25
|
|
|
28
|
-
|
|
26
|
+
## LLM Agent System Prompt
|
|
29
27
|
|
|
30
|
-
|
|
31
|
-
npm install -g tglider
|
|
32
|
-
tglider
|
|
33
|
-
```
|
|
28
|
+
After connecting the server, add this instruction to the MCP client system prompt so the agent uses compiler-backed workspace facts before raw text search:
|
|
34
29
|
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
```sh
|
|
38
|
-
npx -y tglider@alpha
|
|
30
|
+
```text
|
|
31
|
+
When working in TypeScript or JavaScript workspaces, prefer tglider mcp semantic tools before grep, rg, or find for code navigation and refactoring. Use TGlider for symbols, declarations, references, implementations, exports, package importers, project and dependency topology, diagnostics, callers, outgoing calls, impact analysis, and preview-first rename or refactor planning. Use shell text search only for non-code assets, files outside the loaded workspace, generated output, or after TGlider cannot load or cannot answer the question.
|
|
39
32
|
```
|
|
40
33
|
|
|
41
|
-
##
|
|
34
|
+
## CLI Arguments
|
|
42
35
|
|
|
43
36
|
```sh
|
|
44
37
|
tglider --help
|
|
@@ -61,21 +54,9 @@ TGlider exposes MCP tools for:
|
|
|
61
54
|
- semantic symbol search, symbol lookup at position, definitions, declarations, references, implementations, and type hierarchies
|
|
62
55
|
- project dependency topology, dependency paths, file dependents, and cycles
|
|
63
56
|
- API/export discovery and compact semantic queries
|
|
64
|
-
- call graph inspection, cascade impact summaries, conservative unused-code discovery,
|
|
57
|
+
- call graph inspection, cascade impact summaries, conservative unused-code discovery, preview-first rename/refactor planning, and language-service formatting
|
|
65
58
|
- live document open/update/close workflows for editors and agents
|
|
66
59
|
|
|
67
|
-
##
|
|
68
|
-
|
|
69
|
-
Packages are intentionally short-lived. If startup reports that your build has expired, update your installation or keep using the `npx -y tglider` MCP configuration.
|
|
60
|
+
## Version Expiration Notice
|
|
70
61
|
|
|
71
|
-
|
|
72
|
-
npm install -g tglider
|
|
73
|
-
```
|
|
74
|
-
|
|
75
|
-
`tglider --help` and `tglider --version` continue to work after expiry.
|
|
76
|
-
|
|
77
|
-
Alpha builds remain available for early testing:
|
|
78
|
-
|
|
79
|
-
```sh
|
|
80
|
-
npm install -g tglider@alpha
|
|
81
|
-
```
|
|
62
|
+
TGlider packages include release metadata and expire 30 days after their release date. The recommended `npx -y tglider` MCP configuration resolves the current package when the client launches the server. `tglider --help` and `tglider --version` continue to work after expiry.
|