Skip to content

An in-range update of loader.js is breaking the build 🚨 #10

@greenkeeper

Description

@greenkeeper

Version 4.2.0 of loader.js just got published.

Branch Build failing 🚨
Dependency loader.js
Current Version 4.1.0
Type devDependency

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

As loader.js is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • ci/circleci Your tests failed on CircleCI Details
Commits

The new version differs by 14 commits .

  • cc53069 release v4.2.0
  • 1a453d3 Merge pull request #104 from trentmwillis/redefine
  • 93478ef Improve redefinition scenarios
  • e289916 Fix test:dev command
  • 287a487 Merge pull request #105 from trentmwillis/clarify
  • cda1c29 Clarify prime comment
  • 562ecf1 Merge pull request #100 from jrowlingson/master
  • 6a9b916 remove petal references
  • b609262 Merge pull request #95 from chadhietala/heimdall-instrumentation
  • c49296d Instrument with heimdall
  • 453fe8c Merge pull request #97 from Turbo87/ci-deploy
  • 37fef79 CI: Enable automatic NPM deployment for tags
  • c4f0755 Merge pull request #96 from chadhietala/dict-registry
  • 8a34296 Use dict for registery and seen to avoid filling IC cache

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions