Open timgluz opened 10 years ago
mootools-more
is not suitable for distribution via bower as its intended as a modular / customisable build repository.
the reality is, hardly anyone ever uses the whole lot. there is no dist
folder and no pre-made builds shipped with the repo, just raw sources, which would be pretty useless in raw format as dropped by bower.
we can either do a dist/
with all mootools-more
modules and declare that as the main, adding all else to ignore
- or we can just unregister the repo completely. if anyone is using bower
to do their custom -more
builds, they can post here/complain of breakage.
on a side note, what is versioneye's affiliation with bower.io?
Hey, maintainer(s) of mootools/mootools-more!
We at VersionEye are working hard to keep up the quality of the bower's registry.
We just finished our initial analysis of the quality of the Bower.io registry:
7530 - registered packages, 224 of them doesnt exists anymore;
We analysed 7306 existing packages and 1070 of them don't have bower.json on the master branch ( that's where a Bower client pulls a data ).
Sadly, your library
mootools/mootools-more
is one of them.Can you spare 15 minutes to help us to make Bower better?
Just add a new file
bower.json
and change attributes.Read more about bower.json on the official spefication and nodejs semver library has great examples of proper versioning.
NB! Please validate your bower.json with jsonlint before commiting your updates.
Thank you!
Timo, twitter: @versioneye email: timo@versioneye.com VersionEye - no more legacy software!