-
Notifications
You must be signed in to change notification settings - Fork 156
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.
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
feat: load TypeScript config from tsconfig
package instead of ts-jest
#471
Conversation
f70abd7
to
83fbdc1
Compare
thanks @nogic1008 - I'm away for 1 week, I can review when I get back. |
@lmiller1990 is there a particular reason this wasn't merged? I'd like to upgrade to the new versions of vue-jest, but I'd rather not have to install ts-jest, since I use babel for my typescript transpilations in my test environment |
@Aaron-Pool good question, my main concern was I am not sure how to handle breaking changes, since we now tie ourselves to Jest versions. I guess it's time to tear of the band-aid, merge this and ship it. I will make this 28.1 - a minor version bump, and include the breaking change in the notes. |
It's out. Thanks all, especially @nogic1008... https://github.com/vuejs/vue-jest/releases/tag/v28.1.0 |
And thank you, sir, for getting back to me so quickly 👏 |
* fix(tsconfig): parse extended tsconfigs when transpiling script blocks A change introduced in v28.1.0 in PR #471 unintentionally changed the behavior of the tsconfig parsing such that configs using "extends" were no longer being considered. Fixes: #495 * chore(cache): cache tsconfig parsing to avoid the cost per vue file / interpolated string Co-authored-by: Adam Hines <ahines@factset.com>
This PR conflicts with #468, so I set as draft.
Resolve #171, #431
Changes
tsconfig
package to load TypeScript config.ts-jest
peerDependencies.Breaking Changes
ts-jest
config.