thealexlichter/oxc-reproductions — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2025-04-25
Check whether an unexpected Oxc parsing behavior you hit is already a known, documented issue.
Add a minimal reproduction here when reporting a new bug to the Oxc maintainers.
Browse example files to understand specific edge cases in Oxc's linting or parsing.
| thealexlichter/oxc-reproductions | 0verflowme/alarm-clock | 0verflowme/seclists | |
|---|---|---|---|
| Language | — | CSS | — |
| Last pushed | 2025-04-25 | 2022-10-03 | 2020-05-03 |
| Maintenance | Stale | Dormant | Dormant |
| Setup difficulty | easy | easy | easy |
| Complexity | 1/5 | 2/5 | 1/5 |
| Audience | developer | vibe coder | ops devops |
Figures from each repo's GitHub metadata at analysis time.
README is minimal, value is in browsing individual example folders rather than installing a tool.
This is a collection of example projects and test cases that demonstrate problems or behaviors related to Oxc, which is a JavaScript and TypeScript linter and parser. Think of it as a "bug report gallery", developers use it to share concrete examples of issues they've found, edge cases that don't work as expected, or specific scenarios they want the Oxc team to investigate. The repository serves as a reference point for developers working on Oxc itself, as well as anyone trying to understand whether a particular quirk they've encountered is a known issue. Instead of just describing a problem in words ("my code doesn't parse correctly when I do X"), you can point to an actual reproduction, a minimal example that shows exactly how to trigger the behavior. This makes it much easier for maintainers to debug and fix problems, because they can run the code themselves and see what's happening. If you're using Oxc in your own project and hit something unexpected, you might browse this repository to see if someone has already reported it. Or if you're contributing to Oxc, you might add a new reproduction here to document a bug you're investigating. The repository is essentially a structured, searchable way to track "here's a concrete example of what's broken" rather than relying on scattered GitHub issues or Slack conversations. Because the README is minimal, the real value is in exploring the folder structure and individual example files to see what kinds of issues have been collected. It's a practical tool for the Oxc community rather than a library or tool you'd install yourself.
A collection of minimal example projects that reproduce bugs and edge cases in Oxc, a JavaScript/TypeScript linter and parser.
Stale — no commits in 1-2 years (last push 2025-04-25).
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.