Skip to content

Releases: happo/happo.io

v8.3.2

16 Apr 08:29
Compare
Choose a tag to compare

This patch release addresses an issue with external PRs happening in a GitHub actions environment.

v8.3.1

29 Dec 21:15
Compare
Choose a tag to compare
  • Upgrade node dependencies to their latest patch versions.
  • Upgrade jsonwebtoken to 9.0.0 to fix vulnerability GHSA-qwph-4952-7xr6

v8.3.0

15 Nov 09:28
Compare
Choose a tag to compare
  • Allow babel-loader@^9 in peerDependencies

v8.2.0

11 Oct 13:23
Compare
Choose a tag to compare

Increase timeout when making calls to the happo.io API. This mostly affects asset package uploads, where occasionally they would take longer than 30 seconds (which was the previous value).

v8.1.1

15 Sep 07:07
Compare
Choose a tag to compare

Remove warning when using the new afterSyncComparison config option.

v8.1.0

14 Sep 17:28
Compare
Choose a tag to compare

This minor release adds support for a new afterSyncComparison function that you can define in .happo.js. It gets called when a comparison has been made (but only when HAPPO_IS_ASYNC=false). It gets called with an object having this format: https://happo.io/docs/api#Comparison

Thanks to @wokayme for the contribution!

v8.0.0

07 Sep 07:26
Compare
Choose a tag to compare

This major release drops official support for Node v12. It will most likely still work but we will no longer provide fixes that are specific to Node v12.

  • Drops @babel/polyfill (see #239)
  • Upgrade package dependencies to latest patch releases

v7.3.0

02 Aug 10:48
Compare
Choose a tag to compare

This release adds support for using extends with the pages config.

v7.2.1

06 May 21:07
Compare
Choose a tag to compare

Fix misconfigured CHANGE_URL set in the happo-ci-azure-pipelines script.

v7.2.0

02 May 07:01
Compare
Choose a tag to compare

This version allows targets in .happo.js to be plain objects as opposed to instances of RemoteBrowserTarget. This will allow users to run happo using npx -p happo.io happo run without having happo.io installed locally.

Here's an example of what .happo.js can look like when it has no dependency on RemoteBrowserTarget:

module.exports = {
  apiKey: process.env.HAPPO_API_KEY,
  apiSecret: process.env.HAPPO_API_SECRET,
  pages: [{ url: 'https://beteendelabbet.se/', title: 'Beteendelabbet' }],
  targets: {
    'chrome-large': {
      browserType: 'chrome',
      viewport: '800x600',
    },
  },
};

This is equivalent to the regular way of using targets:

const { RemoteBrowserTarget } = require('happo.io');

module.exports = {
  apiKey: process.env.HAPPO_API_KEY,
  apiSecret: process.env.HAPPO_API_SECRET,
  pages: [{ url: 'https://beteendelabbet.se/', title: 'Beteendelabbet' }],
  targets: {
    'chrome-large': new RemoteBrowserTarget('chrome', {
      viewport: '800x600',
    }),
  },
};

If you are using npx to run happo in CI, you might have to set the HAPPO_COMMAND environment variable as well to get things to work.

HAPPO_COMMAND="happo" npx -p happo.io happo-ci-circleci