tleunen/babel-plugin-module-resolver

Custom module resolver plugin for Babel

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Type:Plugin / ExtensionCategory(s):Build Systems & Package ManagersDeveloper Tools
Added to GitGenius on September 20th, 2026
Created on August 16th, 2015
Open Issues & Pull Requests: 109 (+0)
GitHub issues: Enabled
Number of forks: 204
Total Stargazers: 3,471 (+0)
Total Subscribers: 14 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,106 days
Stale 30+ days: 5
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

babel-plugin-module-resolver is a Babel plugin that adds custom module resolution to your build process.

The plugin solves the problem of unwieldy relative import paths in JavaScript projects. Instead of writing deeply nested paths like `../../../../utils/my-utils`, you can define custom root directories and aliases in your Babel configuration, then import from those simplified paths. The plugin intercepts module resolution during Babel compilation and rewrites the import statements to point to the correct locations.

You should adopt this tool if your project uses Babel and you want cleaner, more maintainable import statements. It works well in any JavaScript project structure where relative paths become cumbersome, particularly in monorepos or projects with deep directory hierarchies. The README documents integration with ESLint through eslint-plugin-import and eslint-import-resolver-babel-module to catch unresolved modules, and provides guidance for editor autocompletion in Atom, VS Code, and IntelliJ-based IDEs. The plugin also exposes functions for other plugin authors to build integrations on top of it.

The project maintains active test coverage across Linux and Windows platforms. Development activity shows consistent attention to both bug fixes and feature requests, with documentation kept current alongside code changes. The maintainers have established clear patterns for configuration and provide examples covering common use cases.