eslint: regression in 2.13.0 release - relative extend fails to find referenced file

After the release of 2.13.0, projects consuming my personal eslint-config can no longer successfully load the chain of extends. It would appear that this issue is related to #6450, but the fix for that specific issue (released in 2.13.1) does not appear to resolve this issue.

What version of ESLint are you using? 2.13.1

What parser (default, Babel-ESLint, etc.) are you using? grunt-eslint

Please show your full configuration:

What did you do? Please include the actual source code causing the issue. No eslint related changes were made directly to my projects. I do not track a direct dependency on eslint in the projects that use grunt-eslint, and grunt-eslint depends on ^2.0.0. Since I do not have travis-ci configured to cache dependencies between builds, when it built contributions after 2.13.0 was released it was immediately pulled into the next build and caused it to fail.

What did you expect to happen? I expected that the ^2.0.0 range would be safe from breaking changes and not require my projects to depend on a specific eslint version since I do not depend directly on eslint, but rather depend on it only through grunt-eslint.

What actually happened? Please include the actual, raw output from ESLint. https://travis-ci.org/travi/admin.travi.org-components/jobs/138631754

Running "eslint:target" (eslint) task
Warning: Cannot read config file: /home/travis/build/travi/admin.travi.org-components/node_modules/@travi/eslint-config-travi/rules/react
Error: ENOENT: no such file or directory, open '/home/travis/build/travi/admin.travi.org-components/node_modules/@travi/eslint-config-travi/rules/react'
Referenced from: @travi/travi/rules/tests/react
Referenced from: /home/travis/build/travi/admin.travi.org-components/test/unit/.eslintrc.yml Use --force to continue.
Aborted due to warnings.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 18 (10 by maintainers)

Commits related to this issue

Most upvoted comments

Sorry, lost track of this. Yeah, I think we’re at the point where we’re not going to make a change here. I think asking people to include extensions is reasonable given how we have to support a few different config file formats. Leaving open a couple more days to see if anyone else on the team feels strongly otherwise.