<commit_before>---
layout: default
title: Just in time for Christmas!
description: We got some big news - sitespeed.io 6.0, Browsertime 2.0, The Coach 1.0 and PageXray 2.0 is here!
authorimage: /img/aboutus/jonathan.jpg
intro: We got some big news - sitespeed.io 6.0, Browsertime 2.0, The Coach 1.0 and PageXray 2.0 is here. We moved to NodeJS 8, made a lot of small improvements and focused a lot on making plugins more powerful.
keywords: sitespeed.io, sitespeed, 6.0
nav: blog
---

# 6.0 and more

The last weeks we've been releasing sitespeed.io 6.0, Browsertime 2.0, PageXray 2.0 and the Coach 1.0. And lets talk about the changes we have done. But before we start: Every tool now have latest LTS of NodeJS as requirement (moving from 6 to 8). That means if you don't use our Docker containers, you need to upgrade NodeJS. The move to latest NodeJS will make it easer for us to clean the code and start using await/async.

One of the biggest things we done for all these releases is updating the documentation. It was ok before but missing out on so many things. You really should check out [the new version](https://www.sitespeed.io/documentation/) of the documentation.

## Sitespeed.io 6.0
The main focus for 6.0 has been to update the plugin structure so it's easier to write more powerful plugins. With the new version, plugins communicate with each other using the queue. There's a new queue phase called *sitespeedio.setup* where plugins can talk with the others. For example a plugin can register a PUG file to the HTML plugin, so that the metrics the plugin produces can be [showed in the HTML](https://www.sitespeed.io/documentation/sitespeed.io/plugins/#create-html-for-your-plugin). Another cool thing is that the Browsertime plugin [listens to JavaScript setup messages](https://www.sitespeed.io/documentation/sitespeed.io/plugins/#let-your-plugin-collect-metrics-using-browsertime), so other plugins can run JavaScript on the tested page (through Browsertime), and use the data.

We also moved out the [GPSI plugin](https://github.com/sitespeedio/plugin-gpsi) to be a standalone (example) plugin. That means if you want to use GPSI, you need to follow the [instructions](https://www.sitespeed.io/documentation/sitespeed.io/plugins/#add-a-plugin) in how to add a plugin.

We think these changes will make the plugins more powerful. We have new repo where we will keep track of 3rd party plugins [https://github.com/sitespeedio/plugins](https://github.com/sitespeedio/plugins). Go there and checkout [<NAME>](https://github.com/siteriaitaliana) work in progress to implement a Lighthouse plugin.



When you upgrade, please read or [upgrade notes](https://www.sitespeed.io/documentation/sitespeed.io/upgrade/) and check the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md).<commit_msg>description again<commit_after>---
layout: default
title: Just in time for Christmas!
description: We got some big news - sitespeed.io 6.0, Browsertime 2.0, The Coach 1.0 and PageXray 2.0 is here!
authorimage: /img/aboutus/jonathan.jpg
intro: We got some big news - sitespeed.io 6.0, Browsertime 2.0, The Coach 1.0 and PageXray 2.0 is here. We moved to NodeJS 8, made a lot of small improvements and focused on making plugins more powerful.
keywords: sitespeed.io, sitespeed, 6.0
nav: blog
---

# 6.0 and more

The last weeks we've been releasing sitespeed.io 6.0, Browsertime 2.0, PageXray 2.0 and the Coach 1.0. And lets talk about the changes we have done. But before we start: Every tool now have latest LTS of NodeJS as requirement (moving from 6 to 8). That means if you don't use our Docker containers, you need to upgrade NodeJS. The move to latest NodeJS will make it easer for us to clean the code and start using await/async.

One of the biggest things we done for all these releases is updating the documentation. It was ok before but missing out on so many things. You really should check out [the new version](https://www.sitespeed.io/documentation/) of the documentation.

## Sitespeed.io 6.0
The main focus for 6.0 has been to update the plugin structure so it's easier to write more powerful plugins. With the new version, plugins communicate with each other using the queue. There's a new queue phase called *sitespeedio.setup* where plugins can talk with the others. For example a plugin can register a PUG file to the HTML plugin, so that the metrics the plugin produces can be [showed in the HTML](https://www.sitespeed.io/documentation/sitespeed.io/plugins/#create-html-for-your-plugin). Another cool thing is that the Browsertime plugin [listens to JavaScript setup messages](https://www.sitespeed.io/documentation/sitespeed.io/plugins/#let-your-plugin-collect-metrics-using-browsertime), so other plugins can run JavaScript on the tested page (through Browsertime), and use the data.

We also moved out the [GPSI plugin](https://github.com/sitespeedio/plugin-gpsi) to be a standalone (example) plugin. That means if you want to use GPSI, you need to follow the [instructions](https://www.sitespeed.io/documentation/sitespeed.io/plugins/#add-a-plugin) in how to add a plugin.

We think these changes will make the plugins more powerful. We have new repo where we will keep track of 3rd party plugins [https://github.com/sitespeedio/plugins](https://github.com/sitespeedio/plugins). Go there and checkout [<NAME>](https://github.com/siteriaitaliana) work in progress to implement a Lighthouse plugin.



When you upgrade, please read or [upgrade notes](https://www.sitespeed.io/documentation/sitespeed.io/upgrade/) and check the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md).
{'fraction_non_alphanumeric': 0.08277562522014793, 'fraction_numerical': 0.012680521310320535, 'mean_word_length': 4.3676748582230625, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 20, 'lorem ipsum': 0, 'www.': 10, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2754685', 'n_tokens_mistral': 1652, 'n_tokens_neox': 1595, 'n_words': 750}