Recordsnpmtypescript5.8.2compilerOptions.baseUrl
Published samples
- typescript 5.8.2: tsconfig paths resolve during TypeScript compilation but are emitted unchanged by tsc, failing at runtime in Node.js without package subpaths or bundler alias plugins This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWts.resolveModuleNamets.transpileModulecompilerOptions.pathscompilerOptions.baseUrlnode MIT-0 · 2026-08-15
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-18 |
snapshot · 2026-09-15
Failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×3 5.8.2 → 6.0.3 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-09-06Diagnostic re-verification candidate