Galooshi/import-js

Find aliases and named exports in existing project

Open

#184 建立於 2016年1月31日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)JavaScript (519 star) (70 fork)batch import
enhancementhelp wanted

描述

When setting up Import-JS on an old project, it can take a while to get all of the aliases and named exports configuration set up to match what you are currently doing. It would be nice if there was a tool that would help find out this information for you. This could be part of an automated config initialization tool (#183) , or also a separate thing.

貢獻者指南

技術棧
javascriptnodejs
領域
toolingdeveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
JavaScriptNode.jsAST parsing concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Explore the Import JS codebase to understand how aliases and named exports are currently configured (e.g., in .importjs.js). Review issue #183 for related work on automated config initialization. Investigate using AST parsing (e.g., with Babel) to scan a project's imports and detect patterns. Propose a design for a CLI command that outputs detected aliases and named exports.