overengineeringstudio / overengineeringstudio/effect-utils
Improve pnpm GVS invalidation and install telemetry
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 82
- Forks
- 2
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 121
Description
Context
Live installs now use pnpm 11 global virtual store with a shared files store and workspace-local mutable link metadata. The current implementation deliberately purges GVS link state when policy surfaces change, which is correct but coarse.
Proposal
Explore a more precise strategy:
- partition workspace-local GVS link state by install policy hash instead of deleting it wholesale
- emit task telemetry that distinguishes lockfile, policy, generated-config, and GVS-link invalidation causes
- keep fixed-output Nix dependency prep isolated from live GVS unless a relocatable GVS artifact is proven safe
Acceptance criteria
- Warm
pnpm:installstatus paths explain why they miss. - Policy changes do not force unrelated reinstall work when a hash-partitioned cache can be reused safely.
- FOD prep remains reproducible and does not archive dangling builder-local GVS links.
Posted on behalf of @schickling
| field | value |
|---|---|
agent_name |
🍋 co2-lemon |
agent_session_id |
309e59a9-8084-48d6-a9d8-cea6803d907f |
agent_tool |
Codex CLI |
agent_tool_version |
0.140.0 |
agent_runtime |
Codex CLI 0.140.0 |
agent_model |
unknown |
runtime_profile |
/nix/store/wbb5q5n2gbk751hcyr5ndp0zrmar602x-coding-agent-runtime-profile/share/coding-agents/profile.json |
skills_manifest |
/nix/store/3i12shfqx3wqzq2di3jy1m7f8fn4prmm-agent-skills-corpus/share/agent-skills/manifest.json |
worktree |
effect-utils/schickling/2026-06-19-deps |
machine |
dev3 |
tooling_profile |
dotfiles@unknown-dirty |
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the warm pnpm:install status paths and the current global virtual store link-state purge, then inspect how fixed-output dependency preparation handles GVS links. Done means status misses identify their invalidation cause, reusable policy partitions avoid unrelated reinstall work, and FOD preparation remains reproducible without dangling builder-local links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100