HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pzavolinsky
elmx
JavaScript2016–2019
pzavolinsky / elmx

elmx

A tiny precompiler that takes an Elm program with embedded HTML and desugars the HTML into elm-html syntax. Elmx is to Elm what React's JSX is to Javascript

6Distinct people
6Mentions
0Explicit recommenders
358GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A tiny precompiler that takes an Elm program with embedded HTML and desugars the HTML into elm-html syntax. Elmx is to Elm what React's JSX is to Javascript

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:01:57 AM 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 year6 dated mentions

Observed mentions: 2016-06-13 19:55:45 UTC to 2019-04-17 04:44:47 UTC.

01232016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019

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.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC312
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

What Hacker News says

1 sources
You interpreted hackability = ability for you to spend your time hacking on it. But I think they were going for hackability = other people will be more likely to develop plugins. The lower barrier to entry is basically one of the major upsides of Atom/VSCode: their plugins tend to have cutting edge support. For example, iirc Atom was the first to have a good plugin for Elm lang (elm-jitsu). Meanwhile the Elm plugin for Jetbrains' IntelliJ came later as the result of the effort of two Microsoft employees spending billable time on the somewhat academic project. A better example is that the creator of elmx ("JSX for Elm") was able to create an Atom plugin for their basically experimental library: https://github.com/pzavolinsky/elmx#atom-integration I also think this differs from "hackability" when used with Vim/Emacs which does mean "you wil
Read the rest
l be hacking together your .*rc file" which is definitely not how I'd characterize VSCode/Atom.
In Panic’s Next Editor

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.