`@babel/core` fails in all current variants
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 606
- Forks
- 157
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
Situation
Running citgm @babel/core fails all tests
macos/ubuntu/windows
Node.js 22/24/26
Steps to reproduce
Run https://github.com/nodejs/citgm/actions/workflows/test-module.yml
Module to test: @babel/core
CITGM repository to checkout: nodejs/citgm
CITGM GitHub ref to checkout: main
Result
See https://github.com/MikeMcC399/citgm/actions/runs/34339097913
cc: @nicolo-ribaudo @JLHwung @liuxingbaoyu
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the test-module.yml workflow and the linked CITGM run, using the main ref and the @babel/core module named in the issue. Reproduce the failure across the listed macOS, Ubuntu, and Windows with Node.js 22, 24, and 26, then trace the failing test output. Done means the @babel/core tests pass for the affected variants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100