Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[enhancement] Add missing bower.json. #1219

Open
timgluz opened this issue Jan 7, 2014 · 1 comment
Open

[enhancement] Add missing bower.json. #1219

timgluz opened this issue Jan 7, 2014 · 1 comment

Comments

@timgluz
Copy link

timgluz commented Jan 7, 2014

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.

{
  "name": "mootools/mootools-more",
  "version": "1.0.0",
  "main": "path/to/main.css",
  "description": "please add it",
  "license": "Eclipse",
  "ignore": [
    ".jshintrc",
    "**/*.txt"
  ],
  "dependencies": {
    "<dependency_name>": "<semantic_version>",
    "<dependency_name>": "<Local_folder>",
    "<dependency_name>": "<package>"
  },
  "devDependencies": {
    "<test-framework-name>": "<version>"
  }
}

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: [email protected]
VersionEye - no more legacy software!

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1372517-enhancement-add-missing-bower-json?utm_campaign=plugin&utm_content=tracker%2F22069&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F22069&utm_medium=issues&utm_source=github).
@DimitarChristoff
Copy link
Member

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants