HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Wildhoney
Maple.js
JavaScript2015–2015
Wildhoney / Maple.js

Maple.js

Maple.js is a React webcomponents based framework mixing ES6 with Custom Elements, HTML Imports and Shadow DOM. It has in-built support for SASS and JSX, including a Gulp task for vulcanizing your project.

3Distinct people
3Mentions
0Explicit recommenders
429GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Maple.js is a React webcomponents based framework mixing ES6 with Custom Elements, HTML Imports and Shadow DOM. It has in-built support for SASS and JSX, including a Gulp task for vulcanizing your project.

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, 3:56:07 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 week3 dated mentions

Observed mentions: 2015-05-15 13:24:46 UTC to 2015-08-05 14:59:16 UTC. Weeks start Monday, UTC.

012015-05-11 00:00:00 UTC to 2015-05-18 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 112015-05-18 00:00:00 UTC to 2015-05-25 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2015-05-25 00:00:00 UTC to 2015-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-01 00:00:00 UTC to 2015-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-08 00:00:00 UTC to 2015-06-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-15 00:00:00 UTC to 2015-06-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-22 00:00:00 UTC to 2015-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 222015-06-29 00:00:00 UTC to 2015-07-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-06 00:00:00 UTC to 2015-07-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-13 00:00:00 UTC to 2015-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-20 00:00:00 UTC to 2015-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-27 00:00:00 UTC to 2015-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-03 00:00:00 UTC to 2015-08-10 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 3

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
May 112015-05-11 00:00:00 UTC2015-05-18 00:00:00 UTC110
May 182015-05-18 00:00:00 UTC2015-05-25 00:00:00 UTC110
May 252015-05-25 00:00:00 UTC2015-06-01 00:00:00 UTC000
Jun 12015-06-01 00:00:00 UTC2015-06-08 00:00:00 UTC000
Jun 82015-06-08 00:00:00 UTC2015-06-15 00:00:00 UTC000
Jun 152015-06-15 00:00:00 UTC2015-06-22 00:00:00 UTC000
Jun 222015-06-22 00:00:00 UTC2015-06-29 00:00:00 UTC000
Jun 292015-06-29 00:00:00 UTC2015-07-06 00:00:00 UTC000
Jul 62015-07-06 00:00:00 UTC2015-07-13 00:00:00 UTC000
Jul 132015-07-13 00:00:00 UTC2015-07-20 00:00:00 UTC000
Jul 202015-07-20 00:00:00 UTC2015-07-27 00:00:00 UTC000
Jul 272015-07-27 00:00:00 UTC2015-08-03 00:00:00 UTC000
Aug 32015-08-03 00:00:00 UTC2015-08-10 00:00:00 UTC101

What Hacker News says

3 sources
I like this answer, however, its still not sufficient. Because you dont want to mix the "structure" of your UI with the behaviour of it. But in very dynamic apps behaviour = structure. So in that case React makes sense. However, i dove into web components with Polymer, and it seems that this is the "official" direction of components in the future web... It also doesnt try to mix HTML with JavaScript. In fact in the future there will be more langauges than javascript since there will be a bytecode for the browser. Having your app written in React poses a real problem when you want to switch your logic to a different programming language. So isnt the Web Components solution much better? It seems that React and Web Components can be combined: https://github.com/Wildhoney/Maple.js
In React Static Site

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.