solid-site
htm
Our great sponsors
solid-site | htm | |
---|---|---|
66 | 42 | |
156 | 8,551 | |
2.6% | - | |
8.4 | 0.0 | |
14 days ago | 3 months ago | |
TypeScript | JavaScript | |
- | Apache 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.
solid-site
-
Learn how to install SolidJS with Flowbite and Tailwind CSS
SolidJS is a popular and open-source declarative JavaScript library that empowers reactive UI interfaces for the web that ensures a performant benchmark, leverages the flexibility of JSX and also provides support for TypeScript, Astro, and Vite.
- Porting my old dynamic form render from React to SolidJS
-
Question: Where does Nuxt 3 fit in, in 2023?
In 2023 there are a wealth of developer options for front-end: React, Vue, Svelte, Solid and many more.
-
Using Solid Start with GitHub pages
You may or may not yet have heard about Solid Start, which is the much anticipated upcoming meta framework for Solid.js currently being in beta.
-
Invoking Solid.js components from your Ember apps
SolidJS is a powerful, pragmatic and productive JavaScript library for building user interfaces with simple and performant reactivity. It stands on the shoulders of giants, particularly React and Knockout. If you've developed with React Functional Components and Hooks before, Solid will feel very natural because it follows the same philosophy as React, with unidirectional data flow, read/write segregation, and immutable interfaces.
-
Reactivity Without Virtual DOM
Things like Solid (https://www.solidjs.com/) also have no virtual DOM, and the improves are in higher ceiling for performance, lower memory usage, simpler DX (components are not re-executed, there aren't any dependency arrays everywhere), easy high performance (no useRef this and useRef that to make things fast, no useCallback, no React.memo, these things are just obsolete).
-
I also build my portfolio with Tailwind (links and details in coments)
Made with: - Windblade (my own version of Tailwind) - Solid JS - Vite
-
Using ES6 Proxy for Cross-cut Concerns - A Real-world Example
SolidJS
-
Separation of concerns slows you down
For the time being, this is how I approach web development on pretty much every project I have “architectural control” over. That’s how I worked with Solid.js and Tailwind CSS for the past 2 years. That’s how Vrite is being built. Has worked pretty well so far…
-
What I want for 2023
SolidJS (They've started building the SolidStart and I want to give it a try)
htm
-
VanJS: A 0.9KB JavaScript UI framework
The preact team also dislikes transpiling jsx so they've developed an alternative using tagged template literals: https://github.com/developit/htm
-
React SSR web-server from scratch
So getting this to work without bundler magic is very hard. It's not surprising why NextJS is investing in a bundler. Though one thing that really sticks out is how much complexity we add for just miniscule dev ergonomics. Not using JSX and using something like htm would make all this easier (removing the bundler entirely), it's a lot of overhead to avoid a couple of quotes. React should really have a tagged-template mode. Also all of this is indirection is actually bad for dev ergonomics too! One of the reasons I did this is because I'm absolutely sick of magic caches and sorting through code that's been crushed by a bundler into something I don't recognize and can't easily debug. While we can't get rid of this completely (ts/jsx) this preserves the module import graph completely on the client-side making it easy to find things as you are working and preserving line numbers. This obviously is not useful for a production build and there's a lot of work that would need to go in to support both modes over the same code, but it's depressing no tools really work like this for local development.
-
HTML Web Components
You can also do JSX and skip the build step with preact + htm : https://github.com/developit/htm#example
-
Service Worker Templating Language (SWTL)
While I was able to achieve this fairly easily, the developer experience of manually stitching strings together wasnt great. Being myself a fan of buildless libraries, such as htm and lit-html, I figured I'd try to take a stab at implementing a DSL for component-like templating in Service Workers myself, called Service Worker Templating Language (SWTL), here's what it looks like:
-
Gaseous - Yet Another Games Manager
I would however highly recommend https://github.com/developit/htm
-
Create and Hydrate HTML with HTM
I thought the same thing, but apparently "HTM" is a JSX like javascript string template representation of HTML, and it can be found here: https://github.com/developit/htm
-
Anyone using React from just a CDN, barbarian style?
If you're going to do a no-build approach, assume modern JS (so you don't have to transpile the JS syntax). Also, you can use https://github.com/developit/htm as a nearly-identical equivalent to JSX syntax, also without transpiling.
-
Simple Modern JavaScript Using JavaScript Modules and Import Maps
This seems like a case of caring way too much about something that's hardly very different. JSX versus tagged template strings can be incredibly similar to one another.
The examples in this article are using vanilla template strings to author raw html, but that only misses a couple of nicities JSX has. There are tagged template string libraries like htm[1] that do include some of the few nicities JSX has, but which are actually compatible with the official language.
-
A few programming language features I’d like to see
The first one exists in JavaScript and is called Tagged Template Literals. I agree with the author that its a nice feature. It's the perfect construct to use for prepared SQL statements, LINQ-style queries, or reimplementing a JSX-like syntax (see HTM https://github.com/developit/htm).
-
Using React without JSX == no build
There is however a library that is closer to JSX (HTML-like feel) but yet does not require a build step. htm. HTM uses tagged templates to leverage template literal as native Javascript template strings. If you have not played with tagged templates, I encourage you to check this out, it's a quite powerful feature, that has recently become a part of Javascript.
What are some alternatives?
Ionic Framework - A powerful cross-platform UI toolkit for building native-quality iOS, Android, and Progressive Web Apps with HTML, CSS, and JavaScript.
jsx - The JSX specification is a XML-like syntax extension to ECMAScript.
purescript-halogen - A declarative, type-safe UI library for PureScript.
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.
esbuild-plugin-alias - esbuild plugin for path aliases
reagent - A minimalistic ClojureScript interface to React.js
babel-plugin-react-html-attrs - Babel plugin which transforms HTML and SVG attributes on JSX host elements into React-compatible attributes
solid-start - SolidStart, the Solid app framework
vim-jsx-pretty - :flashlight: [Vim script] JSX and TSX syntax pretty highlighting for vim.
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
lit - Lit is a simple library for building fast, lightweight web components.