[enhancement] Add missing bower.json.

[timgluz]

Hey, maintainer(s) of akv2/MaxImage!

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 akv2/MaxImage 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": "akv2/MaxImage",
  "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: timo@versioneye.com VersionEye - no more legacy software!

[simonbengtsson]

This would be great indeed!

[pparavicini]

I was able to download from bower using '*' as the version number. When attempting to add the current version, I get the error message: 'No tag found that was able to satisfy 2.0.8'.

Going forward, it would be good practice to tag your releases in github with the proper version number, as this ensures that developers can rely on a given version being immutable. It's also easy to do, so why not!