Docs/442 ci troubleshooting guide - #513
Merged
El-swaggerito merged 2 commits intoJul 29, 2026
Merged
Conversation
Closes Axionvera#442 Contributors hitting a failing check (TypeScript, lint, tests, Expo config, dependency install) had no single place documenting the local command to reproduce it or how to fix it. - Add docs/ci-troubleshooting.md: the four local commands that mirror CI (npm install --legacy-peer-deps, npm run typecheck, npm run lint, npm test), plus fixes for the failure patterns actually reproduced while writing this guide in this repo: - Peer dependency conflicts requiring --legacy-peer-deps - Multiple lock files (pnpm-lock.yaml/bun.lock alongside package-lock.json) causing Expo tooling to pick the wrong package manager, observed as `spawn bun ENOENT` when `expo lint` tried to auto-install eslint via bun - TypeScript syntax-error cascades (JSX parent element / unclosed brace errors) - Jest "Unexpected token 'export'" from an untransformed ESM dependency (lucide-react-native) missing from transformIgnorePatterns - Empty test files ("must contain at least one test") - Async test timeouts from unmocked dependencies - expo-doctor's network-dependent config-schema check failing in offline/sandboxed environments - A "clean install" recovery sequence - What reviewers/GrantFox evaluators expect from a green PR - Add "lint": "expo lint" to package.json so the guide (and CONTRIBUTING.md) can reference npm run lint consistently with npm run typecheck / npm test, instead of a bare npx invocation. - Link the guide from README.md, CONTRIBUTING.md's PR checklist, and mobile-onboarding-checklist.md's new "Common CI Failures" pointer. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #
Test Plan and Evidence
Self-Assessment
Complete the
Contributor Self-Assessment before
requesting review. Include concise evidence below; use
Not applicable — <reason>instead of leaving a required area unexplained.or unfinished work.
or a no-test justification is provided.
latest commit.
screenshots, and links are updated, or no update is needed.
and follow-up work are disclosed below.
or verification evidence below.
CI Status
Documentation
Known Limitations
Acceptance Criteria
Screenshots or Recordings