-
-
Notifications
You must be signed in to change notification settings - Fork 448
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
Deno support #3330
Comments
This issue has been labeled as stale due to inactivity. Reply to keep this issue open. |
As far as I'm aware this hasn't been addressed or triaged. It would be nice if this extension worked as well with Deno as it does with a project containing a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Do you have any suggestions for using the VS Code Prettier extension in a Deno project (which doesn't have
package.json
ornode_modules
) and specifying a specific version to match the project?We're able to run Prettier as a script locally and on CI with these tasks configured in
deno.jsonc
:but Deno's Prettier install isn't resolved by this extension.
Describe the solution you'd like
It would be nice to have the extension resolve the version of Prettier installed by Deno or be able to pick a fallback version.
Describe alternatives you've considered
I've tried installing Prettier with npm up a directory or globally installing it and enabling
Prettier: Resolve Global Modules
but couldn't seem to get the extension to resolve that Prettier instance.Additional context
I'd assume that other frameworks without npm or things like Yarn PnP would have similar issues.
The text was updated successfully, but these errors were encountered: