template

A simple framework for webapps

Explore on GitHub Read Hacker News discussions

2Distinct people

4Mentions

0Explicit recommenders

483GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

A simple framework for webapps

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month4 dated mentions

Observed mentions: 2023-03-16 21:20:51 UTC to 2023-11-27 17:54:37 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Mar 2023	2023-03-01 00:00:00 UTC	2023-04-01 00:00:00 UTC	2	1	1
Apr 2023	2023-04-01 00:00:00 UTC	2023-05-01 00:00:00 UTC	0	0	0
May 2023	2023-05-01 00:00:00 UTC	2023-06-01 00:00:00 UTC	1	0	1
Jun 2023	2023-06-01 00:00:00 UTC	2023-07-01 00:00:00 UTC	0	0	0
Jul 2023	2023-07-01 00:00:00 UTC	2023-08-01 00:00:00 UTC	0	0	0
Aug 2023	2023-08-01 00:00:00 UTC	2023-09-01 00:00:00 UTC	0	0	0
Sep 2023	2023-09-01 00:00:00 UTC	2023-10-01 00:00:00 UTC	0	0	0
Oct 2023	2023-10-01 00:00:00 UTC	2023-11-01 00:00:00 UTC	0	0	0
Nov 2023	2023-11-01 00:00:00 UTC	2023-12-01 00:00:00 UTC	1	0	1

What Hacker News says

4 sources

r3trohack3r·Nov 27, 2023

For folks looking for a lightweight JS class that manages the lifecycle of Web Components, I have this little Template class I use in many of my front-end projects. It's able to manage the application state by pushing the state down through the application and bubbling changes up. It's a 161-line file that's easy to reason about and modify as needed. https://github.com/retrohacker/template

In Web Components Eliminate JavaScript Framework Lock-In

r3trohack3r·May 26, 2023

I’ve been using <template> to avoid the whole “create DOM elements in JS” thing, and it’s been working well so far. I wrote a little wrapper class to help with it: https://github.com/retrohacker/template

In That people produce HTML with string templates is telling us something

stefankuehnel·Mar 17, 2023Submission

Template – A simple framework for webapps

81 points · Open discussion

r3trohack3r·Mar 16, 2023

This is exactly what I'm doing with my personal "framework" I use for client contracts. It's just Web Components with a handy class based wrapper. I call it Template, since it's based off <template> tags. It's a joy to work in, feels "frameworky" but it's just web standards with <100 lines of convenience JS wrapped around it. There is no magic beyond what the browser provides - I like it that way. https://github.com/retrohacker/template/ It's "open source" as a reference. Just using it for myself. There aren't many docs beyond notes to myself. But the actual framework is a 90LoC JavaScript file that is an easy read. You're welcome to kick the tires. If you like it I'd entertain PRs and stuff but it's such a small library forking is probably entirely reasonable to make your own flavor too. The general idea is you extend the Template base c

Read the rest

lass and call "super" with the id of the <template> that will get bound to the ShadowDOM when the class is mounted. Then you call instance.mount and pass a dom node to mount it into the DOM. For child nodes, you use `this.fragment.querySelector` to select them from the <template> you mounted. It supports garbage collection by tracking children, so when you "unmount" it recursively unmounts all child instances as well. Finally it has an event emitter implementation, so changes/actions/events bubble up the DOM while state can push down through the DOM. Keeps things clean. I recently added state methods since I was duplicating state management everywhere. Now the base template class has a `setState` that will emit a single `change` event for all changes in the current "tick" of the browser eval loop. Cheers and happy hacking!

In Introducing react.dev