search

Kronos-Integration / kronos-koa

Extends koa that routes could be added/removed dynamically
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

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

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

The devDependency rollup was updated from 1.25.2 to 1.26.0.

🚨 View failing branch.

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/Kronos-Integration/kronos-koa/builds/603609538?utm_source=github_status&utm_medium=notification)).
Release Notes for v1.26.0

2019-10-27

Features

  • Only warn when no output is provided for an IIFE bundle but still produce valid code (#3181)
  • Support reexporting namespaces as a binding (#3193)
  • Switch from hash.js to crypto for hashing in the Node build for better performance and support for very large assets (#3194)

Bug Fixes

  • Correctly handle chunks reexporting the same namespace as two different bindings (#3193)

Pull Requests

Commits

The new version differs by 5 commits.

  • 53fb6fe 1.26.0
  • 1fad958 Update changelog
  • 1e1a111 Add support for "export * as name from …" (#3193)
  • 2f7e064 Remove the need to provide an output name for IIFE bundles (#3181)
  • b4c8b43 [feat] Adds support for large assets (> 100 MB) (#3194)

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 Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

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