tftsr-devops_investigation/node_modules/import-meta-resolve/index.js
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

48 lines
1.3 KiB
JavaScript

/**
* @typedef {import('./lib/errors.js').ErrnoException} ErrnoException
*/
import {defaultResolve} from './lib/resolve.js'
export {moduleResolve} from './lib/resolve.js'
/**
* Match `import.meta.resolve` except that `parent` is required (you can pass
* `import.meta.url`).
*
* @param {string} specifier
* The module specifier to resolve relative to parent
* (`/example.js`, `./example.js`, `../example.js`, `some-package`, `fs`,
* etc).
* @param {string} parent
* The absolute parent module URL to resolve from.
* You must pass `import.meta.url` or something else.
* @returns {string}
* Returns a string to a full `file:`, `data:`, or `node:` URL
* to the found thing.
*/
export function resolve(specifier, parent) {
if (!parent) {
throw new Error(
'Please pass `parent`: `import-meta-resolve` cannot ponyfill that'
)
}
try {
return defaultResolve(specifier, {parentURL: parent}).url
} catch (error) {
// See: <https://github.com/nodejs/node/blob/45f5c9b/lib/internal/modules/esm/initialize_import_meta.js#L34>
const exception = /** @type {ErrnoException} */ (error)
if (
(exception.code === 'ERR_UNSUPPORTED_DIR_IMPORT' ||
exception.code === 'ERR_MODULE_NOT_FOUND') &&
typeof exception.url === 'string'
) {
return exception.url
}
throw error
}
}