skevy/babel-plugin-resolution-test-case — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2016-02-11
Reproduce a known Babel plugin resolution bug with three commands.
Compare a working vs broken plugin setup side-by-side.
Use as a reference when reporting a similar Babel issue.
Study the exact conditions that trigger the resolution failure.
| skevy/babel-plugin-resolution-test-case | a15n/a15n | a15n/checkout-validation | |
|---|---|---|---|
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | 2016-02-11 | 2019-04-07 | 2014-09-04 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | easy | easy | easy |
| Complexity | 1/5 | 2/5 | 2/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Just clone and run the three README commands, no infra required.
This is a minimal test project that demonstrates a specific issue with how Babel (a popular JavaScript code transformation tool) resolves plugins. The repo contains a working example and a broken example side-by-side, so developers can see the difference. When you run the working script, Babel successfully transforms your JavaScript code using a plugin. When you run the broken script, the same setup fails because Babel can't find or load the plugin properly. The purpose is to isolate and illustrate the bug so the Babel team can understand and fix it. This kind of test case is useful for open-source projects: instead of describing a problem in words, you show the exact steps to reproduce it. Anyone can clone the repo, follow the three commands in the README, and immediately see the issue themselves. That makes it much easier for maintainers to diagnose what's wrong and much harder to accidentally close the issue without actually solving it. If you're contributing to Babel or debugging plugin resolution issues, you'd use this repo as a reference or starting point. It's not a tool you'd install for your own projects, it's more like a lab specimen that holds the problem still long enough to study it.
A minimal reproduction repo showing a bug in how Babel resolves and loads plugins, used to help maintainers diagnose the issue.
Mainly JavaScript. The stack also includes JavaScript, Babel.
Dormant — no commits in 2+ years (last push 2016-02-11).
No license information was found in the explanation.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.