An in-range update of rollup is breaking the build 🚨

***
☝️ **Important announcement:** Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! [Find out how to migrate to Snyk and more at greenkeeper.io](https://greenkeeper.io)
***
## The devDependency [rollup](https://github.com/rollup/rollup) was updated from `2.2.0` to `2.3.0`.

🚨 [View failing branch](https://github.com/atlassian/browser-interaction-time/compare/master...atlassian:greenkeeper%2Frollup-2.3.0).

This version is **covered** by your **current version range** and after updating it in your project **the build failed**.

rollup is a devDependency of this project. It **might not break your production code or affect downstream projects**, but probably breaks your build or test tools, which may **prevent deploying or publishing**.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/github/atlassian/browser-interaction-time/builds/668482691?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v2.3.0

2020-03-29

Features

• Do not transpile config files with .mjs extension in Node 13+ or .cjs extension in any Node version and load them appropriately (#3445)


• Extract helper to load a config file the way rollup does it via rollup/dist/loadConfigFile (#3445)

Bug Fixes

• Keep watching the config file if an error occurs during initial load in watch node (#3445)


• Add a helpful error message when using a transpiled config in a repository with "type": "module" (#3445)

Pull Requests

• #3445: Support native ESM configs in Node 13, support untranspiled configs (@lukastaegert)


• #3468: Don't use esm output format alias in the documentation (@vsn4ik)

Commits

The new version differs by 4 commits.

• 9fa326f 2.3.0


• d6376f4 Update changelog


• 7eea04a Support native ESM configs in Node 13, support untranspiled configs (#3445)


• 618e7f6 Don't Use esm Output Format (Alias) (#3468)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Start by inspecting the Greenkeeper failing branch and the linked Travis CI build for the failure introduced by rollup 2.3.0. Compare the project's build configuration and dependency state with the rollup 2.2.0 version, then confirm the build passes after the issue is resolved.

Written by the indexing model from the issue text.