Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

possible cache collisions when using a tsConfig file with "extends" #749

Closed
huafu opened this issue Sep 22, 2018 · 0 comments · Fixed by #751
Closed

possible cache collisions when using a tsConfig file with "extends" #749

huafu opened this issue Sep 22, 2018 · 0 comments · Fixed by #751
Assignees
@huafu
Labels
🐛 Bug
Milestone
23.10.2

Comments

@huafu
Copy link
Collaborator

huafu commented Sep 22, 2018

Issue :

All in the title ;-)

Expected behavior :

The cache key should take care of resolved tsconfig instead of the input
@huafu huafu added the 🐛 Bug label Sep 22, 2018
@huafu huafu added this to the 23.10.2 milestone Sep 22, 2018
@huafu huafu self-assigned this Sep 22, 2018
huafu added a commit to huafu/ts-jest that referenced this issue Sep 22, 2018
@huafu
fix(cache): resolved tsconfig in cache key + pkg digest
e891608 
- Includes the resolved tsconfig object and not the input one in the
jest cache key.
- Includes a digest of ts-jest's package in the jest cache key.
- Cascade typescript compiler cache dir

Closes kulshekhar#749
@huafu huafu mentioned this issue Sep 22, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@huafu huafu

Labels
🐛 Bug
Projects
None yet
Milestone
23.10.2
Development

Successfully merging a pull request may close this issue.

Fix cache collisions huafu/ts-jest
1 participant
@huafu