-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
prettierPath only works via CLI option, not config #7406
Comments
It seems that argv has a default value for |
Hmm, @azz is that intentional? |
I refuse to believe this is intentional (if it is I'll argue against it), so PR very much welcome 🙂 |
Definately not intentional |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🐛 Bug Report
When specifying the
prettierPath
option in a config file or JSON object, it is ignored. Jest prints the warning:By putting a
console.log
in the module at the specifiedprettierPath
, it is apparent that Jest never even attempts to import the supplied path. The value that eventually makes it togetPrettier()
in thejest-jasmine2
package isnull
.Using the same value with
--prettierPath
via the CLI works.To Reproduce
Specify the
prettierPath
option in a config file or--config
JSON object.Expected behavior
The provided path will be used for Prettier.
Link to repl or repo (highly encouraged)
Please provide either a repl.it demo or a minimal repository on GitHub.
Issues without a reproduction link are likely to stall.
Run
npx envinfo --preset jest
Paste the results here:
The text was updated successfully, but these errors were encountered: