Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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:

config file from consuming project
initially included ruleset from my config (references another file from the config project relative to itself)
file that should be extended from the initial extension

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.

Issue Analytics

State:
Created 7 years ago
Comments:18 (10 by maintainers)

Top GitHub Comments

2reactions

nzakascommented, Jul 20, 2016

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.

0reactions

nzakascommented, Aug 3, 2016

No further comments, so closing.

Top Results From Across the Web

eslint couldn't find the config "react-app" to extend from

I am running across this issue when I run my React application: Failed to compile. eslint Failed to load config "react-app" to extend...

ExoPlayer/RELEASENOTES.md at release-v2 - GitHub

Name already in use A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so...

astroid's ChangeLog — Astroid 2.13.0-dev0 documentation

Fix a crash when a AttributeInferenceError was raised when failing to find the real name in infer_import_from. Closes PyCQA/pylint#4692. What's New in astroid ......

Log4j – Changes - Apache Logging Services

Release 2.19.0 – 2022-09-09. Type, Changes, By. Update, Add getExplicitLevel method to LoggerConfig. Fixes LOG4J2 ...

BLAST+ Release Notes - BLAST® Help - NCBI Bookshelf - NIH

Blastn_vdb and tblastn_vdb included in the 2.13.0 release. Makeblastdb now produces a (JSON) metadata file about the database. This makes BLAST ...