{
    "name": "angular-slider",
    "version": "0.3.2",
    "main": "./build/angular-slider.js",
    "ignore": [
        "**/.*",
        "node_modules",
        "components",
        "lib",
        "src",
        "test",
		".g*",
		".editorconfig",
		".jshintrc",
		".travis.yml",
		"Gruntfile.js",
		"karma.conf.js",
		"*.html"
    ],
    "dependencies": {
        "angular": "~1.2.*",
		"angular-touch": "~1.2.*"
    },
    "devDependencies": {
        "angular-mocks": "*",
		"angular-scenario": "*"
    },
	"resolutions": {
		"angular": "v1.2.16"
	}
}

{
    "name": "angular-slider",
    "version": "0.3.2",
    "main": "./build/angular-slider.js",
    "ignore": [
        "**/.*",
        "node_modules",
        "components",
        "lib",
        "src",
        "test",
		".g*",
		".editorconfig",
		".jshintrc",
		".travis.yml",
		"Gruntfile.js",
		"karma.conf.js",
		"*.html"
    ],
    "dependencies": {
        "angular": "~1.2",
        "angular-touch": "~1.2"
    },
    "devDependencies": {
        "angular-mocks": "*",
		"angular-scenario": "*"
    },
	"resolutions": {
		"angular": "v1.2.16"
	}
}

Use correct semver range to avoid resolution errors.
Use correct semver range to avoid resolution errors.

Prior to this change, this package would resolve its dependencies as the latest version of `angular` and `angular-touch` causing bower resolution errors when installing it, rather than being content with any `1.2` release, which I think is what you meant.

More information here: https://www.npmjs.org/package/semver#ranges
