typescript-plugin-styled-components
tsdx
Our great sponsors
| typescript-plugin-styled-components | tsdx | |
|---|---|---|
| 1 | 45 | |
| 418 | 11,157 | |
| - | 0.4% | |
| 4.8 | 0.0 | |
| 11 months ago | 11 months ago | |
| TypeScript | JavaScript | |
| - | 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.
typescript-plugin-styled-components
-
Is babel still relevant for TypeScript projects ?
In this particular case, there is an alternative to make it work without babel, but:
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?
awesome-babel-macros - A collection of awesome babel macros and related resources
Microbundle - 📦 Zero-configuration bundler for tiny modules.
sucrase - Super-fast alternative to Babel for when you can target modern JS runtimes
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]
react-prime - A starter kit to create comprehensive React apps with React-Query and Styled-Components.
parcel - The zero configuration build tool for the web. 📦🚀
typescript-transformer-handbook - 📘 A comprehensive handbook on how to create transformers for TypeScript with code examples
tsup - The simplest and fastest way to bundle your TypeScript libraries.
Next.js - The React Framework
create-react-app - Set up a modern web app by running one command.
typescript-is
nx - Smart Monorepos · Fast CI