jsx
daisyui
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.
jsx
-
I am having to pass down 8+ props even for simple components. What are some common ways to mitigate this? (Typescript)
Svelte syntax? Yes, there is upcoming initiative JSX 2.0 which includes shorthands like that. However, have no idea whether it will be released any time soon. So let's say "this is part of React/JSX 1.0" (shrugging)
-
Why TypeScript is the better JavaScript
Inherent support for JSX in the language itself
-
Node.js やReact、ESM、Viteの説明
JavaScript + HTML(DOM)= JSX
-
Alpine.js
FWIW, the className prop is a React thing not a JSX thing. Other libraries which use JSX will happily accept a plain class prop. The React limitation is abstraction leakage: props are not attributes, they map to DOM properties.
But to the point that JSX is a DSL, that limitation is specifically because React itself is very tightly coupled to DOM semantics… but JSX explicitly has no built in semantics[1].
1: First sentence of https://facebook.github.io/jsx/ - “JSX is an XML-like syntax extension to ECMAScript without any defined semantics.”
-
React - Introducing JSX
JSX stands for 'JavaScript XML' and is a syntax extension for JavaScript. It is used to create DOM elements that are then rendered in the React DOM. Although it looks like HTML, it is actually an XML-like syntax specifically written for use in React. Interestingly, JSX is not valid JavaScript either. JSX needs to be compiled by a tool like Babel to be translated into regular JavaScript that a browser can understand. Put simply, JSX describes what the UI should look like, and React takes care of properly rendering it.
- Web lagnunages to learn
-
My thoughts on Mithril.js
Alternatively, you can use JSX syntax (like with React), but then you need build-tools.
-
Incrementally adopting TypeScript in a create-react-app project
Note: For React component files (JSX) we'll use .tsx to maintain JSX support and for non React files we'll use the .ts file extension. However, if you want you could still use .ts file extension for React components without any problem.
-
Sciter, the 5 MB Electron alternative, has switched to JavaScript
I’m concerned that you’re falling into the same trap here with integrating your own variant of JSX, and mulling over adding more things like hyphens in unquoted object literal keys.
JSX is popular enough that it’s safe, ECMAScript isn’t going to break it, but your alterations to JSX are already significantly incompatible: you have being equivalent to JSX("input", {"class": "search"}, null), but the JSX everyone else is using has that equivalent to JSX(input.search, {}, null). I’m not certain if your JSX syntax is supposed to be able to be used with React code or anything else that uses JSX syntax, but if yes then it’ll be broken in a significant number of cases so that it’s worse than useless, and if no, well, it’s going to be misleading, and what if JSX did get merged into ECMAScript in some form? Then you’d be incompatible with ECMAScript again.
Same deal with hyphens in unquoted object literal keys: it’s not part of ECMAScript now, but just because it’d be a syntax error now doesn’t mean it always will be. Decorators in TypeScript are a good example of things going badly wrong even when an extremely popular project is involved.
I say: if you want to go JavaScript, go JavaScript, maaaaaybe plus standard JSX conforming with <https://facebook.github.io/jsx/>, and no further. Even if what you do is obviously superior, &c. &c. I’d apply the same reasoning on your fork of CSS: you introduced it for a good reason back then, but now it’s just friction, even if it’s a little better in a vacuum (and maybe it is in parts, maybe it isn’t in other parts).
-
Do you think HTML is a programming language
Then it might be time for a pull request which identifies these parts as JSX.
daisyui
-
HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
DaisyUI offers zero-JS components
https://daisyui.com/
I used it for a small form + search result list recently and it works well enough for simple / static stuff.
But I think I'll still be reaching for a JS lib first since I'd miss things like inputs-with-autocomplete too much.
- Show HN: Open Source TailwindCSS UI Components
-
How to use Tailwind with any CSS framework
Tailwind is great, but creating everything from scratch is annoying. A nice base of components which can be extended with tailwind would be great. There are a few tailwind frameworks like Flowbite, Daisy Ui, but I like Bulma, PicoCSS and Bootstrap.
- Ask HN: Freelance website builders/maintainers, what's in your 2024 toolkit?
-
Building a Fast, Efficient Web App: The Technology Stack of PromptSmithy Explained
While I have experience with Tailwind and frontend development, I don’t really have the patience to use it. I usually end up using something like Mantine, which is a complete component library UI kit, or Daisy UI, which is a component library built on top of Tailwind. Shadcn/ui is quite similar to Daisy in this sense, but being able to customize the individual components, since they get installed to your components folder, made development more streamlined and more customizable. On top of that being able to change my components style with natural language thanks to v0 made development super easy and fast. Shadcn may be too minimalist of a style for some, but thanks to all the components being local, you can customize them quickly and easily!
-
The Bulma CSS framework reaches 1.0
https://daisyui.com is a really great middle ground—you can move as fast as you would in Bulma, then drop down into the weeds with TW if you need it.
-
Tailwind Color Palette Generator
If you're looking for grab and go components, Daisy UI or Flowbite might be more your speed, I've used both with minimal headache.
https://daisyui.com/
-
DaisyUI + Alpine.js + Codehooks.io - the simple web app trio
This guide is tailored for front-end developers looking to explore the smooth integration of DaisyUI's stylish components, Alpine.js's minimalist reactive framework, and the straightforward back-end capabilities of Codehooks.io.
- DaisyUI: The most popular component library for Tailwind CSS
-
Shadcn: Beautifully designed components that you can copy-paste into your apps
Others:
- https://daisyui.com/
What are some alternatives?
htm - Hyperscript Tagged Markup: JSX alternative using standard tagged templates, with compiler support.
flowbite - Open-source UI component library and front-end development framework based on Tailwind CSS
React - The library for web and native user interfaces.
headlessui - Completely unstyled, fully accessible UI components, designed to integrate beautifully with Tailwind CSS.
joystick - A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.
shadcn/ui - Beautifully designed components that you can copy and paste into your apps. Accessible. Customizable. Open Source.
denoflare - Develop, test, and deploy Cloudflare Workers with Deno.
Material UI - Ready-to-use foundational React components, free forever. It includes Material UI, which implements Google's Material Design.
prepack - A JavaScript bundle optimizer.
theme-change - Change CSS theme with toggle, buttons or select using CSS custom properties and localStorage
vite - Next generation frontend tooling. It's fast!
fullcalendar - Full-sized drag & drop event calendar in JavaScript