babel-plugin-macros
twin.macro
babel-plugin-macros | twin.macro | |
---|---|---|
6 | 57 | |
2,605 | 7,809 | |
- | - | |
0.0 | 5.9 | |
11 months ago | about 1 month 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
twin.macro
-
Tailwindcss in Styled-Components
Twin Macro Github Repo. This is a great resource to help you pick up Twin’s syntax, learn more about the package, and keep up to date with the latest releases.
-
CSS Style Guide for Web Dev?
Personally I like twin.macro the most. It’s similar to the above but based on Tailwind.
-
Cool Tailwindcss Tools For Everyone
twin.macro is a library that allows you to use these styles in your JavaScript code. This library works exactly like styled-components.
- How do you css?
-
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:
-
Setup Nextjs Tailwind CSS Styled Components with TypeScript
twin.macro
-
What unpopular webdev opinions do you have?
If you use Tailwind with React a lot, and are wanting support for Styled Components, give Twin Macro a look. They're close to finishing support for TW v3 in their Releases section :)
- Are utility classes horrible design or am I dumb?
- What's the proper way to write Tailwind with React?
-
Stailwc: an swc plugin for transpiling tailwind directives at compile time
The blocker for us using it is our use of an excellent library called twin.macro which is built against babel's transpilation APIs to parse tailwindcss directives at compile time so that they may be used with css-in-js libraries. This efficiently bundles your css so that you only ship the precise css you use. The problem is, it's all quite slow.
What are some alternatives?
babel-plugin-styled-components - Improve the debugging experience and add server-side rendering support to styled-components
twind - The smallest, fastest, most feature complete Tailwind-in-JS solution in existence.
nextjs-typescript-starter - A starter project with NextJS, Typescript and Tailwind/Styled Components
Tailwind CSS - A utility-first CSS framework for rapid UI development.
babel-plugin-transform-react-remove-prop-types - Remove unnecessary React propTypes from the production build. :balloon:
tailwindcss-classnames - Functional typed classnames for TailwindCSS
jsx-control-statements - Neater If and For for React JSX
jest-styled-components - 🔧 💅 Jest utilities for Styled Components
babel-plugin-module-resolver - Custom module resolver plugin for Babel
vue-emotion - Seamlessly use emotion (CSS-in-JS) with Vue.js
babel-plugin-proposal-pattern-matching - the minimal grammar, high performance JavaScript pattern matching implementation
tailwind-safelist-generator - Tailwind plugin to generate purge-safe.txt files