fix: sale price comparison

[dylandepass]

Summary

This PR fixes a critical bug in the formatPrice function. The old formatPrice logic compared prices as strings instead of numbers, which broke sale-price detection. Example: "9" is considered greater than "100" in a string comparison, even though 9 is obviously less than 100. The fix switches the comparisons to numeric by wrapping the values in parseFloat(), so sale prices resolve correctly again.

Changes

Core Implementation

• src/steps/render-body.js: Modified price comparison to use parseFloat(final) < parseFloat(regular) instead of direct string comparison
• src/steps/render-body.js: Exported formatPrice function to enable unit testing

Test Coverage

• test/steps/render-body.test.js: Added comprehensive test suite with 206 test cases covering:
  • Null and empty cases
  • Regular pricing (no sale)
  • Sale pricing scenarios
  • String-to-number conversion edge cases
  • Invalid/NaN handling
  • Zero and negative price handling
  • Decimal precision and large numbers
• ✅ Maintains 100% code coverage (270 tests passing, 100% coverage across all metrics)

Example

Before (Bug)

// String comparison: "9" > "100" (lexicographic)
formatPrice({ final: "9.99", regular: "100.00" })
// Incorrectly displayed as: $9.99 (regular price, no strikethrough)

After (Fixed)

// Numeric comparison: 9.99 < 100.00
formatPrice({ final: "9.99", regular: "100.00" })
// Correctly displayed as: $9.99 ($100.00) (with strikethrough on $100.00)

[github-actions]

🎉 This PR is included in version 1.9.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