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.