tsdx VS semantic-release

tsdx - Zero-config CLI for TypeScript package development

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

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?

NOTE: If your project uses TypeScript, I would suggest using tsdx instead.

Sadly, it's a bit dead. We switched to dts-cli fork, but tsup looks good too

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

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.

May be you need to try https://tsdx.io/

So what is the ideal way to build TypeScript libraries? I've heard that tsdx https://tsdx.io/ is quite good

There’s tsdx. But I’d recommend using Vite and storybook-vite

I'm trying to improve the security behind our release process, which uses semantic-release. During this process, it creates a change log which is committed to the repo, publishes a package and a few other things.

Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.

When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.

To further streamline deployments, I introduced semantic-release. This tool automates commit tagging and tracks changes since the previous version. As a result, deployments now occur only when new tags are present, saving us valuable minutes.

If your projects ar made in javascript and related tools, I'd suggest you to check: semantic-release