babel-plugin-macros
super-expressive.macro
Our great sponsors
| babel-plugin-macros | super-expressive.macro | |
|---|---|---|
| 6 | 1 | |
| 2,604 | 9 | |
| - | - | |
| 0.0 | 0.0 | |
| 11 months ago | about 3 years ago | |
| JavaScript | TypeScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
babel-plugin-macros
-
Fixing Class Composition in Tailwind CSS
One of the more promising alternatives is twin.macro - a Babel macro that processes Tailwind classes to generate JS objects understandable by various CSS-in-JS libraries. The developer experience (DX) of using it is amazing as you not only get all of Tailwind’s features without much change to your code, but you also get much more flexibility - all that on top of the traditional benefits of CSS-in-JS. Here’s an example code:
-
[AskJS] My approach to Application Config, what does the JS community think of this?
For example with Babel you could use babel-plugin-macros to execute this file at compile time and replace the file contents with the result of the computation. So appSettings would only have the configs for the current environment and nothing more and your source wouldn't need to change much.
-
I made a package to help you with file-system based routing for react-router-dom
It does require babel-plugin-macros which should also help with keeping things nice and performant in production. The package is part of a larger initiative im trying to achieve which is to create file-system based routing for all mainstream React and React Native routing packages. I have done everything I can to keep it as boilerplate free as I can. To give an example
-
Jest Error in a NextJS project. babel-jest is unable to find my babel.config.js
MacroError: The macro you imported from "undefined" is being executed outside the context of compilation with babel-plugin-macros. This indicates that you don't have the babel plugin "babel-plugin-macros" configured correctly. Please see the documentation for how to configure babel-plugin-macros properly: https://github.com/kentcdodds/babel-plugin-macros/blob/master/other/docs/user.md
-
I am creating a pattern-matching plugin in javascript. This is what it does. Are you interested in using it?
Yes, it also does that. https://github.com/kentcdodds/babel-plugin-macros
-
A tale of knowledge building
babel-plugin-macros
super-expressive.macro
-
A tale of knowledge building
After a couple of weeks of playing around with the idea and learning much more about Babel plugins in the process, I released super-expressive.macro - a macro to generate Regular Expressions (RegExp) at build-time with super-expressive.
What are some alternatives?
babel-plugin-styled-components - Improve the debugging experience and add server-side rendering support to styled-components
babel-handbook - :blue_book: A guided handbook on how to use Babel and how to create plugins for Babel.
nextjs-typescript-starter - A starter project with NextJS, Typescript and Tailwind/Styled Components
babel-plugin-tsconfig-paths-module-resolver - Use tsconfig-paths in any bundler that supports a custom babel config.
babel-plugin-transform-react-remove-prop-types - Remove unnecessary React propTypes from the production build. :balloon:
super-expressive - 🦜 Super Expressive is a zero-dependency JavaScript library for building regular expressions in (almost) natural language
jsx-control-statements - Neater If and For for React JSX
babel-plugin-module-resolver - Custom module resolver plugin for Babel
babel-plugin-proposal-pattern-matching - the minimal grammar, high performance JavaScript pattern matching implementation
htm - Hyperscript Tagged Markup: JSX alternative using standard tagged templates, with compiler support.