-
-
Notifications
You must be signed in to change notification settings - Fork 450
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
Prettier resolution broken? #471
Comments
Did you restart VSCode after you update prettier in your project? |
Yes I restarted multiple times... I tried to get that code to log things but I'm not familiar with VSCode and couldn't find a way to those to actually how up anywhere. I'd need a bit of guidance here... |
Is that enought to start ? https://github.com/prettier/prettier-vscode#contribute |
Ok, I think I managed to run this locally and debug the extension. But when I set a break point at the line you've referenced, I never seem to hit that breakpoint. Just to be sure I've added a |
I've managed to get the code execution to break in the constructor of |
In my case, for the first opened file, vscode uses prettier with the correct config, although, after opening any other file, the "format document" starts to format WITHOUT prettier edit: Found the problem. The |
If the formatter is not called, try disabling other extensions :-) |
I did :) And then I ran out of time, also to report back here. What I found was that it was Vetur that was applying the formatting in Vue.js files, also through Prettier in my set-up, but obviously not through the |
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. |
I am aware that as of #39, prettier-vscode should resolve to the locally installed version of prettier, but in my configuration that does not seem to be the case. I have prettier
1.13.2
installed in my project, with the new rules for parentheses in math expressions, but when I use theeditor.formatOnSave
feature of VSCode, these get replaced with the way prettier was handling them in1.12.1
and below. It looks like prettier-vscode is using the internal prettier module, despite #39? And due to #470, prettier-vscode's prettier is still at1.12.1
.I was trying to find some debugging information to provide better information for this issue, but wasn't able to find any. What can I do to understand / log what's going on with my configuration?
The text was updated successfully, but these errors were encountered: