api/package.json

{
  "name": "pelias-api",
  "version": "0.0.0-development",
  "author": "pelias",
  "description": "Pelias API",
  "homepage": "https://github.com/pelias/api",
  "license": "MIT",
  "main": "index.js",
  "bin": "./bin/start",
  "scripts": {
    "ciao": "node node_modules/ciao/bin/ciao -c test/ciao.json test/ciao",
    "coverage": "node_modules/.bin/istanbul cover test/unit/run.js",
    "docs": "./bin/generate-docs",
    "lint": "jshint .",
    "start": "./bin/start",
    "test": "npm run unit",
    "travis": "npm test",
    "unit": "./bin/units",
    "validate": "npm ls",
    "config": "node -e \"console.log(JSON.stringify(require( 'pelias-config' ).generate(require('./schema')), null, 2))\"",
    "prune": "npm prune"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/pelias/api.git"
  },
  "keywords": [
    "pelias",
    "elasticsearch",
    "webview"
  ],
  "bugs": {
    "url": "https://github.com/pelias/api/issues"
  },
  "engines": {
    "node": ">=6.0.0"
  },
  "dependencies": {
    "@mapbox/geojson-extent": "^0.3.1",
    "addressit": "1.5.0",
    "async": "^2.0.0",
    "check-types": "^7.0.0",
    "elasticsearch": "^15.0.0",
    "elasticsearch-exceptions": "0.0.4",
    "express": "^4.8.8",
    "geojson": "^0.5.0",
    "geolib": "^2.0.18",
    "iso-639-3": "^1.0.0",
    "joi": "^14.0.0",
    "locale": "^0.1.0",
    "lodash": "^4.17.4",
    "markdown": "^0.5.0",
    "morgan": "^1.8.2",
    "pelias-categories": "^1.2.0",
    "pelias-config": "^3.0.2",
    "pelias-labels": "^1.8.0",
    "pelias-logger": "^1.2.0",
    "pelias-microservice-wrapper": "^1.7.0",
    "pelias-model": "^5.5.2",
    "pelias-query": "^9.1.1",
    "pelias-sorting": "^1.2.0",
    "predicates": "^2.0.0",
    "retry": "^0.12.0",
    "stable": "^0.1.8",
    "stats-lite": "^2.0.4",
    "through2": "^2.0.3"
  },
  "devDependencies": {
    "ciao": "^1.0.0",
    "difflet": "^1.0.1",
    "istanbul": "^0.4.2",
    "jshint": "^2.5.6",
    "pelias-mock-logger": "^1.3.0",
    "precommit-hook": "^3.0.0",
    "proxyquire": "^2.0.0",
    "source-map": "^0.7.0",
    "tap-dot": "^2.0.0",
    "tape": "^4.5.1",
    "tmp": "^0.0.33"
  },
  "pre-commit": [
    "lint",
    "prune",
    "validate",
    "test"
  ],
  "release": {
    "branch": "master",
    "success": []
  }
}
initial commit 10 years ago			`{`
			`"name": "pelias-api",`
Change default NPM package name 7 years ago			`"version": "0.0.0-development",`
Remove other instances of Mapzen 7 years ago			`"author": "pelias",`
initial commit 10 years ago			`"description": "Pelias API",`
			`"homepage": "https://github.com/pelias/api",`
			`"license": "MIT",`
			`"main": "index.js",`
Use pelias-api as executable name 6 years ago			`"bin": "./bin/start",`
initial commit 10 years ago			`"scripts": {`
add security audit scripts 10 years ago			`"ciao": "node node_modules/ciao/bin/ciao -c test/ciao.json test/ciao",`
Change query to use `terms` and add code coverage stats 10 years ago			`"coverage": "node_modules/.bin/istanbul cover test/unit/run.js",`
Add precommit-hook sections to package.json 9 years ago			`"docs": "./bin/generate-docs",`
			`"lint": "jshint .",`
