(lint-staged) Fix prettier error 'No parser could be inferred for file' using pnpm #34
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It seems to be working fine on npm and yarn. Thanks for pointing this out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using pnpm as package manager, when commit an Astro template, prettier throw the error 'No parser could be inferred for file: ...'.
To reproduce you can create a new branch, install the packages with
pnpm install, modify an Astro template (ex. src/pages/index.astro) and try to commit.Adding the parameter
--plugin-search-dir=.to prettier command inlint-stagedsection ofpackage.jsonsolved the problem for me. I found the solution in this comment for more details.