Recordsnpmtldts7.4.12getDomain
OS × runtime at a glance
1 1○ 12026-09-17
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Published samples
- tldts 7.4.12: getDomain, getHostname, getPublicSuffix 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. HOWgetDomaingetHostnamegetPublicSuffixparse MIT-0 · 2026-09-13
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 glibc · docker
Observations: PROJECT_TEST 2✓ — Verified: CONTRACT 1✓
|
LOW | 2 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 4✓
|
LOW | 4 | 0 | 100% | 1 | 2026-09-13 |
| node 24.13 · TS · npm · windows
Observations: PROJECT_COMPILE 36✓ 9✕ · PROJECT_PROCESS 16✓ · PROJECT_TEST 12✓ 2✕ — Verified: PROCESS_START 0✓ 1✕ · UNKNOWN 0✓ 21✕
|
ELEVATED FAILURE | 75 | 22 | 66% | 1 | 2026-09-14 |
snapshot · 2026-09-17
Failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:340c5f78ca35…Image hunterzo-egress-lab:local Building · Image hunterzo-egress-lab:local Built · Network hunterzo-egress-lab_fixture_net Creating …· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 TS7006 ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:341e6d7780ec…src/egress.ts(<n>,<n>): error TS7006: Parameter <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS7034 ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:85a890982324…tests/crawl-budget.test.ts(<n>,<n>): error TS7034: Variable <str> implicitly has type <str> in some locations where its type cannot be determined.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS7005 ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:8dabe9f19999…src/worker.ts(<n>,<n>): error TS7005: Variable <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS7005 ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:9157cca40f14…tests/crawl-budget.test.ts(<n>,<n>): error TS7005: Variable <str> implicitly has an <str> type.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS7034 ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:ac624b80f496…src/worker.ts(<n>,<n>): error TS7034: Variable <str> implicitly has type <str> in some locations where its type cannot be determined.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS2882 ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:afb09a3a1b84…ui/main.tsx(<n>,<n>): error TS2882: Cannot find module or type declarations for side-effect import of <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS2554 ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:b069f147418d…src/egress.ts(<n>,<n>): error TS2554: Expected 2 arguments, but got 3.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS2352 ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:c6b452f5bad2…tests/core.test.ts(<n>,<n>): error TS2352: Conversion of type <str> to type <str> may be a mistake because neither type sufficiently overlaps with the other. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS2349 ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:d6c915113d6a…src/crawl-policy.ts(<n>,<n>): error TS2349: This expression is not callable.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:0cab186a142b…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · 2 !== 0 · at TestContext.<anonymous> (<url>) …javascript/test-runner · test-runner-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 7.4.12 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:53a7d182a4ae…AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: · assert.ok(second.delayMs>0&&second.delayMs<=3000) …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
Showing the 12 most-reported of 32 recorded failure clusters. The rest are single reports.