Skip to content

Releases: stitchesjs/stitches

v0.1.3

25 Mar 17:57
Compare
Choose a tag to compare

Beta Release: 0.1.3 🚀

yarn add @stitches/react@0.1.3
  • Adjusts the insertion method to reduce DOM writes

Migrating from alpha to beta? Here’s a migration guide.

v0.1.2

23 Mar 18:05
Compare
Choose a tag to compare

Beta Release: 0.1.2 🚀

yarn add @stitches/react@0.1.2
  • Polyfills the vendor-prefixed sizing values stretch and fit-content.
  • Maps the outline property to the color theme token.
  • Run utilities for properties instead of polyfills, instead of running them beforehand.
  • Update the DOM even more sparingly.

Migrating from alpha to beta? Here’s a migration guide.

v0.1.1

23 Mar 17:46
Compare
Choose a tag to compare

Beta Release: 0.1.1 🚀

yarn add @stitches/react@0.1.1
  • Polyfills the vendor-prefixed sizing values stretch and fit-content.
  • Maps the outline property to the color theme token.
  • Run utilities for properties instead of polyfills, instead of running them beforehand.
  • Update the DOM even more sparingly.

Migrating from alpha to beta? Here’s a migration guide.

v0.1.0-canary.21

22 Mar 15:31
Compare
Choose a tag to compare
v0.1.0-canary.21 Pre-release
Pre-release
  • Added polyfills for vendor-prefixed properties and logical shorthands.
  • Removed default exports from @stitches/core and @stitches/react.
  • Replaced when responsive property container with the ability to insert breakpoints alongside properties like @bp1.
  • Renamed conditions to media, changing its values from strings like "@media (min-width: 640px)" to "(min-width: 640px)".
  • Renamed insertMethod option to insertionMethod.
  • Reduced TSC issues by half.

v0.1.0-canary.20

12 Mar 21:01
Compare
Choose a tag to compare
v0.1.0-canary.20 Pre-release
Pre-release

Canary Release: 0.1.0-canary.20 🚀

yarn add @stitches/react@0.1.0-canary.20
  • Reduced DOM writes by up to 100%. ("Nothing to write home about.")

Migrating from alpha to beta? Here’s a migration guide.

v0.1.0-canary.19

12 Mar 20:58
Compare
Choose a tag to compare
v0.1.0-canary.19 Pre-release
Pre-release

Canary Release: 0.1.0-canary.19 🚀

yarn add @stitches/react@0.1.0-canary.19
  • Fixed an issue where certain property number values were wrongly not converted to px ("Sorry, wrong number.")

Migrating from alpha to beta? Here’s a migration guide.

v0.1.0-canary.18

11 Mar 21:03
Compare
Choose a tag to compare
v0.1.0-canary.18 Pre-release
Pre-release

Canary Release: 0.1.0-canary.18 🚀

yarn add @stitches/react@0.1.0-canary.18
  • Fixed an issue where certain property number values were wrongly converted to px ("Mad props" or "Strength in numbers")

Migrating from alpha to beta? Here’s a migration guide.

v0.1.0-canary.17

11 Mar 20:59
Compare
Choose a tag to compare
v0.1.0-canary.17 Pre-release
Pre-release

Canary Release: 0.1.0-canary.17 🚀

yarn add @stitches/react@0.1.0-canary.17
  • Fixed an issue where empty responsive variants rendered nesting incorrectly. ("Empty nesters now welcome.")

Migrating from alpha to beta? Here’s a migration guide.

v0.1.0-canary.16

09 Mar 22:35
Compare
Choose a tag to compare
v0.1.0-canary.16 Pre-release
Pre-release

Canary Release: 0.1.0-canary.16 🚀

yarn add @stitches/react@0.1.0-canary.16
  • Fixed an issue where React.forwardRef components were not handled correctly. ("And for reference, I was looking forward to that.")

And another thanks to @arempe93 for contributing to the diagnosis and solution. ✨

Migrating from alpha to beta? Here’s a migration guide.

v0.1.0-canary.15

09 Mar 01:44
Compare
Choose a tag to compare
v0.1.0-canary.15 Pre-release
Pre-release

Canary Release: 0.1.0-canary.15 🚀

yarn add @stitches/react@0.1.0-canary.15
  • Fixed an issue where @keyframes rules were no longer committed to CSS. ("Hey, where’d my keys go?")
  • Fixed an issue where numeric properties were not correctly transforming into or avoiding px units. ("Px or it didn't happen.")
  • Fixed an issue where insertMethod appeared required. ("You’re just not my type." or "Well, that’s one way to promote adoption.")

A big thanks to @arempe93 for flagging the issue with numeric properties and also submitting a fix!