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.