Avoid NPM when starting Dockerfile 7 years ago			`"start": "./bin/start",`
Alphabetize npm scripts 9 years ago			`"test": "npm run unit",`
Remove npm-check 7 years ago			`"travis": "npm test",`
Alphabetize npm scripts 9 years ago			`"unit": "./bin/units",`
feat: set up semantic-release 9 years ago			`"validate": "npm ls",`
add dependency check to pre-commit and travis 8 years ago			`"config": "node -e \"console.log(JSON.stringify(require( 'pelias-config' ).generate(require('./schema')), null, 2))\"",`
added prune target to pre-commit to avoid npm weirdness 7 years ago			`"prune": "npm prune"`
initial commit 10 years ago			`},`
			`"repository": {`
			`"type": "git",`
feat: set up semantic-release 9 years ago			`"url": "https://github.com/pelias/api.git"`
initial commit 10 years ago			`},`
			`"keywords": [`
			`"pelias",`
			`"elasticsearch",`
			`"webview"`
			`],`
			`"bugs": {`
			`"url": "https://github.com/pelias/api/issues"`
			`},`
			`"engines": {`
Increase Node.js requirement to 6.0.0 or higher 7 years ago			`"node": ">=6.0.0"`
initial commit 10 years ago			`},`
			`"dependencies": {`
package: bump config version 7 years ago			`"@mapbox/geojson-extent": "^0.3.1",`
fix(package): update addressit to version 1.5.0 https://greenkeeper.io/ 8 years ago			`"addressit": "1.5.0",`
chore(package): update async to version 2.0.0 https://greenkeeper.io/ 9 years ago			`"async": "^2.0.0",`
chore(package): update check-types to version 7.0.0 https://greenkeeper.io/ 9 years ago			`"check-types": "^7.0.0",`
fix(package): update elasticsearch to version 15.0.0 7 years ago			`"elasticsearch": "^15.0.0",`
improve error matching by using string prefix matching on known elasticsearch exception names 9 years ago			`"elasticsearch-exceptions": "0.0.4",`
current dev branch 10 years ago			`"express": "^4.8.8",`
fix(package): update geojson to version 0.5.0 7 years ago			`"geojson": "^0.5.0",`
Compute distance for each result of reverse query 9 years ago			`"geolib": "^2.0.18",`
negotiate HTTP locales for incoming browser requests 8 years ago			`"iso-639-3": "^1.0.0",`
fix(package): update joi to version 14.0.0 6 years ago			`"joi": "^14.0.0",`
negotiate HTTP locales for incoming browser requests 8 years ago			`"locale": "^0.1.0",`
bumped lodash version to latest 8 years ago			`"lodash": "^4.17.4",`
Use carat ranges for all Pelias Dependencies The overhead of having to merge a Greenkeeper PR for every single change to every single repository (which leads to cascading PRs), is too much. Connects https://github.com/pelias/pelias/issues/366 7 years ago			`"markdown": "^0.5.0",`
Add carat to morgan version 8 years ago			`"morgan": "^1.8.2",`
Use carat ranges for all Pelias Dependencies The overhead of having to merge a Greenkeeper PR for every single change to every single repository (which leads to cascading PRs), is too much. Connects https://github.com/pelias/pelias/issues/366 7 years ago			`"pelias-categories": "^1.2.0",`
			`"pelias-config": "^3.0.2",`
			`"pelias-labels": "^1.8.0",`
fix(package): update pelias-logger to version 1.2.0 Closes #1189 6 years ago			`"pelias-logger": "^1.2.0",`
Require microservice-wrapper version with response time 6 years ago			`"pelias-microservice-wrapper": "^1.7.0",`
Use carat ranges for all Pelias Dependencies The overhead of having to merge a Greenkeeper PR for every single change to every single repository (which leads to cascading PRs), is too much. Connects https://github.com/pelias/pelias/issues/366 7 years ago			`"pelias-model": "^5.5.2",`
			`"pelias-query": "^9.1.1",`
			`"pelias-sorting": "^1.2.0",`
