babel / babel/babel-upgrade

Tracking: handling JavaScript files

Open
#39 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
1.3k
Forks
53
PR merge metrics
No merged PRs in 30d

Description

> Tracked in the readme already but made an issue since not many people read the readme

We should use jscodeshift/babel-codemod for this.

- [ ] Upgrade a js config: `.babelrc.js`, `babel.config.js`, a preset written in JS, or a babel config written via `@babel/core` options or `babel-loader`.
- [ ] Upgrade any tools that use Babel directly
- [ ] import statements like `babel-types` to `@babel/types`
- [ ] API removals/deprecations/changes

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the README’s tracking entry and the handling for JavaScript files in the upgrade tool. Check the listed Babel configuration forms and direct Babel-tool usage, including babel-types imports and API changes. Done means the checklist cases are handled through jscodeshift or babel-codemod.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.