announce "this project is not maintained anymore"

[timaschew]

@componentjs/owners I think it's obvious that component is not maintained anymore. We should put a note in the readme of this repo, not just because it's not maintained, but also component has several issues:

• endpoint only for GitHub and BitBucket
  • rate limit, even if you use an auth token example
• maintain an extra file: component.json
  • need to fork a module when it doesn’t exist
• plugins can only be used via the API
• annoying to update remote dependencies in all locals example
• it’s not maintained anymore, see contributors

@jonathanong wrote a post after he rewrote component: http://www.jongleberry.com/the-future-of-component.html After nearly a year he wrote this: http://www.jongleberry.com/the-story-of-normalize.html

In particular, the more I learn about Webpack, the more amazed I am and its features, especially hot reloading.

We're using component at our company and realize in the last week a drop-in replacement for webpack, it's working fine. The biggest work was to fix all the component repositories where a package.json was configured wrong or didn't exist.

[clintwood]

@timaschew, first off thank you for all your amazing work on componentjs!

In the early days component was amazing but for myself the writing on the wall with respect to it's future was when key people began talk of webcomponents and es6 modules. To that end I have looked to other 'component' packaging, bundling and development mechanisms including jspm, webpack, Polymer as well as switched to es6 for iojs/node side stuff using babel, esperanto and rollup. To be honest it's been a time consuming switch but necessary to stay in the game! Thanks!

[pirxpilot]

Thanks @timaschew and thanks to everyone who made component possible. Probably stating the obvious here: many components (as opposed to the component builder and tools) are probably still used in the wild. I'll keep an eye on a few I am still using. Let's wind it down gently.

[AaronNGray]

Is this just component or the whole of componentjs ?

On 22 June 2015 at 01:48, Damian Krzeminski notifications@github.com wrote:

Thanks @timaschew https://github.com/timaschew and thanks to everyone who made component possible. Probably stating the obvious here: many components (as opposed to the component builder and tools) are probably still used in the wild. I'll keep an eye on a few I am still using. Let's wind it down gently.

— Reply to this email directly or view it on GitHub https://github.com/componentjs/component/issues/639#issuecomment-113974402 .

[vendethiel]

well, the individual components should still work fine, so long they have a bower.json / package.json / something else to be used

[AaronNGray]

So ComponentJS itself is being scrapped ?

On 22 June 2015 at 21:05, ven notifications@github.com wrote:

well, the individual components should still work fine, so long they have a bower.json / package.json / something else to be used

— Reply to this email directly or view it on GitHub https://github.com/componentjs/component/issues/639#issuecomment-114242032 .

[timaschew]

Of course component and its modules (component-builder, component-resolver, component-remotes ,..) - actually everything in the componentjs organisation - will still available on npm and on GitHub, but the development will stop for new features and bugfixes.

And of course all the components like commponent-dom and domify, everything in the component organisation will still work, as long the modules have a component.json file. They even work for other tools like browserify, webpack and jspm if they provide a package.json

[darsain]

Seeing as component is being deprecated, but component spec is still used by duo, webpack, and maybe others, wouldn't it be a good idea to use component.io for description of a spec (similar to json.org), along with component discovery? That way other tools like the ones mentioned would be able to just point to this to specify how to create & find components.

And component discovery could use some upgrade. Instead of relying on one huge wiki page that none really edits, search and list all github repos with component.json in the root. Is this doable?

[netpoetica]

@timaschew Thanks for all your hard work on component amigo. I agree with you that it is the right time for this announcement. I have not had my hands in every nearly as many modules of componentjs as you have and I certainly don't think I would be capable of maintaining this project - especially to the quality it has been maintained by you - without you.

I am still open to being pinged for Bitbucket remote-related issues if they are business-/originzation-crucial, but I do not think this portion of component has been heavily utilized.

Let me know if there is anything you need from me. It's been fun working on the small slices of component that I've had a chance to be involved in - hopefully one day we'll run into each other at a conference!

Cheers, Keith