v1.1.1

Handle undefined CSS property values

v1.1.1 (2025-05-15)

This patch release improves robustness by gracefully handling undefined values in CSSProperties. Previously, explicitly setting a property to undefined would throw an error during stringification.

✅ Fixed

Avoid crashes from undefined property values in stringifyCSSProperties

Now, properties with undefined values are silently skipped instead of throwing an error.

stringifyCSSProperties({
  color: undefined,
  padding: 10,
});

Before

// Throws: "Invalid input: value of 'cssProperties' must be string or number."

After

// Output: "padding:10px;"

📄 Other

🧪 Added unit tests for undefined values

📝 Added a markdown doc with manual publishing instructions

🔗 Related

Issue: Support undefined for values #11

Thanks @dbondarchuk for bringing this up! 🙌

---

🤖 What's Changed

• build(deps-dev): bump vitest from 2.1.1 to 2.1.9 by @dependabot in #9
• update dependencies by @arkarlov in #10
• Fix: Skip explicit undefined values in stringifyCSSProperties by @arkarlov in #12

New Contributors

• @dependabot made their first contribution in #9

Full Changelog: v1.1.0...v1.1.1