-
-
Notifications
You must be signed in to change notification settings - Fork 459
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
this.prettierModule.resolveConfigFile is not a function
error when formatting
#3445
Comments
I am having the same issue. This has started recently. I tried reverting to the previous version, but to no avail. Also of interest, I have other VSCode workspaces in which Prettier is working fine. |
I am also having this issues in one of my workspaces
But other workspaces are having no issues (yet) |
For me the root cause of this was related to this issue found over in Microsoft's vscode-eslint repo. There's a lot at play there, so I'll let the issue speak for itself. |
On my side the issue seems to be solved on its own |
I'm also running into this. I tried disabling the eslint plugin and still had the issue, so I don't think it's related to the issue @bryanjnelson linked. I'm using yarn 4, but I'm not using pnp, which appears to be a key factor in that issue. Prettier Extension Version: 11.0.0 |
Summary
Prettier files a error message when using 'format document with -> prettier'
Github Repository to Reproduce Issue
Steps To Reproduce:
Prettier files a error message when using 'format document with -> prettier'
Expected result
Describe what should have happened.
Actual result
Here's the log:
👇 when I restarted the editor
👇when focusing any editor window
👇when trying 'format document with prettier'
Additional information
VS Code Version: Version: 1.85.2 (Universal)
Prettier Extension Version: 10.4.0
Prettier package version: 3.2.2
Other Libs:
"@trivago/prettier-plugin-sort-imports": "^4.1.1",
"eslint-config-prettier": "8.5.0",
"eslint-plugin-prettier": "5.1.3",
OS and version: Mac OS 13.6.3 (22G436)
Prettier Log Output
The text was updated successfully, but these errors were encountered: