tsx
chakra-ui
Our great sponsors
tsx | chakra-ui | |
---|---|---|
23 | 344 | |
7,569 | 36,454 | |
6.9% | 1.0% | |
9.1 | 9.0 | |
5 days ago | 8 days ago | |
TypeScript | MDX | |
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.
tsx
-
Finally, a guide for Node.js and TypeScript and ESM that works
I really enjoy frontend/node/typescript development. I roll my eyes whenever the HN-types complain about CSS or frontend development being a hellhole. Mostly the comments I see seem ignorant or impatient ("Why doesn't this thing work without be bothering to learn it?")
However, the intersection of typescript, nodejs, and ES modules is consistently the most frustrating experience I ever have. Trying to figure out which magic incantation of tsconfig/esbuild/tsc/node options will let me just write code and run it is a fools errand. You might figure something out, and then you try to use Jest and then you descend into madness again.
The biggest tip I can give people is to ditch ts-node and just use (the awkwardly named) tsx https://github.com/privatenumber/tsx, which pretty much just "mostly works" for running Typescript during dev for node.
The problem mostly seems to stem for all the stakeholders being pretty dogmatic to whatever their goals are, rather than the pragmatic option of just meeting people where they are. I really wish the Node, Typescript, Deno/Bun, and maybe some bundler people would come together and figure out how to make this easier for people.
I’ve found TSX to be a better alternative to ts-node. It seems to have more sensible defaults in 2023. https://github.com/privatenumber/tsx
-
ERDIA: TypeORM entity specification documentation tool
If your TypeORM entity is written in TypeScript, you have to run ERDIA using ts-node or tsx as follows.
-
xtsz - a TS / JS file runner with support for HTTP/S imports
Want to import a package / file conveniently from esm.sh or unpkg or directly from a GitHub repo for a one-off script (for example). To do this I created a custom ESBuild plugin to handle HTTP imports - that worked for ,js files. To support running both ESM and CJS, I use tsx.
-
What is your must have npm package on any given project?
I prefer tsx honestly. Nodemon will detect that your using TypeScript and switch from node to ts-node but tsx is a no config necessary version of ts-node that also runs faster. Of course you can configure ts-node to use swc to be faster but then you're playing with config files to get things working.
-
Thoughts about Deno?
I’ve been trying to adopt Deno into new projects, but I find Node through tsx good enough.
-
Will nodeJs ever have out of the box typescript support?
try tsx. it has support for watch mode and works great with esm module projects.
-
Why is this so hard to do? Help
This is the answer: https://github.com/esbuild-kit/tsx
-
<3 Deno
Have a look at https://github.com/esbuild-kit/tsx
_tsx is a CLI command (alternative to node) for seamlessly running TypeScript & ESM, in both commonjs & module package types.
It's powered by esbuild so it's insanely fast._
-
Achieving end-to-end type safety in a modern JS GraphQL stack
TSX, to run TypeScript without compiling the code;
chakra-ui
-
React Component Libraries
Official Website: https://chakra-ui.com/
-
Material UI vs. Chakra UI: Which One to Choose?
Discover Chakra UI: Chakra UI Documentation
- Tailwind Color Palette Generator
-
Minified React error #426
This error related to the ReactMarkdown component and the useDisclosure hook in the @chakra-ui/react.
-
Shoelace: A forward-thinking library of web components
We settled on Chakra (https://chakra-ui.com/). Although we also abandoned our ambitions of a Next.js migration, so... I guess it didn't really end up mattering all that much anyway.
-
33 React Libraries Every React Developer Should Have In Their Arsenal
4.chakra-ui
-
⚡Top GitHub Repositories for UI Components
🔍 Site ⭐ GitHub
-
Beyond the Basics: Exploring TailwindCSS and Linaria in Next.js - From Installation to Performance Optimization
Examples: radix-ui, chakra-ui, shadcn/ui, tailwind-ui.
-
Ask HN: Examples of best practice modern website design?
(I'm a frontend dev, but I came into the design side only later in my career, after having started as a full-stack programmer.)
I think this book is probably the single best resource I've seen on the topic: https://www.refactoringui.com/
It's a really easy-to-use format (one quick tip on each page, with clear examples).
It's from the people who made Tailwind, a CSS framework that's basically a reimagining of Bootcamp for the Javascript/component era.
Check out some of their templates: https://tailwindui.com/templates
These are lookalike "modern" designs that you can pay to use, or just draw inspiration from. Imitation == flattery and all that.
Along similar lines, check out the free Next.js templates: https://vercel.com/templates/next.js
If you want to build up from components instead, Tailwind offers a component library too: https://tailwindui.com/components
For React, I prefer the astoundingly good MUI framework (amazing components with lots of customizability, a good enough default look, and great documentation): https://mui.com/ If you end up going this route, using their Figma kit (https://mui.com/store/items/figma-react/) plus the Refactoring UI book from above should allow you to whip up a pretty standard-looking, "pretty enough" design in very little time. And then implementing it using the actual MUI lib would just take a few days.
There's also Ant Design: https://ant.design/
And Chakra UI: https://chakra-ui.com/
-----------
For more theoretical stuff (i.e., less visual but still very valuable), the UX research group Nielsen Norman still has a treasure trove of valuable advice: https://www.nngroup.com/articles/top-ten-guidelines-for-home...
You should know the basics of accessibility (beyond general usability, this alos means alt text, header levels, contrast ratios, readability, screen readers, keyboard navigation, special considerations for the hard of sight and hearing, etc.): https://www.w3.org/WAI/standards-guidelines/wcag/ or at least use an easy checklist tool like Microsoft's WCAG analyzer: https://accessibilityinsights.io/
- Ask HN: What's your favorite UI library?
What are some alternatives?
mantine - A fully featured React components library
antd - An enterprise-class UI design language and React UI library
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
Tailwind CSS - A utility-first CSS framework for rapid UI development.
react-star-rating-input - React.js components for entering 0—N stars (N is 5 by default), or displaying 0—N stars
Material UI - Ready-to-use foundational React components, free forever. It includes Material UI, which implements Google's Material Design.
grommet - a react-based framework that provides accessibility, modularity, responsiveness, and theming in a tidy package
rebass - :atom_symbol: React primitive UI components built with styled-system.
primereact - The Most Complete React UI Component Library
base web - A React Component library implementing the Base design language
shadcn/ui - Beautifully designed components that you can copy and paste into your apps. Accessible. Customizable. Open Source.
react-draft-wysiwyg - A Wysiwyg editor build on top of ReactJS and DraftJS. https://jpuri.github.io/react-draft-wysiwyg