makeomatic / makeomatic/ms-mailer

An in-range update of eslint-plugin-import is breaking the build 🚨

Open
#17 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

greenkeeper
Dominant language
JavaScript
Stars
6
Forks
8
PR merge metrics
No merged PRs in 30d

Description

## Version **2.4.0** of [eslint-plugin-import](https://github.com/benmosher/eslint-plugin-import) just got published.



Branch


Build failing 🚨




Dependency


eslint-plugin-import




Current Version


2.3.0




Type


devDependency

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

As eslint-plugin-import 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 :muscle:

Status Details

- ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/makeomatic/ms-mailer/branches/greenkeeper-eslint-plugin-import-2-4-0/builds/1)

---

Commits

The new version differs by 10 commits.



  • 44ca158 update utils changelog

  • a3728d7 bump eslint-module-utils to v2.1.0

  • 3e29169 bump v2.4.0

  • ea9c92c Merge pull request #737 from kevin940726/master

  • 8f9b403 fix typos, enforce type of array of strings in allow option

  • 95315e0 update CHANGELOG.md

  • 28e1623 eslint-module-utils: filePath in parserOptions (#840)

  • 2f690b4 update CI to build on Node 6+7 (#846)

  • 7d41745 write doc, add two more tests

  • dedfb11 add allow glob for rule no-unassigned-import, fix #671


See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

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 inspecting the greenkeeper/eslint-plugin-import-2-4-0 branch and the Semaphore CI failure details to identify why eslint-plugin-import 2.4.0 breaks the build. Confirm the project builds successfully with the dependency update before considering the issue done.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, javascript
Domain
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.