Changelog

We published a new patch version of React Live Chat Loader (2.8.1). In this release, we realigned react-live-chat-loader placeholder styling with Intercom’s current default styling (#215) and bumped all outdated dependencies.

See the full changelog on GitHub.

Our Test Agents are now using Chrome 107 to test your Sites.

Our Test Agents are now using Lighthouse 9.6.8 to test your Sites.

We fixed a problem preventing organisation invitation emails from being delivered in the case where the Resend invitation button was pressed multiple times by the same person to send another invitation email.

Previously Calibre recommended that Time to First Byte (TTFB) should be below 150ms for a good user experience. The recommendation has now been updated to < 300ms based on global data from the Chrome User Experience Report (CrUX).

In Calibre, you will now see a warning if your TTFB is above 300ms and a critical error if it is above 800ms.

Our Test Agents are now using Chrome 106 to test your Sites.

We published a new, minor version of React Live Chat Loader (2.8.0). In this release we:

• Add containerClass prop to allow custom CSS classes on the chat container element
• Improve Typescript definitions
• Refresh the documentation and demo website
• Update placeholder styles to reflect the current default styling of all supported chat beacons

These changes will make using and contributing to React Live Chat Loader easier.

See full changelog on GitHub.

We improved the badge element contrast to pass Web Content Accessibility Guidelines (WCAG) AAA (enhanced contrast) accessibility audits. Previously, they only met the standard on AA (minimum contrast) requirement.

On top of that, we also slightly amended the appearance of badges to give a more soft, rounded feeling. You can see them in action on the Snapshots list, Snapshot page, and Budgets.

We’ll continue evaluating and improving contrast and other accessibility features across Calibre.

Our Test Agents are now using Lighthouse 9.6.7 to test your Sites.

React Live Chat Loader now supports React 18, thanks to contribution from Chris Schuld.

Our Test Agents are now using Chrome 105 to test your Sites.

We published a patch CLI release with a fix to Windows support.

See full changelog on GitHub.

Our Test Agents are now using Chrome 104 and Lighthouse 9.6.4 to test your Sites.

Our Test Agents are now using Lighthouse 9.6.3 to test your Sites.

We published a patch CLI release with the following changes:

• Updated calibre device-list command to output additional emulated device details (screen width and height, device type: phone tablet or desktop and status: current or discontinued)

See full changelog on GitHub.

We continue to improve our open source projects’ governance. React Live Chat Loader, Image Actions and the Calibre Command Line Interface, and Node.js API are now using GitHub Issue Forms. While Issue Forms are currently in beta, they offer a more pleasant and guided way to submitting bugs and questions. See them in action below:

Our Test Agents are now using Chrome 103 to test your Sites.

Our Test Agents are now using Lighthouse 9.6.2 to test your Sites.

Our Test Agents are now using Chrome 101 to test your Sites.

In synthetic and real user monitoring, it’s critical to understand the conditions in which people browse your sites so that we can correlate it to performance. It’s also not uncommon for metric definitions and collection methods to change or bugs to emerge.

To improve the transparency of test settings and debugging changes, we added the Chrome and Lighthouse versions for each test to the Snapshot and Single Page Test report pages:

In 5.0.1, we added a new command, calibre team list, that lists all Teams your API Access Token can access. We also rewrote all command descriptions for better clarity.

See full changelog on GitHub.

You can now see your real user data for Time to First Byte (TTFB) and Interaction to Next Paint (INP) using Core Web Vitals Test:

Time to First Byte is critical to track as it can have a cascading, adverse effect on page load and speed. Interaction to Next Paint is a new, experimental metric measuring the longest observed delay between user interaction and the response on your page. While these metrics are not included in the Core Web Vitals set now, we’d recommend adding them to your “to track” list.

Generate your free report here!

We believe transparent governance is critical to any open source project. We updated our most popular projects (React Live Chat Loader, Image Actions and the Calibre Command Line Interface and Node.js API) to reflect the same policies, such as Code of Conduct, security, contribution and issue logging guidelines.

We also updated project READMEs accordingly to make usage and collaboration even more accessible.

Our Test Agents are now using Chrome 100 to test your Sites.

When you add a new Site to monitor in Calibre, we send a summary email with crucial page speed metrics and how you rank against our measurements dataset. To provide a more comprehensive picture of web performance, alongside Web Vitals, we added Time to First Byte to the email report:

We published a new, major version of Calibre’s CLI (5.0.0), now written in ES Modules! With this release we:

• Add a new flag for calibre test create: --waitForTest
• Add new package exports: cli-commands and cli-metadata (to return command functions and documentation)
• Add CLI_COMMANDS.md that lists all available commands with their options for easy reference
• End support for Node 12

From the 5.0.0 version, we’re also ceasing to update the standalone binary builds for the CLI. They will remain accessible for now, but the recommended method of installing an up-to-date version of the CLI is npm.

See full changelog on GitHub.

Setting Cookies and Headers to either authenticate to your Sites or control the test environment has been in Calibre for some time (set via either the Test Agent or Test Profiles). Now, you can specify those settings while using Pull Request Reviews too:

1version: 2
2pullRequestReviews:
3  # Headers
4  - headers:
5      - name: X-Calibre-Test
6        value: Pull Request
7      - name: User-Agent
8        value: Calibre
9
10  # Cookies
11  - cookies:
12      - name: seen-cookie-notice
13        value: true
14      - name: uid
15        value: 1
16        domain: calibreapp.com
17        path: /
18        secure: true
19        httpOnly: true
20

This is especially useful if you’d like to set cookies and headers only for Pull Request Reviews tests (not inherited from Test Profiles settings). For example, you could set a header to signify that the test is for a Pull Request and should be safely routed to the staging infrastructure.

Our Test Agents are now using Lighthouse 9.5 and Chrome 99 to test your Sites.

Our Test Agents are now using Lighthouse 9.3.1 and Chrome 97 to test your Sites.

If you’re using cookies and headers (either in Test Profiles or Site Settings → Test Agent area), we now change when they are applied.

Previously, Calibre set cookies and headers post-authentication. Now, they are applied during authentication so that you can control more fine-grained authentication scenarios, such as hiding CAPTCHA, so Calibre can quickly test your Site or application.

We introduced two new currencies (EUR and AUD) and several new payment methods, so your team can choose a way of paying that’s most convenient and least costly. You can change your payment currency at any time:

Because limited payment methods can be a software adoption blocker and a source of accounting issues, we also added several new methods of purchasing a subscription—not all of which rely on credit cards. We now accept:

• Credit Card (all plans)
• Apple Pay (all plans, only in Safari browser)
• Google Pay (all plans, only in Google Chrome browser)
• Single Euro Payments Area (SEPA) Direct Debit (all plans in EUR currency)
• Bulk Electronic Clearing System (BECS) Direct Debit (all plans in AUD currency)

Thanks to SEPA and BECS, customers in Australia and SEPA countries with relevant plans (AUD or EUR) can pay for their subscription directly from a nominated bank account. You can change your payment method in Billing → Payment Method tab.

With the new payment methods and currencies, we switched to invoices generated by our payment provider—Stripe. Your designated Billing email will still receive invoices after each transaction, and each Administrator can access the entire invoice history in Invoice History and Settings.

We made it possible to display the request table (from the corresponding HAR file) even when your tests fail. We’re now surfacing more information about errors that lead to Lighthouse failures directly in the Snapshot view, so it’s easier to find out the exact reason:

If your tests are failing (continually or intermittently), you can also refer to the Why do my tests fail? guide that walks through common scenarios and steps to fix them.

With two minor releases of Calibre CLI, we added new commands and ways to query your data. Site.get and Site.update now allow obtaining and updating given Sites. We added missing fields to Test Profiles, Deploys, Location, Metric budgets, and Page queries so that you can receive and manipulate all test data.

See full changelog on Github.

We continually build on our best practices to protect your account and data. From now on, all new registrations and, periodically, existing users will have to verify their email accounts unless they are using Google as a method of authentication.