import-js/eslint-plugin-import

v2.23 no longer works with `Promise`-based Webpack configuration

Open

#2,069 创建于 2021年5月14日

在 GitHub 查看
 (15 评论) (0 反应) (0 负责人)JavaScript (4,946 star) (1,540 fork)batch import
enhancementhelp wantedpackage: resolver/webpack

描述

Prior to v2.23, my webpack.config which returns a Promise<WebpackConfig[]> worked fine, but now it causes the following errors (LOTS of them):

Webpack config returns a `Promise`; that signature is not supported at the moment. Using empty object instead.

贡献者指南

技术栈
javascriptnodejs
领域
toolingbuild system
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Webpack configurationPromise handling
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
The issue is that eslint plugin import v2.23 no longer supports Promise returning Webpack configurations. The change likely occurred in the commit that introduced array of configs support. Investigate the plugin's handling of Webpack config in the `resolve` or `parse` functions, particularly in the file `lib/core/importType.js` or similar. Look at the PRs/issues linked from v2.23 release notes. A fix would involve allowing the config to be a Promise and awaiting it before accessing properties.