Closed JounQin closed 8 months ago
Latest commit: 7ef996405e4c99aeab942cf6a44354fe5c24a7ac
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
This pull request is automatically built and testable in CodeSandbox.
To see build info of the built libraries, click here or the icon next to each commit SHA.
Path | Size |
---|---|
src/index.ts | 981 B (+2.73% 🔺) |
Attention: 1 lines
in your changes are missing coverage. Please review.
Comparison is base (
5055759
) 85.45% compared to head (7ef9964
) 86.04%.
Files | Patch % | Lines |
---|---|---|
src/processFiles.ts | 75.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@JounQin What about bumping the minimum Node.js version as well? Currently pretty-quick
supports Node.js >= 10
.
@JounQin What about bumping the minimum Node.js version as well? Currently
pretty-quick
supportsNode.js >= 10
.
I've already bumped to >=14.8.0
for top level await. See also https://github.com/prettier/pretty-quick/pull/182/files#diff-795f9cd3f5b7c419d737cc16d57e6c86dac57b1e2656da6d436645bdbd264fc6R15
(But Should we do this? Or keep >=14
same as prettier
)
I decided to support >=14
because the efforts are just small.
Should prettier/prettier#15337 be reverted and pretty-quick
be added back to the docs of pre-commit solutions?
close #164
Waiting https://github.com/prettier/pretty-quick/pull/180#issuecomment-1894971802
cc @SukkaW