Galooshi/import-js

Find aliases and named exports in existing project

Open

#184 opened on Jan 31, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (519 stars) (70 forks)batch import
enhancementhelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScriptNode.jsAST parsing concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
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.