Using cache on CI may cause issues when babel plugin version changes
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 696
- Avg merge
- 8m
- Merged PRs (30d)
- 7
Description
We started using metro cache on our CI as a result of the following note:
We encounter issues, reset cache solve that
We stopped using metro cache on our CI due to that issue
The issues related to babel plugin version changes
Does it a known limitation or there is a solution for that?
Contributor guide
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
No files, tests, or entry points are named in the issue. Start by reproducing the CI build with Metro cache enabled while changing a Babel plugin version, compare it with a cache reset, and establish whether the behavior is a known limitation or whether a documented solution exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- babel, javascript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100