Backend: Django 1.7, Postgres, ElasticSearch, Redis.
Running on hetzner root servers in germany.
Frontend: component (https://github.com/componentjs/component) with a lot of custom components, no frameworks.
Using https://codeship.io/ for continuos integration/delivery
Stefan (ChatGrape)
In Intelligent chat that makes your team communication twice as fastcomponentjs
component
JavaScript2012–2016
componentjs / component · Archived
component
frontend package manager and build tool for modular web applications
19Distinct people
29Mentions
1Explicit recommenders
4.5KGitHub stars
What to know before exploring
What it is
frontend package manager and build tool for modular web applications
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
That's why I like the component (http://github.com/component/component) approach; keeping things to such a minimum feature wise that you can understand very easily what each…
hunvreus used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
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, 6:01:08 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 year29 dated mentions
Observed mentions: 2012-09-10 04:14:26 UTC to 2016-03-16 18:23:51 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
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 16 | 0 | 16 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
THIS PROJECT IS DEPRECATED
Component is not maintained anymore. See here #639 for more information.
You can still use the component registry on component.github.io to search for components.
All the components are not affected, because most of them also provide a package.json file.
The component.json files in these components are still kept to provide backwards compatibility for component and duo.
What now?
Consider to use another tool, which rely on the npm and the package.json standard:
webpack
jspm (supports npm and github endpoint)
browserify
Component is a vertically integrated frontend solution, handling everything from package management to the build process, handling everything including HTML, JS, CSS, images, and fonts. Think of it as an opinionated npm + browserify + rework-npm + grunt/gulp/broccoli all wrapped into component build.
Want to know more about Component? Visit the guide or view the comparison with other solutions.
If you're confused about component, components, componentjs, please read disambiguation
Component 1.0.0: Several
major new features have been added, some have been removed, and the project has been greatly reorganized. You may need to upgrade your
version of node and/or npm to avoid breakage. Please see the detailed changelog. Component 0.x will not be maintained anymore.
Installation
First, you need node v0.10+ installed. If you do not have it installed, visit node's download page.
With node installed, run the following command:
$ npm install -g component
Getting Started
Read this Getting Started guide to get a basic static site running very quickly with Component.
Note: the Component repo (this repo) has only documentation for Component 0.19. All of the documentation related to 1.0.0 will be handled in the guide repo.
Team
The team and organization have undergone massive changes. In summary, jonathanong stopped developing Component and started with normalize.io and the guys from segmentio switched to using duo. Component will still be maintained and updated while it is in use. You can read more about Duo.js and Component here.
The long story of Component and the changes that occurred in component can be found in Jonathan Ong's blog post "the future of component".
Development for component (maintenance and features) will be continued at the latest when latest browsers will support the ES6 modules and Web Components natively.
Contributors
Anton Wilhelm/@timaschew - maintainer
Keith Rosenberg/@netpoetica - maintainer
Trevor Gerhardt/@trevorgerhardt - maintainer
Clinton Wood - maintainer
Jason Kurht/@jasonkuhrt - maintainer
visionmedia/@tjholowaychuk - original author
jonathanong/@jongleberry - second-gen author
segmentio/segment.io - original sponsor
Read the full README on GitHubWhat Hacker News says
5 sourcesWe've actually stopped using all pre-processor for everything we do for Segment.io[1] as well, and we're not beginners.
One of the biggest problems with them is that you immediately eliminate a huge portion of the people who are willing to contribute to your code if you select a pre-processor they aren't fond of. It's fine for app internals, but for sharing small[2] open-source[3] components[4] it's not a good idea—whether it's Sass or CoffeeScript or Jade or whatever.
The other problem with CSS pre-processors specifically is that they only work well with the monolithic app mindset. All of your CSS files inside the same `styles` folder, and all of them required by the "top of the monolith" `main.sass` file. Instead, using something like component[5] you get true dependency trees, so you don't have to go monolithic anymore. And trying to g
Read the rest
et Sass to work across a component-ized codebase is a real pain. Instead we use Myth[6] to "post-process" the built CSS.
Pre-processors are a leaky abstraction that comes back to bite you at random points the way all leaky abstractions do, and the ways are usually hard to foresee and thus hard to argue against when the benefits seems so clear.
[1]: https://segment.io
[2]: https://github.com/segmentio/toggle
[3]: https://github.com/segmentio/sheet
[4]: https://github.com/component/tip
[5]: https://github.com/component/component
[6]: http://myth.io
[Component](https://github.com/component/component). That is all.
In You might not need jQueryWow, Pace just blew my mind. You guys are releasing some really awesome stuff :) random other thing is would be sweet if these were component[1] friendly. (Dunno if you've already checked out component, but it is insanely good for front-end work.)
One pattern I picked up from reading TJ's code is the transparent constructor...
odometer(el).value(42);
...which I like using to make things that share a bit of state, but are still one-offs, a bit terser. (Coupled with avoiding options objects in general.) Achieved with the following:
function Odometer (el) {
if (!(this instanceof Odometer)) return new Odometer(el);
...
}
[1] https://github.com/component/component
In CountUp.jsExactly. If this kind of thing seems like your cup of tea check out component[1].
[1]: https://github.com/component/component
In Frameworkless JavaScript