feat: support package.json5 and package.yaml

[outslept]

closes #227 :)

[codecov]

Codecov Report

❌ Patch coverage is 90.74074% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.11%. Comparing base (afdf7cb) to head (249b787).
⚠️ Report is 89 commits behind head on main.

Files with missing lines	Patch %	Lines
src/packagejson/utils.ts	90.74%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #234      +/-   ##
==========================================
+ Coverage   89.40%   91.11%   +1.71%     
==========================================
  Files           5       10       +5     
  Lines         434      315     -119     
  Branches       37       72      +35     
==========================================
- Hits          388      287     -101     
+ Misses         46       28      -18     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pi0]

Thanks for PR!

It would be nice if we could merge them also into one simple util like findPackage(), readPackage(), .. this way users can simply use one standard util to support all possible formats (bun for instance allows jsonc for package.json)

[outslept]

If I understand correctly, merging the existing functions (readPackageJSON, writePackageJSON, resolvePackageJSON + the new JSON5/YAML variants) into unified ones would be a breaking change. What concerns me is that we'd either need to maintain both APIs or break existing users who rely on format-specific functions. The unified approach is so clean but requires a major version bump (?). What's do you think?

[pi0]

thats why i suggested to use new readPackage (vs current readPackageJSON) — also for new formats we could merge them directly to it to reduce confusion with many exported utils.

[outslept]

I misunderstood you at first, feel free to review now

[pi0]

Nice impl, thanks ❤️