playfulprogramming / playfulprogramming/playfulprogramming
[Proposed Post]: The Complete Guide to Babel Plugin Authoring
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 227
- Forks
- 106
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 56
Description
Proposed topic title:
The Complete Guide to Babel Plugin Authoring
Topic description:
Babel is the uber-popular JavaScript transpiler. You can extend it by writing your own plugins, here's how
Link to existing draft:
Refer to: https://unicorn-utterances.com/posts/how-computers-speak#ast
Part of series:
No response
Resources
https://stackoverflow.com/questions/43641032/babel-plugin-how-to-get-the-path-for-a-given-node, https://github.com/jamiebuilds/babel-handbook/blob/master/translations/en/plugin-handbook.md#toc-paths, https://github.com/mattphillips/babel-plugin-console/blob/master/src/macros/scope.macro.js, https://stackoverflow.com/questions/35857271/get-current-filename-in-babel-plugin, https://www.sitepoint.com/understanding-asts-building-babel-plugin/, https://stackoverflow.com/questions/44482606/why-is-babel-using-the-arguments-object-for-optional-parameters, https://github.com/kentcdodds/babel-plugin-macros/blob/master/other/docs/author.md, https://github.com/mattphillips/babel-plugin-console/blob/master/src/scope/index.js, https://github.com/mattphillips/babel-plugin-console/blob/master/src/scope/index.js
Other Notes
No response
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 existing draft at https://unicorn-utterances.com/posts/how-computers-speak#ast, then review the linked Babel plugin handbook, AST article, plugin examples, and authoring resources. The topic should become a complete guide to authoring Babel plugins, with the relevant concepts and examples covered clearly enough for readers to follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100