-
Notifications
You must be signed in to change notification settings - Fork 157
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
Can't resolve path to tsconfig when using tsConfig #148
Comments
Can you please provide a runnable reproduction as a GitHub repository |
i had to add absolute path in order to make it work: This is from jest.config.json in the checkout-ui folder mentioned above. I quickly checked how ts-jest is doing, which seems also to be a good algorithm for vue-jest. |
@eddyerburgh i have seen linked PR, which looks promising. It's for 4.x.x., right? When is v4.0.0-beta.2 to become GA? Is some retrofit to the 3.x.x line planned? |
@janesser thank you for the hint with absolute path. I found a better workaround for now using path.resolve jest.config.js const { resolve } = require("path");
module.exports = {
// ...
globals: {
// ...
"vue-jest": {
tsConfig: resolve("tsconfig.jest.json"),
},
},
}; |
@janesser I haven't planned to add the fix to v3, but I'll accept a PR that adds the fix. |
@eddyerburgh PR set up. Comments welcome. |
The fix is released in v3.0.4, thanks @janesser ! |
Hello!
I upgraded
vue-jest
from 2.6.0 to 3.0.2 and it started to show deprecation message:so I replaced
tsConfigFile
withtsConfig
but it doesn't seem to resolve path properly now for some reasons:Can you give an advice how that can be fixed?
package.json
tsconfig.json
tsconfig.jest.json
The text was updated successfully, but these errors were encountered: