Version 4.6.0

What's Changed

• Fix broken "elements page" link
• Modernize by migrating from Webpack to tsup (esbuild)
• Migrate from Arkit to Dependency Cruiser
• Remove several dependencies
• Linting, even across tests
• Update contributors
• Fix Code Climate in CI

Full Changelog: v4.5.14...v4.6.0

Summary of changes

The majority of these changes are internal and should not affected users. The reason for making this a minor release, rather than a patch release, is because of the possibility of breaking changes when moving from bundling with Webpack to tsup (esbuild).

Now, Figmagic is bundled to both CommonJS as well as a module. The bin link is pointing to the module export.

Version 4.5.14

What's Changed

• Prefix CSS variables with frame name by @timhettler in #203
• SCSS variables output by @timhettler in #204
• Update failing test and MSW issues https://mswjs.io/docs/migrations/1.x-to-2.x/
• Update CI workflows and dependencies

Full Changelog: v4.5.13...v4.5.14

Summary of changes

Adds fixes for overlapping CSS variable names and new SCSS support. Also adds "under-the-hood" updates to keep things current and working.

New Contributors

• @timhettler made their first contribution in #203
• @timhettler also contributed to #204

Version 4.5.13

What's Changed

• Adds RRGGBBAA support for hex color tokens, solving #198

Full Changelog: v4.5.12...v4.5.13

Summary of changes

Updates the classic 6-digit value (excluding alpha) to the newer 8-digital version. The previous way of handling hex colors, was to "bake in" the transparency. Now, the feature parity between RGBA and hex color tokens should be 1:1.

Version 4.5.12

What's Changed

• Added a check function for data passed through sliceOutObjectFromFile() so that invalid JSON (for example, CSS tokens) would not break.
• Bump dependencies.

Full Changelog: v4.5.11...v4.5.12

Summary of changes

This will ensure CSS tokens don't break Figmagic if also using elements. This does not however guarantee that elements are correctly pointing to the right token values.

Version 4.5.11

What's Changed

• Make the code that fetches graphics also pick up instances and not just main components
• Update dependencies

Full Changelog: v4.5.10...v4.5.11

Summary of changes

This change is intended to make it possible to split graphics "main nodes" from the file that Figmagic actually processes.

Version 4.5.10

What's Changed

• Added custom styling to TypeDoc-generated site, docs.figmagic.com
• Restructured README.md
• Added NPM provenance support

Full Changelog: v4.5.9...v4.5.10

Summary of changes

These changes will not impact Figmagic itself, but had to be made because of the provenance needing to get pushed via the CI pipeline.

Version 4.5.9

What's Changed

• Add support for outputting tokens as CSS variables - fixes #190
• Hopefully improve gradient angle calculation
• Cleanup of files, removing old cruft
• Update badge ref from old master branch to newish main branch
• Update (developer) dependencies multiple times since last release
• Update CI configs to use Node 20 and newer Actions

Full Changelog: v4.5.8...v4.5.9

Summary of changes

The most important change in this release is the possibility to output tokens as CSS variables. The other changes are mostly relevant to the development of Figmagic.

Version 4.5.8

What's Changed

• feat: add support to Color Themes #176
• ci(): update CI to build before running
• chore(): bump version and update dependencies
• ci(): remove build folder from checked-in files, build in CI; update README with correct version number

Full Changelog: v4.5.7...v4.5.8

Summary of changes

The primary change is first-class support for color themes. This will not work perfectly (i.e. mapping to tokens) for generated components.

This release also includes improvements for the CI and does no longer include the built files in the checked-in code.

Version 4.5.7

What's Changed

• fix(): update React TSX template so it works; fixing issue #178

Full Changelog: v4.5.6...v4.5.7

Summary of changes

The React template used for .tsx file generation was not working as expected. Added any types and using props instead of spreading to children. Verified it working in Codesandbox.

Version 4.5.6

What's Changed

• feat: add useLiteralFontFamilies option by @opauloh in #174

Full Changelog: v4.5.5...v4.5.6

Summary of changes

Adds a new useLiteralFontFamilies option. This is useful for defining the whole font family stack with the fallbacks instead of a single font name, i.e.: Roboto, BlinkMacSystemFont, Helvetica, Arial, sans-serif.