gatsby-design-tokens - npm Package Compare versions

Comparing version 4.11.0-next.0 to 4.11.0-next.1

CHANGELOG.md

		@@ -6,2 +6,8 @@ # Changelog: `gatsby-design-tokens`

		## [4.10.0](https://github.com/gatsbyjs/gatsby/commits/gatsby-design-tokens@4.10.0/packages/gatsby-design-tokens) (2022-03-16)

		[🧾 Release notes](https://www.gatsbyjs.com/docs/reference/release-notes/v4.10)

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

		## [4.9.0](https://github.com/gatsbyjs/gatsby/commits/gatsby-design-tokens@4.9.0/packages/gatsby-design-tokens) (2022-03-01)
		@@ -8,0 +14,0 @@

package.json

		{
		"name": "gatsby-design-tokens",
		"version": "4.11.0-next.0",
		"version": "4.11.0-next.1",
		"description": "Gatsby Design Tokens",
		@@ -41,3 +41,3 @@ "main": "dist/index.js",
		},
		"gitHead": "e0f8815c007b7915f4d69264b8a5714a4c0ed31b"
		"gitHead": "a9fd6bef3b2b9150de31e1632bfd383ec331743a"
		}

README.md

		@@ -103,4 +103,2 @@ <img src="https://user-images.githubusercontent.com/21834/74070062-35b91980-4a00-11ea-93a8-b77bde7b4c37.png" width="48" height="48" alt="rebeccapurple dot" />

		Find a work-in-progress list of design tokens in the design tokens documentation at [gatsbyjs.org/guidelines/design-tokens](https://www.gatsbyjs.org/guidelines/design-tokens/).

		## `theme-ui` themes 🎨
		@@ -140,3 +138,3 @@

		The theme currently in use on gatsbyjs.org via `gatsby-plugin-theme-ui`:
		The theme currently in use on gatsbyjs.com via `gatsby-plugin-theme-ui`:

		@@ -176,7 +174,7 @@ - Extends the base theme's `colors` with a couple .org-specific things, and provides a `dark` mode (ref. https://theme-ui.com/color-modes).

		The Gatsby monorepo, which hosts this package, also contains the source for gatsbyjs.org, aka `www` — where `theme-gatsbyjs-org` is in use. Using a little helper called `gatsby-dev` we can develop and test both of them locally.
		The Gatsby monorepo, which hosts this package, also contains the source for gatsbyjs.com, aka `www` — where `theme-gatsbyjs-org` is in use. Using a little helper called `gatsby-dev` we can develop and test both of them locally.

		### 1. Clone the `gatsby` monorepo and set it up for local dev

		Follow the [official guide](https://www.gatsbyjs.org/contributing/setting-up-your-local-dev-environment/#fork-clone-and-branch-the-repository) to clone/fork and set up the Gatsby monorepo. This will roughly look like this:
		Follow the [official guide](https://www.gatsbyjs.com/contributing/setting-up-your-local-dev-environment/#fork-clone-and-branch-the-repository) to clone/fork and set up the Gatsby monorepo. This will roughly look like this:

		@@ -200,3 +198,3 @@ ```shell

		Assuming `gatsby-cli` [is installed](https://www.gatsbyjs.org/contributing/setting-up-your-local-dev-environment/#gatsby-functional-changes), let's install [`gatsby-dev-cli`](<(https://www.npmjs.com/package/gatsby-dev-cli)>) with
		Assuming `gatsby-cli` [is installed](https://www.gatsbyjs.com/contributing/setting-up-your-local-dev-environment/#gatsby-functional-changes), let's install [`gatsby-dev-cli`](<(https://www.npmjs.com/package/gatsby-dev-cli)>) with

		@@ -225,3 +223,3 @@ ```shell

		Run `yarn develop`, which thanks to the previous step shouldn't take ~40 minutes but way less. Hopefully you should be able to browse a local version of gatsbyjs.org after this. Let's leave `yarn develop` running!
		Run `yarn develop`, which thanks to the previous step shouldn't take ~40 minutes but way less. Hopefully you should be able to browse a local version of gatsbyjs.com after this. Let's leave `yarn develop` running!

		@@ -228,0 +226,0 @@ ### 3. Rebuild `gatsby-design-tokens` when it changes, and use `gatsby-dev` to copy the changed-and-compiled package over to `www/node_modules`

gatsby-design-tokens - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Worsened metrics