History

Shaun Arman 8839075805 feat: initial implementation of TFTSR IT Triage & RCA application 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>		2026-03-14 22:36:25 -05:00
..
index.js	feat: initial implementation of TFTSR IT Triage & RCA application	2026-03-14 22:36:25 -05:00
license	feat: initial implementation of TFTSR IT Triage & RCA application	2026-03-14 22:36:25 -05:00
package.json	feat: initial implementation of TFTSR IT Triage & RCA application	2026-03-14 22:36:25 -05:00
readme.md	feat: initial implementation of TFTSR IT Triage & RCA application	2026-03-14 22:36:25 -05:00

readme.md

resolve-from

Resolve the path of a module like require.resolve() but from a given path

Install

$ npm install resolve-from

Usage

const resolveFrom = require('resolve-from');

// There is a file at `./foo/bar.js`

resolveFrom('foo', './bar');
//=> '/Users/sindresorhus/dev/test/foo/bar.js'

API

resolveFrom(fromDir, moduleId)

Like require(), throws when the module can't be found.

resolveFrom.silent(fromDir, moduleId)

Returns null instead of throwing when the module can't be found.

fromDir

Type: string

Directory to resolve from.

moduleId

Type: string

What you would use in require().

Tip

Create a partial using a bound function if you want to resolve from the same fromDir multiple times:

const resolveFromFoo = resolveFrom.bind(null, 'foo');

resolveFromFoo('./bar');
resolveFromFoo('./baz');

resolve-cwd - Resolve the path of a module from the current working directory
import-from - Import a module from a given path
import-cwd - Import a module from the current working directory
resolve-pkg - Resolve the path of a package regardless of it having an entry point
import-lazy - Import a module lazily
resolve-global - Resolve the path of a globally installed module