tsdx
turborepo
DISCONTINUED
Our great sponsors
tsdx | turborepo | |
---|---|---|
45 | 79 | |
11,135 | 14,873 | |
0.3% | - | |
0.0 | 9.8 | |
10 months ago | over 1 year ago | |
JavaScript | Rust | |
MIT License | Mozilla Public License 2.0 |
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.
tsdx
-
ReactJS Good Practices
tsdx - Zero-config CLI for TypeScript package development
-
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
Used https://tsdx.io/ recently to do this, saved a lot of time and effort.
-
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.
-
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
-
How to include dependent types in library build?
I'd just add the types as a dependency but if you want to bundle them then afaik https://github.com/jaredpalmer/tsdx can do it (though I have never tried).
turborepo
-
Learn how to build a monorepo in Next.js
Turborepo: Smart build system for JavaScript/TypeScript monorepos
-
Building a full-stack TypeScript application with Turborepo
We’ve only scratched the surface of what we can do with Turborepo. You can find more examples in the Turborepo examples directory on GitHub. Skill Recordings on GitHub is also another great resource that has been around since Turborepo was first released.
-
10 Trending Github repositories / October, 27 2022
git clone https://github.com/vercel/turborepo.git
-
Component composition
I use https://turborepo.org/ to facilitate my monorepo. Essentially it's a way of structuring your configs, UI; apps etc and you consume each like an internal package. I find benefits for this as the kinds of sites I make will generally have an internal app, an admin panel and a marketing site. I can write UI, config etc in one place and consume them over the three projects to keep everything consistent.
-
How I Monorepo
The latest addition to the Composer Suite monorepo, Turborepo optimizes monorepo workflows by caching build artifacts. This may sound a little abstract and boring, but what this actually means is that when you build something within your monorepo, Turborepo will make sure only the things that it depends on are rebuilt; everything else will be retrieved from a cache that either lives on your local computer, or a remote cache server. Adding Turborepo to the Composer Suite monorepo pretty much halved CI build times, but it was also a way to teach Vercel, which I use for hosting the various example apps in the repo, to only actually deploy the ones that have changed since their last deployment. And that's really cool!
- What is the easiest way to use shared code with multiple Vue3 projects?
-
The different strategies to building a cross-platform app
NB: "Turbo" also has other meanings in a React Native context, so don't confuse Hotwire Turbo Native with Turbo Modules or Turborepo (as used in create-t3-turbo, mentioned later here).
-
Minimal Nextjs-Typescript boilerplate
Personally I just use this: https://github.com/vercel/turborepo/tree/main/examples/with-tailwind
-
Shared packages between React Native and Web project in monorepo.
To set up our monorepo we will use Turborepo which will take care of installing the basic parameters for us.
- Partager son code entre des projets React et React Native sur un monorepo
What are some alternatives?
nx - Smart Monorepos · Fast CI
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
vite - Next generation frontend tooling. It's fast!
rushstack - Monorepo for tools developed by the Rush Stack community
Microbundle - 📦 Zero-configuration bundler for tiny modules.
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
parcel - The zero configuration build tool for the web. 📦🚀
tsup - The simplest and fastest way to bundle your TypeScript libraries.
create-react-app - Set up a modern web app by running one command.
Bazel - a fast, scalable, multi-language and extensible build system
lage - Task runner in JS monorepos