react-tw-blog-post
A component library built with React + Tailwind + TSDX for a blog post. (by hamatoyogi)
changesets
🦋 A way to manage your versioning and changelogs with a focus on monorepos (by changesets)
SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
react-tw-blog-post | changesets | |
---|---|---|
1 | 30 | |
13 | 8,033 | |
- | 1.8% | |
1.6 | 5.4 | |
11 months ago | 7 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
react-tw-blog-post
Posts with mentions or reviews of react-tw-blog-post.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-16.
-
How to Build A React TS Tailwind Design System
If you want to skip ahead to the "How to" section click here, or if you want to go straight ahead to the final code, check out the repository here.
changesets
Posts with mentions or reviews of changesets.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-27.
-
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.