Skip to content

fix(utoopack): use .utoopack for persistent cache - #139

Draft
fireairforce wants to merge 1 commit into
mainfrom
zoomdong/utoopack-cache-directory
Draft

fireairforce wants to merge 1 commit into
mainfrom
zoomdong/utoopack-cache-directory

Conversation

@fireairforce

Copy link
Copy Markdown
Member

Utoopack development and production builds now store persistent cache, lock files, and traces in the application's .utoopack directory instead of the default .turbopack directory.

Upgrade @utoo/pack to ^1.5.19 for cacheDirectory support and update the lockfile. Exclude .utoopack from Git, scaffold copying and packaging, and Turbo test inputs; retain existing .turbopack exclusions for older caches.

Validation on the latest main baseline:

  • npm run check-types
  • npm run lint
  • npm test
  • git diff --check and git diff origin/main --check

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-18T07:07:25.135195Z f0735c8 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@fireairforce
fireairforce marked this pull request as draft September 18, 2026 07:18

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants