Skip to content

Conversation

@xesrevinu
Copy link
Member

Signed-off-by: xesrevinu <github-action@actions-template-sync.noreply.github.com>
@xesrevinu xesrevinu merged commit ce944d9 into main Nov 28, 2025
3 of 4 checks passed
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 24 to 27
"typecheck": {
"executor": "nx:run-commands",
"dependsOn": ["^build"],
"options": {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid requiring missing build targets for event-log typecheck

Adding dependsOn: ["^build"] makes nx typecheck pkgs-event-log invoke the build target on every dependency before running the checker. pkgs-event-log imports packages like @xstack/fx/worker/runner, and packages/fx/project.json (and most other workspace libs) define no build target, so the command now errors with “Target build not found for project pkgs-fx” rather than running type checks. Unless every dependency gains a build target, this dependency chain breaks the typecheck target.

Useful? React with 👍 / 👎.

Comment on lines 116 to 120
"expo": "^54.0.25",
"expo-asset": "^12.0.10",
"expo-audio": "^1.0.15",
"expo-bip39": "workspace:*",
"@xstack/expo-bip39": "workspace:*",
"expo-clipboard": "^8.0.7",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep pnpm-lock in sync with renamed expo-bip39 package

The dependency was renamed to @xstack/expo-bip39, but pnpm-lock.yaml still pins the old unscoped expo-bip39 entry (e.g., lines 369–371). With pnpm install --frozen-lockfile the installer now fails because the new specifier has no matching lock entry, blocking installs until the lockfile is regenerated for the scoped name.

Useful? React with 👍 / 👎.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants