Skip to content

Releases: crystal-ball/componentry

v7.2.0

22 Oct 20:42
v7.2.0
08c64aa
Compare
Choose a tag to compare

What's Changed

Full Changelog: v7.1.0...v7.2.0

v7.1.0

22 Oct 20:37
v7.1.0
8e44249
Compare
Choose a tag to compare

What's Changed

Full Changelog: v7.0.0...v7.1.0

v7.0.0 🚀 - Useful utilities

13 Mar 02:58
v7.0.0
1048cc6
Compare
Choose a tag to compare

What's Changed

BREAKING 💥

  • createUtilityClasses has been renamed to createUtilityProps. The return value has been updated to return { filteredProps, utilityClassName, and utilityStyle }
  • initializeUtilityClassesTheme has been renamed to initializeUtilityPropsTheme

Full Changelog: v6.5.0...v7.0.0

v6.5.0

02 Feb 13:37
v6.5.0
9cd2f92
Compare
Choose a tag to compare

What's Changed

Full Changelog: v6.4.0...v6.5.0

v6.4.0

02 Feb 13:37
v6.4.0
edd2fb0
Compare
Choose a tag to compare

What's Changed

Full Changelog: v6.3.0...v6.4.0

v6.3.0

02 Feb 13:37
v6.3.0
4d95e0e
Compare
Choose a tag to compare

What's Changed

  • New: Babel plugin custom import path and transform stats by @DHedgecock in #503

Full Changelog: v6.2.0...v6.3.0

v6.2.0

02 Feb 13:36
v6.2.0
3e86118
Compare
Choose a tag to compare

What's Changed

Full Changelog: v6.1.0...v6.2.0

v6.1.0

13 Oct 12:15
v6.1.0
7853b66
Compare
Choose a tag to compare

What's Changed

Full Changelog: v6.0.0...v6.1.0

v6.0.0 🚀 - Babel Precompiling

12 Sep 02:37
v6.0.0
fa2b87a
Compare
Choose a tag to compare

v6 of Componentry provides a feature that has been in the works for a long time: Precompiling components with Babel 🏎 🎉

The display components Block, Flex, Grid, Paper, and Text now have full support for precompilation with Babel at build time. By compiling these components to static DOM elements with classNames applications can use flexible design system components with helpful guardrails with zero runtime overhead

Breaking changes

The configuration shape for ComponentryProvider and componentry.config.js is updated to support precompilation configurations. The exported Config shape should be used for both (note all fields are optional)

A common setup might look like:

componentry.config.js

const { theme } = require('./src/theme/theme')
const { textStyles } = require('./src/components/Text/Text/styles')

module.exports = {
  theme,
  styles: {
    Text: textStyles
  }
}

app.js

import { ComponentryProvider } from 'componentry'
import { theme } from './theme/theme'
import { textProps } from './components/Text/Text'

const componentryConfig = {
  theme,
  defaultProps: {
    Text: textProps
  }
}

root.render(
  <ComponentryProvider config={componentryConfig>
    <App />
  </ComponentryProvider>
)

What's Changed

Full Changelog: v5.0.1...v6.0.0

v6.0.0-beta.0 🧪

12 Sep 01:35
v6.0.0-beta.0
bc820ee
Compare
Choose a tag to compare
v6.0.0-beta.0 🧪 Pre-release
Pre-release

What's Changed

Full Changelog: v5.0.1...v6.0.0-beta.0