Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Initial Roadmap Suggestions #7192
I'm interested in questions/feedback and but more importantly people to help!
This isn't just to explain to you the work we are going to do but to ask you to get involved in some ideas that aren't fully thought out yet or started
In this PR we can add more points and details if anyone has questions, or we can create a new issue (if there isn't one already) for further discussion.
Looking forward to some new contributors
EDIT: dang if I edit people's comments become "outdated" in the diff
What I'd like to see soon (all related to v6 to v7 support):
stefanpenner left a comment •
Another big ticket item would be addressing source maps.
Currently, babel and it's plugins author produce invalid source-maps. Although some manual spot-checks may work, various aspects of the current approach appear fundamentally flawed. This results in breaking downstream tools, and a poor debugging experience (both in dev, and in prod).
More details here: #6008
Original our team hoped to get resources to work on this problem. Unfortunately do to conflicting obligations/resourcing we have been unable to secure the required resourcing.
Plugin Compat / Transition Plan
One the largest pains I had (and continue to have) with the babel 5 to 6 transition, was plugins. If there are planned breaking changes, we should attempt to avoid them, but if they are unavoidable, a proper transition guide and tooling (maybe a code-mod) would really help.
Checking plugin compatibility if breaks occur would be handy, either a version encoded in the plugin or some sort of capability check (or both). Lots of our users had pretty poor experiences, as forgetting to upgrade one plugin or another resulted in very poor errors.
Not sure if this feedback is useful, but I'm working on a tool that consumes