leecade / leecade/fe

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

Open
#111 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

greenkeeper
Dominant language
JavaScript
Stars
15
Forks
4
PR merge metrics
No merged PRs in 30d

Description

The dependency colors was updated from 1.3.3 to 1.4.0.

🚨 View failing branch.

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

colors 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 8 commits.

  • baa0e1c update roadmap
  • 56de9f0 Add bright/light colors, closes #128
  • b4d964b Make stylize() work for non-ASCI styles (#155)
  • a1407ae Document colors.enable() and .disable() (#255)
  • acb7f66 Merge branch 'develop' of github.com:Marak/colors.js into develop
  • 9bfb136 more node versions
  • 5d9eb90 Fixed: throws non-intuitive error on color.red(null) but not on colors.red(undefined) (#261)
  • aa012aa Redo weak equality check so we can colorize null in safe mode (#257)

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 🌴

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the failing Greenkeeper branch and the linked AppVeyor and Travis CI build details to identify which change in colors 1.4.0 breaks the project. Compare the project’s current dependency configuration with the 1.3.3-to-1.4.0 update, then confirm the chosen resolution with the project’s CI builds passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.