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>
48 lines
1.8 KiB
Markdown
48 lines
1.8 KiB
Markdown
# string_decoder
|
|
|
|
***Node-core v8.9.4 string_decoder for userland***
|
|
|
|
|
|
[](https://nodei.co/npm/string_decoder/)
|
|
[](https://nodei.co/npm/string_decoder/)
|
|
|
|
|
|
```bash
|
|
npm install --save string_decoder
|
|
```
|
|
|
|
***Node-core string_decoder for userland***
|
|
|
|
This package is a mirror of the string_decoder implementation in Node-core.
|
|
|
|
Full documentation may be found on the [Node.js website](https://nodejs.org/dist/v8.9.4/docs/api/).
|
|
|
|
As of version 1.0.0 **string_decoder** uses semantic versioning.
|
|
|
|
## Previous versions
|
|
|
|
Previous version numbers match the versions found in Node core, e.g. 0.10.24 matches Node 0.10.24, likewise 0.11.10 matches Node 0.11.10.
|
|
|
|
## Update
|
|
|
|
The *build/* directory contains a build script that will scrape the source from the [nodejs/node](https://github.com/nodejs/node) repo given a specific Node version.
|
|
|
|
## Streams Working Group
|
|
|
|
`string_decoder` is maintained by the Streams Working Group, which
|
|
oversees the development and maintenance of the Streams API within
|
|
Node.js. The responsibilities of the Streams Working Group include:
|
|
|
|
* Addressing stream issues on the Node.js issue tracker.
|
|
* Authoring and editing stream documentation within the Node.js project.
|
|
* Reviewing changes to stream subclasses within the Node.js project.
|
|
* Redirecting changes to streams from the Node.js project to this
|
|
project.
|
|
* Assisting in the implementation of stream providers within Node.js.
|
|
* Recommending versions of `readable-stream` to be included in Node.js.
|
|
* Messaging about the future of streams to give the community advance
|
|
notice of changes.
|
|
|
|
See [readable-stream](https://github.com/nodejs/readable-stream) for
|
|
more details.
|