An in-range update of replace-ext is breaking the build 🚨

[greenkeeper]

---

☝️ 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

---

The dependency replace-ext was updated from 1.0.0 to 1.0.1.

🚨 View failing branch.

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

replace-ext is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).
• ❌ Travis CI - Branch: The build errored.
• ❌ Build: Your Google Cloud Platform project is not set up correctly for this GitHub app. Please go through the setup flow again in the cloud console.

---

Commits

The new version differs by 5 commits.

• 2c67ddd Release: 1.0.1
• 8bee038 Fix: Preserve first dot of relative path (fixes #5)
• a55455a Scaffold: Normalize repository
• 9047016 Scaffold: Add Tidelift security & marketing
• 93a5b14 Build: Enforce consistent line endings

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 1.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.