8839075805
Implements Phases 1-8 of the TFTSR implementation plan. Rust backend (Tauri 2.x, src-tauri/): - Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama - PII detection engine: 11 regex patterns with overlap resolution - SQLCipher AES-256 encrypted database with 10 versioned migrations - 28 Tauri IPC commands for triage, analysis, document, and system ops - Ollama: hardware probe, model recommendations, pull/delete with events - RCA and blameless post-mortem Markdown document generators - PDF export via printpdf - Audit log: SHA-256 hash of every external data send - Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2) Frontend (React 18 + TypeScript + Vite, src/): - 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings - 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives - 3 Zustand stores: session, settings (persisted), history - Type-safe tauriCommands.ts matching Rust backend types exactly - 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs) DevOps: - .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push - .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload Verified: - cargo check: zero errors - tsc --noEmit: zero errors - vitest run: 13/13 unit tests passing Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
72 lines
1.8 KiB
Markdown
72 lines
1.8 KiB
Markdown
# cli-width
|
|
|
|
Get stdout window width, with four fallbacks, `tty`, `output.columns`, a custom environment variable and then a default.
|
|
|
|
[](http://badge.fury.io/js/cli-width)
|
|
[](https://travis-ci.org/knownasilya/cli-width)
|
|
[](https://coveralls.io/github/knownasilya/cli-width?branch=master)
|
|
|
|
Tested against Node v12 to v20.
|
|
Includes TypeScript types.
|
|
|
|
## Usage
|
|
|
|
```
|
|
npm install --save cli-width
|
|
```
|
|
|
|
```js
|
|
const cliWidth = require('cli-width');
|
|
|
|
cliWidth(); // maybe 204 :)
|
|
```
|
|
|
|
You can also set the `CLI_WIDTH` environment variable.
|
|
|
|
If none of the methods are supported, and the environment variable isn't set,
|
|
the default width value is going to be `0`, that can be changed using the configurable `options`.
|
|
|
|
## API
|
|
|
|
### cliWidth([options])
|
|
|
|
`cliWidth` can be configured using an `options` parameter, the possible properties are:
|
|
|
|
- **defaultWidth**\<number\> Defines a default value to be used if none of the methods are available, defaults to `0`
|
|
- **output**\<object\> A stream to be used to read width values from, defaults to `process.stdout`
|
|
- **tty**\<object\> TTY module to try to read width from as a fallback, defaults to `require('tty')`
|
|
|
|
### Examples
|
|
|
|
Defining both a default width value and a stream output to try to read from:
|
|
|
|
```js
|
|
const cliWidth = require('cli-width');
|
|
const ttys = require('ttys');
|
|
|
|
cliWidth({
|
|
defaultWidth: 80,
|
|
output: ttys.output,
|
|
});
|
|
```
|
|
|
|
Defines a different tty module to read width from:
|
|
|
|
```js
|
|
const cliWidth = require('cli-width');
|
|
const ttys = require('ttys');
|
|
|
|
cliWidth({
|
|
tty: ttys,
|
|
});
|
|
```
|
|
|
|
## Tests
|
|
|
|
```bash
|
|
npm install
|
|
npm test
|
|
```
|
|
|
|
Coverage can be generated with `npm run coverage`.
|