Published as @profullstack/sh1pt@0.3.0 . This is the first release you can actually install. 0.2.0 could not be: the cli declared a dependency on @profullstack/sh1pt-openapi , which had never been published, so npm i @profullstack/sh1pt ended in a 404 before it got anywhere. The cause was a gap between two lists. The cli depends on six workspace packages, and pnpm rewrites workspace: into a real…
sh1pt: release v0.2.0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Reported: pasting a Cookie Editor JSON export into LinkedIn setup silently failed with "couldn't find required cookie li_at". The masked password prompt redraws an asterisk per character, which mangles long pastes in many terminals; my JSON parser then hit malformed input and returned {} with no diagnostic. Three fixes: Visible 'text' prompt for the paste-all step. Long pastes go through cleanly…
`const [name] = id.split('@')` is undefined when id is empty under noUncheckedIndexedAccess, which the workspace's strict tsconfig turns on. The CI publish build (now fanning out to all 200+ adapters) tripped over it. Use `?? id` and fall back to '_' for the bucket char so the URL is always well-formed. Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
Was: the CLI told you which package to install and made you run it yourself. Now: detect which PM put sh1pt on disk (same logic as `sh1pt update`), check whether the wanted adapter is already in that PM's global node_modules, and if not, run ` add -g <pkgs...>` with stdio inherited so the user sees the native PM logs. No prompt. Wired into every place the CLI lazy-imports an adapter: `sh1pt…
Bun returns instantly from `bun add -g pkg@latest` when its cache holds an older tag; the [4ms] "install" path keeps users stranded on whatever version they last had. Pass --force on bun/aube and --prefer-online on pnpm/npm so update actually re-checks the registry every time. No core changes; cli only. 0.1.7 → 0.1.8. Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
Was hardcoded to 0.1.0; bun/pnpm/npm install 0.1.6+ but sh1pt -V kept reporting the dev placeholder. createRequire('../package.json') resolves at runtime to the package root from both dist/ and tsx src/, so the printed version always tracks what the package manager installed. Drive-by: route libsodium-wrappers through createRequire too — its ESM bundle is broken (modules-esm/libsodium-wrappers.mjs…
chore: release sh1pt v0.1.6
chore: release sh1pt v0.1.5
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com