Maybe transfer the repo to @components

[sammousa]

Maybe transfer the repo to @components

[SamMousa]

Sounds great; I have no interest in being the maintainer anyway =D

How do we proceed with that?

[rogeriopradoj]

I think you should open a Issue in official central repo, https://github.com/components/components/issues/, make a link to this issue here, and wait for what the organization @components say. (There is a few other requests there, as you can see).

They will probably ask to include support for bower and other package/component managers. I think I could help you with some, and the community as well because the visibility will increase, right?

Just saying, I'm not related with them, just an enthusiast who wants to see the project get better, ok?

See ya!

[holtkamp]

What is the status of this? Both Composer and Packagist.org are suggesting to use (non existing) bower-asset/datatables instead of this components/datatables package, why would that be?

https://packagist.org/packages/components/datatables

[SamMousa]

Yes, I have deprecated this package.
Checkout https://github.com/francoispluchino/composer-asset-plugin

This is a plugin that allows you to use bower and npm assets.
These are package managers for javascript.

The advantage of this approach is that there is no need for a composer.json in javascript libraries. Most javascript libraries have a bower.json for bower or package.json for npm.

When you have installed composer-asset-plugin composer will be able to find bower-asset/*** packages.

[holtkamp]

Thanks for the swift response, seems an elegant solution indeed.

It might be useful to include that pointer to your README.MD ;)

[SamMousa]

Done!