tool · inferred from evidence
yarn
A JavaScript package manager.
- Doesn't work with a new repo when using npm [turborepo]
When turbo run dev executes nothing or loops on a new npm repo, check for stray lockfiles and odd package.json variants: a package-lock.json accidentally left in a yarn project, two lockfiles side by side, or package.json5 (turbo doesn't re
- Error: @vercel/edge-config: Network error
How to fix error: @vercel/edge-config: Network error (Vercel Blob). The verified answer from the upstream issue, distilled into steps.
- error after yarn dev
Switch poetry to the right interpreter with the full path: `poetry env use /full/path/to/python` (`poetry env use $(which python)` works if python is on your PATH).. (E2B; via gh:e2b-dev/e2b#3)
- Webpack failure TypeError: hexoid is not a function
A practical guide for Auth0. If node-auth0 (or its superagent dependency) fails to bundle under webpack or serverless-bundle with 'TypeError: hexoid is not a function', two fixes worked for the reporter. One: disable Formidable in the bundl
- strcpy_chk: symbol not found
How to fix 'strcpy_chk: symbol not found' in Turso, straight from the verified resolution in gh:tursodatabase/libsql-client-ts#180. Root cause plus what to change.
- Renovate lockfiles not being updated in dependency PRs
Renovate lockfiles not being updated in dependency PRs. This was a Renovate regression fixed in version 23.70.1, upgrade to that release or later.
- sync-wasm connect() fails with "unexpected path ... .db-log: files must be created in advance for OPFS IO"
Fixed in PR #8524, which registers the MVCC log path with the OPFS worker before the sync engine connects. Use `@tursodatabase/sync-wasm` 0.8.0-pre.9 or newer.
- The ENCORE_RUNTIME_LIB environment variable is not set (yarn start on Windows)
ENCORE_RUNTIME_LIB points Encore at its native runtime binary, and when you launch with plain node or npm run test the variable is never set. The supported paths are to run the app with the Encore CLI (encore run) and run tests with encore