fix(package): update predicates to version 2.0.0 7 years ago			`"predicates": "^2.0.0",`
fix(package): update retry to version 0.12.0 7 years ago			`"retry": "^0.12.0",`
fix(interpolation): Ensure proper sorting of streets with interpolated addresses In cases where several conditions are met, it is possible for results to be returned from the API that are not sorted as they were intended. These conditions are: * over 10 results total were returned from Elasticsearch * the interpolation middleware was called * not all street results end up with possible interpolated address matches, and some of those streets come before other interpolated address records, necessitating a re-sorting of the results in the interpolation middleware In these cases, the ordering of streets as defined by Elasticsearch, such as by linguistic match or distance from a focus point, will no longer be respected in the results. This is because Node.js's `Array.prototype.sort` uses an [unstable QuickSort for arrays of size 11 or greater](https://github.com/nodejs/node/blob/master/deps/v8/src/js/array.js#L670). The solution is to switch to a sorting algorithm that is always stable. This ensures that whatever ordering was specified in the Elasticsearch queries is observed, without any of that logic having to be duplicated, and then possibly conflict. Stable sorting is provided by the [stable](http://npmjs.com/stable) NPM package. 7 years ago			`"stable": "^0.1.8",`
Use carat version for stats-lite dependency 8 years ago			`"stats-lite": "^2.0.4",`
Use caret range for through2 8 years ago			`"through2": "^2.0.3"`
add unit test suite 10 years ago			`},`
			`"devDependencies": {`
update dev dep: ciao 8 years ago			`"ciao": "^1.0.0",`
add common.diff() function for test debugging 9 years ago			`"difflet": "^1.0.1",`
chore(package): update dependencies http://greenkeeper.io/ 9 years ago			`"istanbul": "^0.4.2",`
adding jshintignore and jshintrc, pre commit hook js lint 10 years ago			`"jshint": "^2.5.6",`
Use carat ranges for all Pelias Dependencies The overhead of having to merge a Greenkeeper PR for every single change to every single repository (which leads to cascading PRs), is too much. Connects https://github.com/pelias/pelias/issues/366 7 years ago			`"pelias-mock-logger": "^1.3.0",`
chore(package): update dependencies http://greenkeeper.io/ 9 years ago			`"precommit-hook": "^3.0.0",`
chore(package): update proxyquire to version 2.0.0 7 years ago			`"proxyquire": "^2.0.0",`
chore(package): update source-map to version 0.7.0 7 years ago			`"source-map": "^0.7.0",`
chore(package): update tap-dot to version 2.0.0 7 years ago			`"tap-dot": "^2.0.0",`
fix: Explicitly depend on packages' optional dependencies [istanbul](https://www.npmjs.com/package/istanbul) and [escodegen](https://www.npmjs.com/package/escodegen) have optional dependencies, which for some reason `npm ls` in npm version 3 fails to handle properly. We don't need these packages, but installing them does little harm so it seems to be the best way to make our precommit-hook scripts pass for all users. 9 years ago			`"tape": "^4.5.1",`
feat(deps): Remove uglify devDependency As I recall, this was only added to mitigate issues with running `npm ls` and correctly showing all dependencies installed (see https://github.com/pelias/api/issues/1179). 6 years ago			`"tmp": "^0.0.33"`
Add precommit-hook sections to package.json 9 years ago			`},`
			`"pre-commit": [`
			`"lint",`
added prune target to pre-commit to avoid npm weirdness 7 years ago			`"prune",`
Add precommit-hook sections to package.json 9 years ago			`"validate",`
Remove npm-check 7 years ago			`"test"`
Run semantic-relase on the production branch This change will make semantic-release run only on the `production` branch. This means only merges to production will create new NPM packages, GitHub releases, git tags, and `:latest` Docker images on Docker hub. Connects https://github.com/pelias/pelias/issues/721 7 years ago			`],`
			`"release": {`
chore(release): Run releases off master branch Connects https://github.com/pelias/pelias/issues/749 6 years ago			`"branch": "master",`
Disable semantic-release success actions The default is to comment on every issue which made it into the release. Possibly convenient, definitely spammy. See https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/plugins.md#success-plugin and https://github.com/semantic-release/github 7 years ago			`"success": []`
Run semantic-relase on the production branch This change will make semantic-release run only on the `production` branch. This means only merges to production will create new NPM packages, GitHub releases, git tags, and `:latest` Docker images on Docker hub. Connects https://github.com/pelias/pelias/issues/721 7 years ago			`}`
chore(package): update dependencies http://greenkeeper.io/ 9 years ago			`}`