component.github.io is component dead?

Sep 12 '16 06:09 thisconnect

I'm using components of component to make website and new components from npm everyday, but I think the website and command line tool of component is dead, webpack and npm are better choice IMO.

Sep 12 '16 07:09 chemzqm

thanks. I like the small repos on (https://github.com/component).

http://component.github.io/ is confusing. seems to be different libraries than what is on github.com/component

Sep 12 '16 07:09 thisconnect

// Update

Just using the word component is ambiguous!

Component, the package manager and build tool, located under the componentjs organization is deprecated, see here: https://github.com/componentjs/component/blob/master/Readme.md or here https://github.com/componentjs/component/issues/639

All the repos within the component organization are kind of the official components.

http://component.github.io provides a registry and everyone can add his library to this registry, like npm. You just need a component.json in your project root and then you can publish it this way

Sep 12 '16 07:09 timaschew

Ty for the quick reply. So componentjs is DEPRECATED. The repos on https://github.com/component have recent commits.

What is your opinion on official components?

Sep 12 '16 08:09 thisconnect

I'm still maintaining a few of the "official components", but only for usage in npm. This said, I strongly encourage you to use webpack or browserify rather than component.

Sep 12 '16 16:09 stephenmathieson

Yes For building I use rollup for es6 and sometimes use webpack or broserify. I find the official components small focused and cute. So I wondered if you use them. Should they be rewritten to es2015 one day?

Sep 13 '16 07:09 thisconnect

Should they be rewritten to es2015 one day?

probably not, as component doesn't support clever lifecycle hooks like npm's prepublish.. plus they work fine as es5 currently ;)

Sep 15 '16 20:09 stephenmathieson