htm
stencil
Our great sponsors
htm | stencil | |
---|---|---|
42 | 55 | |
8,551 | 12,280 | |
- | 0.7% | |
0.0 | 9.9 | |
3 months ago | 4 days ago | |
JavaScript | TypeScript | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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.
stencil
- Ajout de l'auto-complétion sur les Web Components avec Stencil
-
Making Web Component properties behave closer to the platform
First a disclosure: I never actually used Stencil, only played with it a bit locally in a hello-world project while writing this post.
-
Plasmic.app – the visual builder for your tech stack
This is my main concern too.
I don't understand why tools like this "pick a winner" with a specific framework instead of rendering to Web Components with a framework wrapper, or using something like Stencil[1] that can render to any framework.
-
Design Systems with Web Components
I was recently able to sit down with some of the core members of Ionic, who also created Stencil a toolchain for building Design Systems and Progressive Web Apps. We talked at great length how typically companies are approaching Ionic from a Design Team and need help building components. As a developer I wanted to talk about the Web Components that are used within the Design System first. There was a decent amount of surprise, so I thought I would break down what a Design System is and why it doesn't matter which end you start with, as long as you have both your Design and Development teams working together to build your Design System.
- Nue: A React/Vue/Vite/Astro Alternative
-
If Web Components are so great, why am I not using them?
Examples like this bug me. The React example is using a high level abstraction, the web component is directly using the API. A more accurate example would show how those React calls eventually boil down to document.createElement()
I don’t think the Web Components API was meant to be used directly all the time. You can use a framework like StencilJS:
- Use Stencil / the ionic framework with emberjs [video]
-
World Wide Web Wars
You might say that this is the same vicious cycle as JavaScript frameworks. That's wrong, because Web Components are interoperable by design. Choosing Stencil or Lit or any other library is a development convenience that has little to do with the interoperability of the resulting components.
-
React Component in vue/angular
Not sure about Vue but you can in Angular, though my experience with React components in Angular has not been pleasant. Libraries such as Stencil allow you to create native Web Componets from React components.
-
Is there a plugin that abstracts registering web components with React?
I guess my problem is more specific to my overall architecture. I have components that when are placed in the DOM, have props rendered on them by their parent elements. I'm using stencil to do this.
What are some alternatives?
jsx - The JSX specification is a XML-like syntax extension to ECMAScript.
lit - Lit is a simple library for building fast, lightweight web components.
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
Svelte - Cybernetically enhanced web apps
esbuild-plugin-alias - esbuild plugin for path aliases
vite-ssg - Static site generation for Vue 3 on Vite
babel-plugin-react-html-attrs - Babel plugin which transforms HTML and SVG attributes on JSX host elements into React-compatible attributes
css-modules - Documentation about css-modules
vim-jsx-pretty - :flashlight: [Vim script] JSX and TSX syntax pretty highlighting for vim.
catalyst - Catalyst is a set of patterns and techniques for developing components within a complex application.
shoelace-css - A collection of professionally designed, every day UI components built on Web standards. SHOELACE IS BECOMING WEB AWESOME. WE ARE LIVE ON KICKSTARTER! 👇👇👇