s at compile time?](#how-about-implicit-optimizations-at-compile-time) - [Inspiration](#inspiration) - [Other Solutions](#other-solutions) - [Issues](#issues) - [πŸ› Bugs](#-bugs) - [πŸ’‘ Feature Requests](#-feature-requests) - [Contributors ✨](#contributors-) - [LICENSE](#license) ## Installation This module is distributed via [npm][npm] which is bundled with [node][node] and should be installed as one of your project's `devDependencies`: ``` npm install --save-dev babel-plugin-macros ``` ## Usage > You may like to watch > [this YouTube video](https://www.youtube.com/watch?v=1queadQ0048&list=PLV5CVI1eNcJgCrPH_e6d57KRUTiDZgs0u) > to get an idea of what macros is and how it can be used. ### User docs Are you trying to use `babel-plugin-macros`? Go to [`other/docs/user.md`](other/docs/user.md). ### Author docs Are you trying to make your own macros that works with `babel-plugin-macros`? Go to [`other/docs/author.md`](other/docs/author.md). (you should probably read the user docs too). ### Caveats #### Babel cache problem > **Note:** This issue is not present when used in Create React App. Most of the time you'll probably be using this with the babel cache enabled in webpack to rebuild faster. If your macro function is **not pure** which gets different output with same code (e.g., IO side effects) it will cause recompile mechanism fail. Unfortunately you'll also experience this problem while developing your macro as well. If there's not a change to the source code that's being transpiled, then babel will use the cache rather than running your macro again. For now, to force recompile the code you can simply add a cache busting comment in the file: ```diff import macro from 'non-pure.macro'; -// Do some changes of your code or +// add a cache busting comment to force recompile. macro('parameters'); ``` This problem is still being worked on and is not unique to `babel-plugin-macros`. For more details and workarounds, please check related issues below: - babel-plugin-preval: [How to force recompile? #19](https://github.com/kentcdodds/babel-plugin-preval/issues/19) - graphql.macro: [Recompile problem (babel cache) #6](https://github.com/evenchange4/graphql.macro/issues/6) - twin.macro: [Can't change taliwind config #37](https://github.com/ben-rogerson/twin.macro/discussions/37) ## FAQ ### How do I find available macros? You can write your own without publishing them to `npm`, but if you'd like to see existing macros you can add to your project, then take a look at the [Awesome babel macros](https://github.com/jgierer12/awesome-babel-macros) repository. Please add any you don't see listed! ### What's the difference between babel plugins and macros? Let's use [`babel-plugin-console`](https://www.npmjs.com/package/babel-plugin-console) as an example. If we used `babel-plugin-console`, it would look like this: 1. Add `babel-plugin-console` to `.babelrc` 2. Use it in a code: ```js function add100(a) { const oneHundred = 100 console.scope('Add 100 to another number') return add(a, oneHundred) } function add(a, b) { return a + b } ``` When that code is run, the `scope` function does some pretty nifty things: **Browser:** ![Browser console scoping add100](https://github.com/mattphillips/babel-plugin-console/raw/53536cba919d5be49d4f66d957769c07ca7a4207/assets/add100-chrome.gif) **Node:** Node console scoping add100 Instead, let's use the macro it's shipped with like this: 1. Add `babel-plugin-macros` to `.babelrc` (only once for all macros) 2. Use it in a code: ```js import scope from 'babel-plugin-console/scope.macro' function add100(a) { const oneHundred = 100 scope('Add 100 to another number') return add(a, oneHundred) } function add(a, b) { return a + b } ``` The result is exactly the same, but this approach has a few advantages: **Advantages:** - requires only one entry in `.babelrc` for all macros used in project. Add that once and you can use all the macros you want - toolkits (like [create-react-app][cra]) may already support `babel-plugin-macros`, so no configuration is needed at all - it's explicit. With `console.scope` people may be fooled that it's just a normal `console` API when there's really a babel transpilation going on. When you import `scope`, it's obvious that it's macro and does something with the code at compile time. Some ESLint rules may also have issues with plugins that look for "global" variables - macros are safer and easier to write, because they receive exactly the AST node to process - If you misconfigure `babel-plugin-console` you wont find out until you run the code. If you misconfigure `babel-plugin-macros` you'll get a compile-time error. **Drawbacks:** - Cannot (should not) be used for implicit transpilations (like syntax plugins) - Explicitness is more verbose. Which some people might consider a drawback... ### In what order are macros executed? This is another advantage of `babel-plugin-macros` over regular plugins. The user of the macro is in control of the ordering! The order of execution is the same order as imported. The order of execution is clear, explicit and in full control of the user: ```js import preval from 'preval.macro' import idx from 'idx.macro' // preval macro is evaluated first, then idx ``` This differs from the current situation with babel plugins where it's prohibitively difficult to control the order plugins run in a particular file. ### Does it work with function calls only? No! Any AST node type is supported. It can be tagged template literal: ```js import eval from 'eval.macro' const val = eval`7 * 6` ``` A function: ```js import eval from 'eval.macro' const val = eval('7 * 6') ``` JSX Element: ```js import Eval from 'eval.macro' const val = 7 * 6 ``` Really, anything... See the [testing snapshot](src/__tests__/__snapshots__/index.js.snap) for more examples. ### How about implicit optimizations at compile time? All examples above were _explicit_ - a macro was imported and then evaluated with a specific AST node. Completely different story are _implicit_ babel plugins, like [transform-react-constant-elements](https://babeljs.io/docs/plugins/transform-react-constant-elements/), which process whole AST tree. Explicit is often a better pattern than implicit because it requires others to understand how things are globally configured. This is in this spirit are `babel-plugin-macros` designed. However, some things _do_ need to be implicit, and those kinds of babel plugins can't be turned into macros. ## Inspiration - [threepointone/babel-plugin-macros](https://github.com/threepointone/babel-plugin-macros) - [facebookincubator/create-react-app#2730][cra-issue] Thank you to [@phpnode](https://github.com/phpnode) for donating the npm package `babel-plugin-macros`. ## Other Solutions - [sweetjs](http://sweetjs.org/) ## Issues _Looking to contribute? Look for the [Good First Issue][good-first-issue] label._ ### πŸ› Bugs Please file an issue for bugs, missing documentation, or unexpected behavior. [**See Bugs**][bugs] ### πŸ’‘ Feature Requests Please file an issue to suggest new features. Vote on feature requests by adding a πŸ‘. This helps maintainers prioritize what to work on. [**See Feature Requests**][requests] ## Contributors ✨ Thanks goes to these people ([emoji key][emojis]):

Kent C. Dodds

πŸ’» πŸ“– πŸš‡ ⚠️

Sunil Pai

πŸ€”

Lily Scott

πŸ’¬ πŸ“–

Michiel Dral

πŸ€”

Kye Hohenberger

πŸ€”

Mitchell Hamilton

πŸ’» ⚠️

Justin Hall

πŸ“–

Brian Pedersen

πŸ’» πŸ“–

Andrew Palm

πŸ’»

Michael Hsu

πŸ“– πŸ”Œ

Bo Lingen

πŸ’»

Tyler Haas

πŸ“–

FWeinb

πŸ’»

TomΓ‘Ε‘ Ehrlich

πŸ› πŸ’»

Jonas Gierer

πŸ“–

LoΓ―c Padier

πŸ’»

Paul Sherman

πŸ’»

Conrad Buck

πŸ’» ⚠️ πŸ“–

InvictusMB

⚠️

Eric Berry

πŸ”

Futago-za Ryuu

πŸ’» ⚠️

Luc

πŸ’»

Victor Vincent

πŸ’»

я ΠΊΠΎΡ‚ΠΈΠΊ ΠΏΡƒΡ€-ΠΏΡƒΡ€

πŸ“–

Armando Sosa

πŸ“–

Matthias

πŸ’»

Jovi De Croock

πŸ’» ⚠️

Victor Arowo

πŸ“–

Alex Chan

πŸ“–

Evan Jacobs

πŸ’»
This project follows the [all-contributors][all-contributors] specification. Contributions of any kind welcome! ## LICENSE MIT [npm]: https://www.npmjs.com [node]: https://nodejs.org [build-badge]: https://img.shields.io/github/workflow/status/kentcdodds/babel-plugin-macros/validate?logo=github&style=flat-square [build]: https://github.com/kentcdodds/babel-plugin-macros/actions?query=workflow%3Avalidate [coverage-badge]: https://img.shields.io/codecov/c/github/kentcdodds/babel-plugin-macros.svg?style=flat-square [coverage]: https://codecov.io/github/kentcdodds/babel-plugin-macros [version-badge]: https://img.shields.io/npm/v/babel-plugin-macros.svg?style=flat-square [package]: https://www.npmjs.com/package/babel-plugin-macros [downloads-badge]: https://img.shields.io/npm/dm/babel-plugin-macros.svg?style=flat-square [npmtrends]: http://www.npmtrends.com/babel-plugin-macros [license-badge]: https://img.shields.io/npm/l/babel-plugin-macros.svg?style=flat-square [license]: https://github.com/kentcdodds/babel-plugin-macros/blob/main/LICENSE [prs-badge]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square [prs]: http://makeapullrequest.com [coc-badge]: https://img.shields.io/badge/code%20of-conduct-ff69b4.svg?style=flat-square [coc]: https://github.com/kentcdodds/babel-plugin-macros/blob/main/CODE_OF_CONDUCT.md [emojis]: https://github.com/all-contributors/all-contributors#emoji-key [all-contributors]: https://github.com/all-contributors/all-contributors [all-contributors-badge]: https://img.shields.io/github/all-contributors/kentcdodds/babel-plugin-macros?color=orange&style=flat-square [bugs]: https://github.com/kentcdodds/babel-plugin-macros/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+sort%3Acreated-desc+label%3Abug [requests]: https://github.com/kentcdodds/babel-plugin-macros/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc+label%3Aenhancement [good-first-issue]: https://github.com/kentcdodds/babel-plugin-macros/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc+label%3Aenhancement+label%3A%22good+first+issue%22 [preval]: https://github.com/kentcdodds/babel-plugin-preval [cra]: https://github.com/facebook/create-react-app [cra-issue]: https://github.com/facebook/create-react-app/issues/2730