-
-
Notifications
You must be signed in to change notification settings - Fork 48
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 3.0 #171
Comments
More info in this PR |
Any update on this ? |
This issue is stale because it has been open for 14 days with no activity. |
Please fix this. I can no longer use your plugin and I have severe health problems. I need this automation. |
Please fix it, thank you. |
Any update on this? |
prettier/prettier-eslint#901 just got merged. |
Any update? Much appreciated |
Seems like this should be fixed by #187 |
Sorry for the lack of response. I've been dealing with medical issues in addition to everything else. Someone created a PR to update everything (#189) but it needs some changes and I don't have much time to help. Also, the automated deploy isn't working and could use some help there. |
I did a little testing of #189 and upgrading to Prettier 3 is not an option at this time. I am getting the same error as prettier/prettier-vscode#3114 describes when I try to run my extension. Prettier 3 added a dynamic |
Do you still need help resolving automated deploys? |
@KillDozerX2 I do still need help with automated deploys. I'm using Auto (docs) to automate the deploys. I think I have it setup wrong. When I run the release workflow it should see there is a new version and publish the extension, but it doesn't. Here is their example: https://intuit.github.io/auto/docs/build-platforms/github-actions I think it only works with this workflow: https://intuit.github.io/auto/docs/generated/shipit#release-pipeline |
I would recommend to migrate to And it maybe great to migrate this repo into the |
I created something based on your work @idahogurl. Tested with:
(https://github.com/0x2aff/vscode-prettier-eslint) |
@0x2aff I actually tried using worker threads as well but it wasn't applying the Prettier config in my tests. I'll have to try your code and see if I can't get my tests to pass. |
Or you can try https://github.com/un-ts/synckit to simplify. |
@0x2aff I tried your extension and it has the same problem with my test file. I'll create an issue in your repository and provide the files needed to reproduce. |
Here is a PR attempting to fix the issue, does it works for you? #198 |
Click here to create a branch for this issue |
Branch 171-prettier-3-0 |
I do have a beta version of the extension working with Prettier 3. It has some breaking changes:
Download and install the extension from here: Once I have enough people testing it, I will making it available as a general release. Let me know if you find any issues with it. |
@idahogurl The latest beta version works great for me. I'm not seeing any noticeable delay when formatting. |
@netux @jaschaephraim Try this version. I preloaded the worker. |
@idahogurl beta 2 performs just like beta 1, still a short delay on the first run only |
I installed
Any idea what else could be missing? |
@jaulz All I can think of is having you restart VS Code and creating a minimal reproduction project. |
what versions of |
I've been struggling with lack of format on save all day and haven't found a solution. I'll just add my +1. |
@Jmyerzzz @uberubert Format on save should be working. Can you provide further information as to exactly isn't working and perhaps a minimal reproduction project? Also, what version of VS Code are you running? I've been using the beta for a while now and haven't had issues. Last thing, have you checked the Output (described in the README in the troubleshooting section)? If there is an error it will show up there. |
@idahogurl Using beta 1 at the moment in a mid-sized monorepo and not seeing any issues with formatting. However if I change my prettier or eslint config files I have to reload VSCode in order for the extension to pick up the changes and format properly again. Otherwise it works great, thank you for maintaining this extension 👍. |
VSCode v1.85.1 Output: |
@Jmyerzzz You need to download and install the beta 1 version of the extension. Use this link |
@netux @jaschaephraim Please try this new version to see if it speeds things up |
Still seeing the same short delay on the first format, very fast after that. |
I've been using beta3 all morning, It seems to be working fine! I'll be using it daily, so unless I report back, it's safe to assume that it's working well for me as well.
|
Beta 3 is working well for me |
If you go to vscode settings and find My vscode keeps adding it back somehow then |
@idahogurl
Beta 1 doesn't have this issue. VSCode:
|
@novarolV Can you help to test via PR based of https://github.com/idahogurl/vs-code-prettier-eslint/pull/199/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R59 and #199 (comment) |
@JounQin @idahogurl I created a PR with proposed change to fix the file path error on Windows. |
Beta 3 works great in my project. Thank you! |
@idahogurl you are doing an awesome job here <3 Do we have any eta? Stay well! |
@idahogurl The v6 tag/release is missing. |
Works great. Thank you! |
Branch 171-prettier-3-0 |
Prettier just released a new major version which includes some breaking changes to the API. Currently Prettier 3.0 causes the extension to throw a type error:
I haven't looked into the source code for Prettier or this extension for a while so I don't know how difficult of a fix this is.
If anyone is having this same issue, the short term solution is to explicitly install a version of prettier before 3.0.
The text was updated successfully, but these errors were encountered: