gatsby-design-tokens - npm Package Compare versions

Comparing version 2.0.3 to 2.0.4

CHANGELOG.md

		@@ -6,2 +6,6 @@ # Change Log

		## [2.0.4](https://github.com/gatsbyjs/gatsby/compare/gatsby-design-tokens@2.0.3...gatsby-design-tokens@2.0.4) (2020-03-23)

		Note: Version bump only for package gatsby-design-tokens

		## [2.0.3](https://github.com/gatsbyjs/gatsby/compare/gatsby-design-tokens@2.0.2...gatsby-design-tokens@2.0.3) (2020-03-16)
		@@ -38,3 +42,4 @@

		This update moves the rudimentary tokens even closer to our current sole target, CSS. This e.g. means that instead of exporting an array of integers for `fontSizes` or `space`, we now provide `rem` values instead (while still making the v1 variants available — but we do have "soft" preferences regarding default units for CSS, which are emphasized by these breaking changes).
		This update moves the rudimentary tokens even closer to our current sole target, CSS. This e.g. means that instead of exporting an array of integers for `fontSizes` or `space`, we now provide `rem` values instead (while still making the v1 variants available — but we do have "soft" preferences regarding default units for CSS, which are emphasized by these breaking changes).

		We currently only consume these tokens in the context of CSS, so let's make things a bit easier there:
		@@ -41,0 +46,0 @@

package.json

		{
		"name": "gatsby-design-tokens",
		"version": "2.0.3",
		"version": "2.0.4",
		"description": "Gatsby Design Tokens",
		@@ -37,3 +37,6 @@ "main": "dist/index.js",
		},
		"gitHead": "07dc2c19f18cd8e67e5c59061832cea09d43ade8"
		"engines": {
		"node": ">=10.13.0"
		},
		"gitHead": "10722585e3544fd7672c6a262198461a6968b0eb"
		}

New alerts