Local Config File Resolution throw error in file protocol

https://cn.eslint.org/docs/developer-guide/shareable-configs#local-config-file-resolution

I create my config @scope/eslint-config-myconfig in local, and install it by npm install file:../eslint-config-myconfig

eslint-config-myconfig

// index.js
module.exports = {
  parser: 'babel-eslint',
  extends: ['./base.js'],
};

// base.js
module.exports = {
  extends: ['other-config'],
  rules: {
  },
};

// vue.js
module.exports = {
  extends: ['@scope/eslint-config-myconfig', 'plugin:vue/essential'],
  rules: {
  },
};

project-1

module.exports = {
  extends: '@scope/eslint-config-myconfig/vue'
};

when i run eslint src, it throw error

Oops! Something went wrong! :(

ESLint: 7.1.0

ESLint couldn't find the config "@scope/eslint-config-myconfig" to extend from. Please check that the name of the config is correct.

The config "@scope/eslint-config-myconfig" was referenced from the config file in "/Users/my/scope/eslint-config-myconfig/vue.js".

If you still have problems, please stop by https://eslint.org/chat to chat with the team.

but it succeed after published to npm

Tell us about your environment

• ESLint Version: 7.1.0
• Node Version: 10.16.3
• npm Version: 6.11.3

Resolved

I used extends: ['./base'] to resolved it, but i diff to document

[mysticatea]

throw error Error: Cannot find module ‘@scope/eslint-config-myconfig’, maybe it load from eslint-config-myconfig/node_modules

OK, so this is the designed behavior. You have to write eslint-config-myconfig as working fine with this behavior.

I’m not familiar with lerna, so I mention another solution: I guess you can use extends:"./index.js" or something like instead of extends:"@scope/eslint-config-myconfig", because require("./index.js") in the vue.js should work fine.

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that accepted issues failing to be implemented after 90 days tend to never be implemented, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.