In my .eslintrc, my settings are "settings": { "import/resolver": "webpack" } and webpack.config.js lives in the same folder as package.json. When upgrading from 0.2.1 to 0.2.2 of the webpack resolver, I am ge
"settings": { "import/resolver": "webpack" }, Or, install eslint-import-resolver-webpack and see if that works better. The former is fewer dependencies so I’d try that first, but up to you. Is a little strange you’d end up with the config pointing to it without it in your ...
'off':configconstrules={eslint:{'no-case-declarations':'off','import/no-unresolved':'off','import/namespace':'off','import/no-duplicates':'off','no-async-promise-executor':'off','block-spacing':'error','import/named':'off','quotes':['error','single'],'semi':['error','never']...
https://github.com/benmosher/eslint-plugin-import/blob/master/resolvers/webpack/index.js#L37 when run with eslint-loaderfileis only a relative path. when run with eslintfileis a fully qualified path in my case adding apath.resolve()aroundfileseems to solve the problem: packageDir = find...
benmosher mentioned this issue Feb 18, 2016 [webpack-resolver]: use enhanced-resolve? #182 Closed 3 tasks michaelfaith pushed a commit to michaelfaith/eslint-plugin-import that referenced this issue Sep 7, 2024 docs/fix: flat config (import-js#135) 2f21f7e Sign...
Needs to take a file path as config, but have some default fallback akin to Webpack's (i.e. webpack.config.js as sibling to nearest ancestor package.json). find webpack config (use some lib to find package.json and look in that dir) use ...