linkedin / linkedin/opticss

An in-range update of @types/prettier is breaking the build 🚨

Open
#63 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

greenkeeper
Dominant language
TypeScript
Stars
713
Forks
23
PR merge metrics
No merged PRs in 30d

Description

## The dependency [@types/prettier](https://github.com/DefinitelyTyped/DefinitelyTyped) was updated from `1.16.4` to `1.18.0`.

🚨 [View failing branch](https://github.com/linkedin/opticss/compare/master...linkedin:greenkeeper%2Fdefault%2F%40types%2Fprettier-1.18.0).

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

@types/prettier 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/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/linkedin/opticss/builds/561117470?utm_source=github_status&utm_medium=notification)).

---

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](https://greenkeeper.io) Bot :palm_tree:

Contributor guide

Open the contributing guide

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 with the Greenkeeper failing branch and the linked Travis CI build to identify the exact failure after @types/prettier changed from 1.16.4 to 1.18.0. Inspect the project's dependency declaration and CI output; the work is done when the dependency update no longer breaks the build.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
build-system, ci-cd, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.