Use lerna/nx cache for build steps
Repository details (talkie)
- Project page
- talkie
- Project log category
- talkie (708 entries)
- Repository
- @joelpurra/talkie
- Owner
- @joelpurra
- Issues
- Issues on Github
- Contributors
- Contributors on Github
- Project status
- ⏲️ This project has had recent commits.
- 📂 This project is open.
- 🌠 This project is popular.
- Repository activity period
- 🗓—
- Commits
- 751 commits
- Stars
- 71 stars
Commit details (adcf4a92)
- Author
- Joel Purra
- Authored at
- Committer
- Joel Purra
- Committed at
Commit message
Use lerna/nx cache for build steps
- Caches per-package files for
buildandreconstructsteps.
- Mainly concerns the output in
dist/directories.- Relies on the inferred package build order.
- Cached output is stored by hash.
- The hash depends on source files,
TALKIE_ENV,node --version, etcetera.- The custom
inputsinnx.jsonmay need to be tweaked to correctly separate (and therefore "invalidate") cached files.- Cached output expires after one week.
- Use
npx nx resetto manually clear on-disk caches.- See
NX_CACHE_DIRECTORY, defaulting to./node_modules/.cache/nx.See
Raw text
Use lerna/nx cache for build steps - Caches per-package files for `build` and `reconstruct` steps. - Mainly concerns the output in `dist/` directories. - Relies on the inferred package build order. - Cached output is stored by hash. - The hash depends on source files, `TALKIE_ENV`, `node --version`, etcetera. - The custom `inputs` in `nx.json` may need to be tweaked to correctly separate (and therefore "invalidate") cached files. - Cached output expires after one week. - Use `npx nx reset` to manually clear on-disk caches. - See `NX_CACHE_DIRECTORY`, defaulting to `./node_modules/.cache/nx`. See - https://nx.dev/recipes/adopting-nx/lerna-and-nx - https://lerna.js.org/docs/concepts/task-pipeline-configuration - https://lerna.js.org/docs/features/cache-tasks - https://nx.dev/recipes/running-tasks/customizing-inputs