tleunen/babel-plugin-module-resolver

Document in README.md how to debug/print search path

Open

#187 建立於 2017年5月25日

在 GitHub 查看
 (1 留言) (3 反應) (0 負責人)JavaScript (3,417 star) (217 fork)batch import
enhancementhelp wanted

描述

The readme describes basic usage, but when the basic setup doesn't work, it's hard to know what to do.

There should be some command to run in order to test a simple import and get the search path printed, next steps in order to debug and/or similar.

貢獻者指南

技術棧
javascriptnodejs
領域
documentationdeveloper experience
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
無
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
Review the current README.md in the repository to understand the existing basic usage section. Look at the plugin's source code (e.g., src/index.js) to identify how the search path is resolved and printed. Consider adding a dedicated debugging section with commands like `node e "require('babel plugin module resolver')"` or using an environment variable to log search path. Check if any existing issues or pull requests discuss debugging (e.g., issue #187 itself has a comment with suggestions). Write clear steps for common debugging scenarios.