gatsby-plugin-layout - npm Package Compare versions

Comparing version 1.0.8 to 1.0.9

CHANGELOG.md

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

		<a name="1.0.9"></a>

		## [1.0.9](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-layout@1.0.8...gatsby-plugin-layout@1.0.9) (2018-11-14)

		### Bug Fixes

		- docs: update broken links with working links ([#9912](https://github.com/gatsbyjs/gatsby/issues/9912)) ([e9f2a6f](https://github.com/gatsbyjs/gatsby/commit/e9f2a6f))

		<a name="1.0.8"></a>
		@@ -8,0 +16,0 @@

package.json

		{
		"name": "gatsby-plugin-layout",
		"version": "1.0.8",
		"version": "1.0.9",
		"description": "Reimplements the behavior of layout components in gatsby@1, which was removed in version 2.",
		@@ -34,3 +34,3 @@ "main": "index.js",
		},
		"gitHead": "f9714a5646523bc728586e3692190507ad68e6c1"
		"gitHead": "41ed9421797bc111fd3627bccd604cab29dcd5ff"
		}

README.md

		@@ -53,3 +53,3 @@ # gatsby-plugin-layout

		1. You have a large or complex V1 site and [refactoring to the new layout component](https://v2--gatsbyjs.netlify.com/docs/migrating-from-v1-to-v2/#update-layout-component) is not feasible
		1. You have a large or complex V1 site and [refactoring to the new layout component](https://www.gatsbyjs.org/docs/migrating-from-v1-to-v2/#remove-or-refactor-layout-components) is not feasible
		2. Your site uses page transitions or other transitions that break if the layout component is unmounted and remounted when routes change
		@@ -56,0 +56,0 @@ 3. Your site attaches global state in the layout that doesn't persist if the component is unmounted and remounted

New alerts