twin.examples
changesets
twin.examples | changesets | |
---|---|---|
5 | 30 | |
460 | 8,049 | |
- | 2.0% | |
6.4 | 5.4 | |
about 1 month ago | 15 days ago | |
TypeScript | TypeScript | |
- | 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.
twin.examples
-
How to load a GLTF model inside NextJS in 2022
Hey, I'm trying (and failing) to put together a codesandbox. I think it's easier to replicate the steps from here: https://github.com/ben-rogerson/twin.examples/tree/master/next-styled-components
-
How to set up _document.js with twin.macro + Google Analytics ?
well, this is exactly how it's set up in the twin.macro example repo with next.js, and it is working perfectly fine?
-
How to setup create-react-app twin.macro and emotion
You can pretty much follow all the steps from this tutorial, until this point where it tells you to extend JSX with a jsx-pragma in front of every twin.macro import. The documentation underneath says the following:
-
How to Build A React TS Tailwind Design System
Alright, I had my tools in place and it was time to start connecting the dots, so to speak. I kicked off a new TSDX project, installed Styled components, and then went on to try and set up twin.macro. However, I hit a snag there... In the Twin example repo, there was no Styled Components + Storybook example, so I configured what seemed to make sense. Then I went on to add some samples, imported them into a new Story, and tried to run Storybook. It didn't work as expected. Some of the code worked and other components that were using the tw syntax didn't:
-
Boilerplate with React 17, Webpack 5, Tailwind 2, using babel, sass, with a hot dev server and an optimized production build
the biggest would be as a plugin to compile/transpile other language macros for example twin-macro (styled components using tailwind syntax) https://github.com/ben-rogerson/twin.examples/tree/master/component-library-styled-components/packages/components
changesets
-
I made a set of devtools for small projects
In my circles, this is the go-to for release automation / changelogs: https://github.com/changesets/changesets
-
Criando um Design System reutilizável entre React e React Native com Tamagui
🦋 Publicando com changesets
- Changesets
-
Nx - Highlights of 2023
Open source libraries and frameworks share a common necessity: the need to develop multiple packages cohesively and efficiently while managing their versioning and publishing to NPM. Nx has emerged as a go-to choice for handling such open source monorepos (as we'll explore further in the next section of this blog post). Until recently, one area Nx did not address directly was versioning and release management. Traditionally, this gap has been filled with tools like release-it, changesets, or custom Node scripts, similar to our approach in the Nx repository.
-
Automate NPM releases on GitHub using changesets 🦋
Doing these tasks by hand can quickly become a hassle. If you're open to receiving contributions from others, it can be an even bigger headache. In this post we'll cover how to use changesets to automate all of these steps.
- Show HN: Changesets, manage your versioning and changelogs
-
[AskJS] Advice on how to manage breaking changes in the first versions of a UI Library
For versioning we use changeset, but with fixed-packages. We have found that the user thinks updating and managing our dependencies much easier if they can just bump each package to the same version. (storybook, sanity follows this appoach). While it feels unintuitive that each package gets a major if just the CSS has breaking changes, the user don't really care. They just want to finish the chore of updating their dependencies fast, without having to understand the system that deeply. This also makes documenting the changes much easier!
- [Reactjs] React UI Composant Library Playplate
-
Hey guys, I made a small CLI to automatically update monorepo packages and NPM releases. I would like some feedback.
Thanks for sharing this. Why should I choose that instead of Changesets that work like a charm?
-
Conventional Commits - Am I missing something?
You’re right this information would be better suited for for commit trailers. A lot more information can be put there as well. For the purpose of changelog generation, what it’s commonly used for, it could just as well be put in the trailers and not crammed into the subject. I personally prefer changesets though.
What are some alternatives?
prettier-eslint - Code :arrow_right: prettier :arrow_right: eslint --fix :arrow_right: Formatted Code :sparkles:
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
twin.macro - 🦹♂️ Twin blends the magic of Tailwind with the flexibility of css-in-js (emotion, styled-components, solid-styled-components, stitches and goober) at build time.
nx - Smart Monorepos · Fast CI
tailpress - TailPress is a minimal boilerplate theme for WordPress using Tailwind CSS.
semver - Semantic Versioning Specification
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
Visual Studio Code - Visual Studio Code
eslint-config-prettier - Turns off all rules that are unnecessary or might conflict with Prettier.
pnpm - Fast, disk space efficient package manager
react-webpack-5-tailwind-2 - React 17 Boilerplate with Webpack 6, Tailwind 2, using babel, SASS/PostCSS, HMR, dotenv and an optimized production build
berry - 📦🐈 Active development trunk for Yarn ⚒