Skip to content

Troubleshooting

$npx linersh@latest --version

Expected current output:

>liner 1.1.1 (tui) · 1.1.1 (core)

If the platform core binary cannot be resolved, the version command prints only the TUI package version.

If compile says a page needs headless Chromium, run:

$npx --yes linersh@latest setup-jsliner setup-js

Use the npx form for one-shot installs, or liner setup-js after a global install. The terminal UI can also run this from the compile screen when it shows the JS rendering callout.

YouTube can block transcript fetching for age-restricted, region-locked, or rate-limited videos. Use a Netscape-format cookies file:

$liner compile mobile-design-foundations --cookies ~/cookies.txt

You can also set a default in ~/.liner/config.toml.

For local development, point the npm TUI at a specific Python core binary:

$LINER_BIN=/path/to/liner liner

The resolver tries LINER_BIN, the bundled platform package, the repo-local virtualenv, then liner on PATH.

$npx --yes linersh@latest uninstall --yesliner uninstall --yes

Use the npx form for one-shot installs, or liner uninstall --yes after a global install. This removes Liner’s local state, Playwright Chromium cache, and npm’s npx execution cache. It is useful when testing a clean npx linersh install.