-
Notifications
You must be signed in to change notification settings - Fork 63
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Release Notes - Gatsby 4 now available * Release Notes: WebOps updated to use Lighthouse 9 * Update docs/static/data/releases.json
- Loading branch information
1 parent
79e3ee6
commit 0587eef
Showing
4 changed files
with
60 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
description: Render pages at run-time with Gatsby 4. | ||
tags: [faststore] | ||
hide_table_of_contents: false | ||
--- | ||
|
||
# Gatsby 4 now available | ||
|
||
We updated our infrastructure to allow you to use site generators that support **server-side rendering** (SSR), such as [Next.JS](https://nextjs.org/) and [Gatsby 4](https://www.gatsbyjs.com/gatsby-4/). | ||
|
||
## What has changed? | ||
|
||
Before, there were only two ways to render a FastStore website: either via client-side rendering (CSR) or static site generation (SSG). Now, you can also use server-side rendering. | ||
|
||
:::info | ||
Server-side rendering (SSR) is a method of rendering pages at run-time. It loads the website code on a server and returns a fully rendered HTML page to the client (browser). | ||
::: | ||
|
||
## Why did we make these changes? | ||
|
||
We made these changes precisely to support Gatsby 4 and NextJS. With these frameworks, you will be able to choose the best way to generate the pages of your store website, opening up new possibilities for what you can create with FastStore. | ||
|
||
## What needs to be done? | ||
|
||
These changes make Gatsby 4 available for usage, but they do not automatically change the Gatsby version of your project. For further instructions on how to migrate from Gatsby 3 to Gatsby 4, please refer to [this article.](https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
--- | ||
description: Maintain your store's performance by using WebOps with Lighthouse 9. | ||
tags: [webops] | ||
hide_table_of_contents: false | ||
--- | ||
|
||
# WebOps upgraded to use Lighthouse 9 | ||
|
||
The WebOps pipeline has been updated to use the newest **Lighthouse** version. In November 2021, Google published Lighthouse version 9.0. Among its main changes, highlights include the upgrade of Lighthouse APIs, the introduction of new user flows, the redesign of Lighthouse reports, and the addition of new accessibility features. | ||
|
||
## What has changed? | ||
|
||
Before, the WebOps pipeline was using Lighthouse version 8. Now, we are using Lighthouse 9. As a result, newer audit reports may slightly differ from those previously issued. For more information, please refer to [this announcement](https://developer.chrome.com/blog/lighthouse-9-0/). | ||
|
||
## Why did we make these changes? | ||
|
||
We understood that getting different results from WebOps and Lighthouse could lead to misunderstandings, so we made this modification to match both results. | ||
|
||
## What needs to be done? | ||
|
||
These changes are already available for everyone. Thus no further action is required to use WebOps with Lighthouse 9. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,26 +1,26 @@ | ||
[ | ||
{ | ||
"title": "Base Store", | ||
"title": "WebOps updated to use Lighthouse 9", | ||
"product": "WebOps", | ||
"fileName": "2022-04-05-webops", | ||
"description": "The WebOps pipeline has been updated to use the newest Lighthouse version. As a result, newer audit reports may slightly differ from those previously issued." | ||
}, | ||
{ | ||
"title": "Gatsby 4 now available", | ||
"product": "FastStore", | ||
"fileName": "2022-04-05-faststore", | ||
"description": "Render pages at run-time with Gatsby 4. We updated our infrastructure to allow you to use site generators that support server-side rendering (SSR), such as Next.JS and Gatsby 4." | ||
}, | ||
{ | ||
"title": "Base Store - Release Notes", | ||
"product": "Base Store", | ||
"fileName": "2022-04-01-basestore", | ||
"description": "The Base Store now has new components: EmptyState, Suggestions and SearchHistory." | ||
}, | ||
{ | ||
"title": "FastStore", | ||
"title": "FastStore - Release Notes", | ||
"product": "FastStore", | ||
"fileName": "2022-04-01-faststore", | ||
"description": "The FastStore API now includes an Express GraphQL Server, and the FastStore UI now has a new Dropdown component. Also, the performance of the useStorage hook has been improved." | ||
}, | ||
{ | ||
"title": "FastStore", | ||
"product": "FastStore", | ||
"fileName": "2022-03-04-faststore", | ||
"description": "Adjustments in the SearchInput reference and useStorage hook. Fixes in StoreProduct values and trailing slash from incoming requests. Also, new Performance Budgets section to the lighthouse report." | ||
}, | ||
{ | ||
"title": "Improved WebOps build time", | ||
"product": "WebOps", | ||
"fileName": "2022-02-08-webops", | ||
"description": "With the increased number of concurrent users of the WebOps platform, we noticed WebOps pipelines were taking longer to execute. Actions have already been taken." | ||
} | ||
] |