v0.1.18
Keep the vendored copies out of this package's coverage floor
src/vendor/** is generated and identical in every package that carries it, so
measuring it here counts the same lines N times and holds this package to a
floor for code it cannot change — which is what pushed several suites under
their thresholds the moment the copies landed.
The behaviour is not left unmeasured: it is pinned where it broke, in bay's
quasar-bridge suite, which now covers both manager shapes the loader has to
accept.
Run cargo with --locked in CI
Without it, cargo rewrites Cargo.lock in place when it has drifted from the
manifests — so CI resolves dependencies fresh and tests a graph nobody
committed, then the release is built from it. The workspace lock had drifted
by 382 lines before the same flag caught it locally.
Every package here commits a Cargo.lock, so --locked is meaningful: it fails
loudly instead of silently updating. Verified against the current lock before
the flag went in.
The Node side is deliberately left alone: these repositories ship no
pnpm-lock.yaml, so --frozen-lockfile has nothing to freeze against, and
resolving from the registry is what a consumer gets anyway.
Take the NAPI platform table from the vendored copy
The map from Node's platform/arch to napi-rs's suffix was repeated here as
well. Adding a target means adding it everywhere, and a package that misses
the edit fails only on that platform.
The table, the path and the require come from scripts/vendor/nativeBinary.ts.
The policy does not: what this package does when the binary is absent, and the
error it raises, stay here — they carry this package's code and its build
instruction, which a shared helper has no business inventing.
Take nodeEnv from the vendored copy
The file was identical to the other packages' copies, line for line, and they
had drifted apart only in their comments — each explaining its own
consequence, which is what made three identical files impossible to diff.
It is generated from scripts/vendor/nodeEnv.ts now and never edited here; the
reason this package cares moved to the decision it explains. It cannot be a
dependency: this package is published and built from its own repository, where
nothing of the workspace exists.
Give the packing hook a timeout of its own
The beforeAll runs package: @c9up/inker@0.1.18
Tarball Contents
dist/augmentations.d.ts
dist/augmentations.d.ts.map
dist/augmentations.js
dist/augmentations.js.map
dist/globals.d.ts
dist/globals.d.ts.map
dist/globals.js
dist/globals.js.map
dist/helpers.d.ts
dist/helpers.d.ts.map
dist/helpers.js
dist/helpers.js.map
dist/identifierGuards.d.ts
dist/identifierGuards.d.ts.map
dist/identifierGuards.js
dist/identifierGuards.js.map
dist/index.d.ts
dist/index.d.ts.map
dist/index.js
dist/index.js.map
dist/InkerProvider.d.ts
dist/InkerProvider.d.ts.map
dist/InkerProvider.js
dist/InkerProvider.js.map
dist/InkerRenderer.d.ts
dist/InkerRenderer.d.ts.map
dist/InkerRenderer.js
dist/InkerRenderer.js.map
dist/InkerRenderError.d.ts
dist/InkerRenderError.d.ts.map
dist/InkerRenderError.js
dist/InkerRenderError.js.map
dist/loadNapi.d.ts
dist/loadNapi.d.ts.map
dist/loadNapi.js
dist/loadNapi.js.map
dist/native/generated.d.ts
dist/native/generated.d.ts.map
dist/native/generated.js
dist/native/generated.js.map
dist/nodeEnv.d.ts
dist/nodeEnv.d.ts.map
dist/nodeEnv.js
dist/nodeEnv.js.map
dist/renderNode.d.ts
dist/renderNode.d.ts.map
dist/renderNode.js
dist/renderNode.js.map
dist/SafeString.d.ts
dist/SafeString.d.ts.map
dist/SafeString.js
dist/SafeString.js.map
dist/services/main.d.ts
dist/services/main.d.ts.map
dist/services/main.js
dist/services/main.js.map
dist/stacks.d.ts
dist/stacks.d.ts.map
dist/stacks.js
dist/stacks.js.map
dist/Templates.d.ts
dist/Templates.d.ts.map
dist/Templates.js
dist/Templates.js.map
dist/testing/index.d.ts
dist/testing/index.d.ts.map
dist/testing/index.js
dist/testing/index.js.map
index.linux-x64-gnu.node
LICENSE
package.json
README.md
Tarball Details
c9up-inker-0.1.18.tgz, which builds and archives the package — a
minute's work on a loaded machine. It inherited the suite's per-test timeout,
sized for tests rather than for a build, so the hook failed under load and
passed when run alone.
Run clippy as a gate, not a note
cargo fmt --check was gating the formatting while nothing gated the
lints that catch a real defect — the one place the compiler stays silent
and clippy does not. Nine of the ten crates in this cohort had the same
hole; only one ran it.
No version change: this gates what is already there, and every crate
passes it today.
Changes since v0.1.17.