Migrate project to Prettier 3.0.0-alpha.4, run tests against Prettier v1 and v2

[kachkaev]

Closes #30

[codecov]

Codecov Report

Base: 94.68% // Head: 95.28% // Increases project coverage by +0.60% 🎉

Coverage data is based on head (705d3b4) compared to base (0780588).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #36      +/-   ##
==========================================
+ Coverage   94.68%   95.28%   +0.60%     
==========================================
  Files           5        6       +1     
  Lines          94      106      +12     
  Branches       14       16       +2     
==========================================
+ Hits           89      101      +12     
  Misses          4        4              
  Partials        1        1              

Impacted Files	Coverage Δ
src/parser.ts	88.88% <100.00%> (+0.65%)	⬆️
src/test-helpers/prettier-wrapper.ts	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[fisker]

Why don't you do

yarn upgrade prettier@1
yarn test

https://github.com/prettier/angular-estree-parser/blob/09541d0d2ae5d99f17477cae597fa6b743a4a415/.github/workflows/ci.yml#L39

[kachkaev]

👋 @fisker! I was thinking of doing something like that in CI, but then decided to include three local Prettier versions. This way I can switch between them on the fly while keeping git status clean. I might switch to yarn upgrade in CI at some point, but I don’t see any problems with the current approach at the moment.

Thanks for taking a look at this PR, let me know if you have any other thoughts!