chore(deps-dev): bump rollup-plugin-babel from 3.0.7 to 4.4.0

[dependabot-preview]

Bumps rollup-plugin-babel from 3.0.7 to 4.4.0.

Changelog

Sourced from rollup-plugin-babel's changelog.

4.3.2

• Fixed usage with externalHelpers: true option

4.3.1

• Add .js extension to the virtual babel helpers file (only matters when using preserveModules option in rollup)

4.3.0

• Added .custom builder.
• Fail build when a plugin tries to add non existent babel helper

4.2.0

Allow rollup@1 as peer dependency.

4.1.0

• Fixed "preflight check" for ignored files.
• Return null when no transformation has been done (fixing source maps for this case)

4.0.3

Fixed fallback class transform in "preflight check".

4.0.2

Fixed rollup peer dependency.

4.0.0

Babel 7 compatible! (dropped Babel 6 compatibility though).

Additionally:

• Internal preflight checks are created now per plugin instance, so using 2 instances of rollup-plugin-babel (i.e. targeting 2 different set of files with include/exclude options) shouldn't conflict with each other
• Transpiling by default only what Babel transpiles - files with those extensions: .js, .jsx, .es6, .es, .mjs. You can customize this with new extensions option. This also fixes long standing issue with rollup-plugin-babel trying to transform JSON files.

3.0.3

• Drop babel7 support. Use 4.0.0-beta if you use babel 7
• Use "module" in addition to "jsnext:main" (#150)
• Remove unused babel helpers namespace declaration & expression (#164)

3.0.2

• Fix regression with Babel 6 (#158)

3.0.1

... (truncated)

Commits

• 05fb203 4.4.0
• c2821d0 Allow Rollup 2 in peer dependency range
• 4d8c0c5 4.3.3
• e386e1f Update [email protected] (#311)
• 54a166a chore: npm audit fix
• 18e4232 chore: audit fixes
• 8357816 Update CHANGELOG with note about 4.3.2
• 79941b5 4.3.2
• a7e7676 Fix usage with externalHelpers flag
• 66f2f41 Add note to CHANGELOG about v4.3.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

• ci/circleci

Dependabot will still automatically merge this pull request if you amend it and your tests pass.