changesets
tsdx
Our great sponsors
changesets | tsdx | |
---|---|---|
30 | 45 | |
7,998 | 11,148 | |
4.0% | 0.3% | |
5.7 | 0.0 | |
8 days ago | 11 months ago | |
TypeScript | JavaScript | |
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.
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.
tsdx
-
ReactJS Good Practices
tsdx - Zero-config CLI for TypeScript package development
-
Help with bundling a module using webpack
If youāre into TypeScript, I highly recommend https://tsdx.io . Iāve used it to create a package before and itās so much easier
-
Using Next.js components in a custom npm library
Thanks for the insight fellas. Aside question, I was thinking of bootstrapping the project with tsdx, but their last release was well over 2 years ago. Wondering if there are any alternative options for creating libraries?
-
Rollup Library Starter
NOTE: If your project uses TypeScript, I would suggest using tsdx instead.
-
Creating Modern npm Packages
Sadly, it's a bit dead. We switched to dts-cli fork, but tsup looks good too
-
TypeScript is terrible for library developers
I don't depend on the actual typescript docs much but thankfully in @types and in tons of repos there are examples of well written typescript code.
The amount of JS and TS out there is also a bit of a foot gun though so stick with heavily used/starred libs if you aren't sure.
One tool that helps a lot with developing libraries in typescript is TSDX[0] or its successor dts-cli[1] and there is a bunch of good stuff in awesesome-typescript[2].
Maybe library devving is harder?(more work?) with tyepscript but it is worth it for the end developer, especially if that end developer is you. If you aren't using your own libs then you're probably getting paid by someone else to make them or... idk.
https://github.com/jaredpalmer/tsdx
-
How to create your own React Components library
We will use a TSDX library - this tool is something similar to create-react-app, but for creating components library. It allows as to initialize a project immediately with already set up bundler, Rollup with Typescript supporting, testing with Jest, code formatter, Prettier and Storybook.
-
Is there a point in writing in TypeScript personal projects that I will maintain myself?
May be you need to try https://tsdx.io/
-
The Node ecosystem (still) has tooling problems
So what is the ideal way to build TypeScript libraries? I've heard that tsdx https://tsdx.io/ is quite good
-
React component library - 2022 where to start
Thereās tsdx. But Iād recommend using Vite and storybook-vite
What are some alternatives?
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
Microbundle - š¦ Zero-configuration bundler for tiny modules.
nx - Smart Monorepos Ā· Fast CI
turborepo - Incremental bundler and build system optimized for JavaScriptĀ and TypeScript, written in Rust ā including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
semver - Semantic Versioning Specification
parcel - The zero configuration build tool for the web. š¦š
Visual Studio Code - Visual Studio Code
tsup - The simplest and fastest way to bundle your TypeScript libraries.
pnpm - Fast, disk space efficient package manager
create-react-app - Set up a modern web app by running one command.
berry - š¦š Active development trunk for Yarn ā