feat: replace parsePackageAuthor with npm package

[kristo-baricevic]

PR Checklist

• Addresses an existing open issue: fixes 🛠 Tooling: Replace parsePackageAuthor with npm package #789
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

#789 parse-author dependency was installed and the parse method was used to replace split and trim logic on the string containing author's name and email

[codecov]

Codecov Report

Merging #904 (2173def) into main (2ea9d87) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #904   +/-   ##
=======================================
  Coverage   93.46%   93.47%           
=======================================
  Files          91       91           
  Lines        4852     4858    +6     
  Branches      405      403    -2     
=======================================
+ Hits         4535     4541    +6     
  Misses        316      316           
  Partials        1        1           

Flag	Coverage Δ
create	71.13% <15.38%> (-0.05%)	⬇️
initialize	38.27% <69.23%> (+0.09%)	⬆️
migrate	69.98% <15.38%> (-0.05%)	⬇️
unit	68.12% <100.00%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...options/createOptionDefaults/parsePackageAuthor.ts	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[kristo-baricevic]

I was working through the checks git showed me, and after running pnpm lint the checks back been stuck on "expected - waiting for status to be reported"

Let me know how the titling and additional info looks! I enjoyed working on this feature.

[JoshuaKGoldberg]

We chatted 1:1 a bit - the merge conflicts are stopping builds from running. And also looks like there are some other changes in the mix.

[kristo-baricevic]

I am not exactly sure what happened there but I do know it happened when I was trying to respond to the red X's in git github checks, and it involved some installs and running npx create-typescript-app. So I backed up the HEAD of the branch to the commit before those changes were made.

[JoshuaKGoldberg]

LGTM, thanks! Clean implementation and passes all the existing tests. Nice.

Once you resolve the merge conflicts we should be good to go. 🚀

[JoshuaKGoldberg]

💯 swell, thanks @kristo-baricevic!

[JoshuaKGoldberg]

Initialization script failures are unrelated. Sorry for the noise :c

[github-actions]

🎉 This is included in version v1.37.0 🎉

The release is available on:

• GitHub releases
• npm package (@latest dist-tag)

Cheers! 📦🚀