Nathan Rajlich
e1e64e3de3
* docs: apply Vercel technical writing standards Audit the complete documentation corpus, package READMEs, skills, and source TSDoc/comments against the vercel-technical-writing skill and style-rules.md. Normalize sentence-case headings without changing published anchors, remove prose em dashes and filler wording, improve active voice and self-contained phrasing, standardize product/brand capitalization, American English, list punctuation, units, and code fence languages, and preserve exact runtime strings/table placeholders. All executable code is unchanged. Modified skills have their metadata versions bumped. * docs: extend writing audit to repository Markdown Apply the same technical-writing rules to design documents, compiler specifications, workbench guides, package changelogs, and the remaining tracked Markdown outside the deployed docs corpus. Preserve historical meaning, commands, output literals, table placeholders, and heading anchors. * docs: exclude generated package changelogs from audit
tarballs
Static Vercel project that builds and serves preview tarballs for every public package in packages/*.
For each public package, scripts/pack.ts:
- Rewrites the package version to
<version>-<git-sha>, updates generated version files to match, and rewrites every workspace dependency to a tarball URL on the current Vercel deployment (https://$VERCEL_URL/<escaped-name>.tgz). - Runs
pnpm packand writes the result topublic/<escaped-name>.tgz. - Restores the original
package.jsonand generated version files.
It also generates a public/index.html that lists every published package alongside a copyable pnpm i … command, so the bare deployment URL is itself useful when shared.
The deployment serves the resulting *.tgz files at the root of the project URL. For example, https://<deployment>.vercel.sh/workflow.tgz.
This is used for pre-release testing of vercel/workflow PRs by installing tarballs directly:
{
"dependencies": {
"workflow": "https://<deployment>.vercel.sh/workflow.tgz"
}
}
The Vercel project must be configured to be publicly accessible (no Deployment Protection on previews or production) so that pnpm/npm can fetch tarball URLs from third-party projects. The smoke check (scripts/check-tarballs-smoke.mjs) verifies this on every deployment and fails loudly if the deployment is behind a login redirect.