@basemaps/lambda-tiler 6.40.0 → 6.43.0

package/dist/node_modules/mkdirp-classic/package.json

@@ -1,18 +0,0 @@
-{
-  "name": "mkdirp-classic",
-  "version": "0.5.3",
-  "description": "Mirror of mkdirp 0.5.2",
-  "main": "index.js",
-  "dependencies": {},
-  "devDependencies": {},
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/mafintosh/mkdirp-classic.git"
-  },
-  "author": "Mathias Buus (@mafintosh)",
-  "license": "MIT",
-  "bugs": {
-    "url": "https://github.com/mafintosh/mkdirp-classic/issues"
-  },
-  "homepage": "https://github.com/mafintosh/mkdirp-classic"
-}

package/dist/node_modules/napi-build-utils/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2018 inspiredware
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/dist/node_modules/napi-build-utils/README.md

@@ -1,48 +0,0 @@
-# napi-build-utils
-
-[![npm](https://img.shields.io/npm/v/napi-build-utils.svg)](https://www.npmjs.com/package/napi-build-utils)
-![Node version](https://img.shields.io/node/v/prebuild.svg)
-[![Build Status](https://travis-ci.org/inspiredware/napi-build-utils.svg?branch=master)](https://travis-ci.org/inspiredware/napi-build-utils) 
-[![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg)](http://standardjs.com/) 
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) 
-
-A set of utilities to assist developers of tools that build [N-API](https://nodejs.org/api/n-api.html#n_api_n_api) native add-ons.
-
-## Background
-
-This module is targeted to developers creating tools that build N-API native add-ons. 
-
-It implements a set of functions that aid in determining the N-API version supported by the currently running Node instance and the set of N-API versions against which the N-API native add-on is designed to be built. Other functions determine whether a particular N-API version can be built and can issue console warnings for unsupported N-API versions. 
-
-Unlike the modules this code is designed to facilitate building, this module is written entirely in JavaScript. 
-
-## Quick start
-
-```bash
-$ npm install napi-build-utils
-```
-
-The module exports a set of functions documented [here](./index.md). For example:
-
-```javascript
-var napiBuildUtils = require('napi-build-utils');
-var napiVersion = napiBuildUtils.getNapiVersion(); // N-API version supported by Node, or undefined.
-```
-
-## Declaring supported N-API versions
-
-Native modules that are designed to work with [N-API](https://nodejs.org/api/n-api.html#n_api_n_api) must explicitly declare the N-API version(s) against which they are coded to build. This is accomplished by including a `binary.napi_versions` property in the module's `package.json` file. For example:
-
-```json
-"binary": {
-  "napi_versions": [2,3]
-}
-``` 
-
-In the absence of a need to compile against a specific N-API version, the value `3` is a good choice as this is the N-API version that was supported when N-API left experimental status. 
-
-Modules that are built against a specific N-API version will continue to operate indefinitely, even as later versions of N-API are introduced. 
-
-## Support
-
-If you run into problems or limitations, please file an issue and we'll take a look. Pull requests are also welcome.  

package/dist/node_modules/napi-build-utils/index.js

@@ -1,213 +0,0 @@
-'use strict'
-// Copyright (c) 2018 inspiredware
-
-var path = require('path')
-var pkg = require(path.resolve('package.json'))
-
-var versionArray = process.version
-  .substr(1)
-  .replace(/-.*$/, '')
-  .split('.')
-  .map(function (item) {
-    return +item
-  })
-
-/**
- *
- * A set of utilities to assist developers of tools that build
- * [N-API](https://nodejs.org/api/n-api.html#n_api_n_api) native add-ons.
- *
- * The main repository can be found
- * [here](https://github.com/inspiredware/napi-build-utils#napi-build-utils).
- *
- * @module napi-build-utils
- */
-
-/**
- * Implements a consistent name of `napi` for N-API runtimes.
- *
- * @param {string} runtime The runtime string.
- * @returns {boolean}
- */
-exports.isNapiRuntime = function (runtime) {
-  return runtime === 'napi'
-}
-
-/**
- * Determines whether the specified N-API version is supported
- * by both the currently running Node instance and the package.
- *
- * @param {string} napiVersion The N-API version to check.
- * @returns {boolean}
- */
-exports.isSupportedVersion = function (napiVersion) {
-  var version = parseInt(napiVersion, 10)
-  return version <= exports.getNapiVersion() && exports.packageSupportsVersion(version)
-}
-
-/**
- * Determines whether the specified N-API version is supported by the package.
- * The N-API version must be preseent in the `package.json`
- * `binary.napi_versions` array.
- *
- * @param {number} napiVersion The N-API version to check.
- * @returns {boolean}
- * @private
- */
-exports.packageSupportsVersion = function (napiVersion) {
-  if (pkg.binary && pkg.binary.napi_versions &&
-      pkg.binary.napi_versions instanceof Array) {
-    for (var i = 0; i < pkg.binary.napi_versions.length; i++) {
-      if (pkg.binary.napi_versions[i] === napiVersion) return true
-    };
-  };
-  return false
-}
-
-/**
- * Issues a warning to the supplied log if the N-API version is not supported
- * by the current Node instance or if the N-API version is not supported
- * by the package.
- *
- * @param {string} napiVersion The N-API version to check.
- * @param {Object} log The log object to which the warnings are to be issued.
- * Must implement the `warn` method.
- */
-exports.logUnsupportedVersion = function (napiVersion, log) {
-  if (!exports.isSupportedVersion(napiVersion)) {
-    if (exports.packageSupportsVersion(napiVersion)) {
-      log.warn('This Node instance does not support N-API version ' + napiVersion)
-    } else {
-      log.warn('This package does not support N-API version ' + napiVersion)
-    }
-  }
-}
-
-/**
- * Issues warnings to the supplied log for those N-API versions not supported
- * by the N-API runtime or the package.
- *
- * Note that this function is specific to the
- * [`prebuild`](https://github.com/prebuild/prebuild#prebuild) package.
- *
- * `target` is the list of targets to be built and is determined in one of
- * three ways from the command line arguments:
- * (1) `--target` specifies a specific target to build.
- * (2) `--all` specifies all N-API versions supported by the package.
- * (3) Neither of these specifies to build the single "best version available."
- *
- * `prebuild` is an array of objects in the form `{runtime: 'napi', target: '2'}`.
- * The array contains the list of N-API versions that are supported by both the
- * package being built and the currently running Node instance.
- *
- * The objective of this function is to issue a warning for those items that appear
- * in the `target` argument but not in the `prebuild` argument.
- * If a specific target is supported by the package (`packageSupportsVersion`) but
- * but note in `prebuild`, the assumption is that the target is not supported by
- * Node.
- *
- * @param {(Array<string>|string)} target The N-API version(s) to check. Target is
- * @param {Array<Object>} prebuild A config object created by the `prebuild` package.
- * @param {Object} log The log object to which the warnings are to be issued.
- * Must implement the `warn` method.
- * @private
- */
-exports.logMissingNapiVersions = function (target, prebuild, log) {
-  if (exports.getNapiBuildVersions()) {
-    var targets = [].concat(target)
-    targets.forEach(function (napiVersion) {
-      if (!prebuildExists(prebuild, napiVersion)) {
-        if (exports.packageSupportsVersion(parseInt(napiVersion, 10))) {
-          log.warn('This Node instance does not support N-API version ' + napiVersion)
-        } else {
-          log.warn('This package does not support N-API version ' + napiVersion)
-        }
-      }
-    })
-  } else {
-    log.error('Builds with runtime \'napi\' require a binary.napi_versions ' +
-              'property on the package.json file')
-  }
-}
-
-/**
- * Determines whether the specified N-API version exists in the prebuild
- * configuration object.
- *
- * Note that this function is speicifc to the `prebuild` and `prebuild-install`
- * packages.
- *
- * @param {Object} prebuild A config object created by the `prebuild` package.
- * @param {string} napiVersion The N-APi version to be checked.
- * @return {boolean}
- * @private
- */
-var prebuildExists = function (prebuild, napiVersion) {
-  if (prebuild) {
-    for (var i = 0; i < prebuild.length; i++) {
-      if (prebuild[i].target === napiVersion) return true
-    }
-  }
-  return false
-}
-
-/**
- * Returns the best N-API version to build given the highest N-API
- * version supported by the current Node instance and the N-API versions
- * supported by the package, or undefined if a suitable N-API version
- * cannot be determined.
- *
- * The best build version is the greatest N-API version supported by
- * the package that is less than or equal to the highest N-API version
- * supported by the current Node instance.
- *
- * @returns {number|undefined}
- */
-exports.getBestNapiBuildVersion = function () {
-  var bestNapiBuildVersion = 0
-  var napiBuildVersions = exports.getNapiBuildVersions(pkg)
-  if (napiBuildVersions) {
-    var ourNapiVersion = exports.getNapiVersion()
-    napiBuildVersions.forEach(function (napiBuildVersion) {
-      if (napiBuildVersion > bestNapiBuildVersion &&
-        napiBuildVersion <= ourNapiVersion) {
-        bestNapiBuildVersion = napiBuildVersion
-      }
-    })
-  }
-  return bestNapiBuildVersion === 0 ? undefined : bestNapiBuildVersion
-}
-
-/**
- * Returns an array of N-API versions supported by the package.
- *
- * @returns {Array<string>}
- */
-exports.getNapiBuildVersions = function () {
-  var napiBuildVersions = []
-  // remove duplicates, convert to text
-  if (pkg.binary && pkg.binary.napi_versions) {
-    pkg.binary.napi_versions.forEach(function (napiVersion) {
-      var duplicated = napiBuildVersions.indexOf('' + napiVersion) !== -1
-      if (!duplicated) {
-        napiBuildVersions.push('' + napiVersion)
-      }
-    })
-  }
-  return napiBuildVersions.length ? napiBuildVersions : undefined
-}
-
-/**
- * Returns the highest N-API version supported by the current node instance
- * or undefined if N-API is not supported.
- *
- * @returns {string|undefined}
- */
-exports.getNapiVersion = function () {
-  var version = process.versions.napi // string, can be undefined
-  if (!version) { // this code should never need to be updated
-    if (versionArray[0] === 9 && versionArray[1] >= 3) version = '2' // 9.3.0+
-    else if (versionArray[0] === 8) version = '1' // 8.0.0+
-  }
-  return version
-}

package/dist/node_modules/napi-build-utils/index.md

@@ -1,81 +0,0 @@
-<a name="module_napi-build-utils"></a>
-
-## napi-build-utils
-A set of utilities to assist developers of tools that build
-[N-API](https://nodejs.org/api/n-api.html#n_api_n_api) native add-ons.
-
-The main repository can be found
-[here](https://github.com/inspiredware/napi-build-utils#napi-build-utils).
-
-
-* [napi-build-utils](#module_napi-build-utils)
-    * [.isNapiRuntime(runtime)](#module_napi-build-utils.isNapiRuntime) ⇒ <code>boolean</code>
-    * [.isSupportedVersion(napiVersion)](#module_napi-build-utils.isSupportedVersion) ⇒ <code>boolean</code>
-    * [.logUnsupportedVersion(napiVersion, log)](#module_napi-build-utils.logUnsupportedVersion)
-    * [.getBestNapiBuildVersion()](#module_napi-build-utils.getBestNapiBuildVersion) ⇒ <code>number</code> \| <code>undefined</code>
-    * [.getNapiBuildVersions()](#module_napi-build-utils.getNapiBuildVersions) ⇒ <code>Array.&lt;string&gt;</code>
-    * [.getNapiVersion()](#module_napi-build-utils.getNapiVersion) ⇒ <code>string</code> \| <code>undefined</code>
-
-<a name="module_napi-build-utils.isNapiRuntime"></a>
-
-### napi-build-utils.isNapiRuntime(runtime) ⇒ <code>boolean</code>
-Implements a consistent name of `napi` for N-API runtimes.
-
-**Kind**: static method of [<code>napi-build-utils</code>](#module_napi-build-utils)  
-
-| Param | Type | Description |
-| --- | --- | --- |
-| runtime | <code>string</code> | The runtime string. |
-
-<a name="module_napi-build-utils.isSupportedVersion"></a>
-
-### napi-build-utils.isSupportedVersion(napiVersion) ⇒ <code>boolean</code>
-Determines whether the specified N-API version is supported
-by both the currently running Node instance and the package.
-
-**Kind**: static method of [<code>napi-build-utils</code>](#module_napi-build-utils)  
-
-| Param | Type | Description |
-| --- | --- | --- |
-| napiVersion | <code>string</code> | The N-API version to check. |
-
-<a name="module_napi-build-utils.logUnsupportedVersion"></a>
-
-### napi-build-utils.logUnsupportedVersion(napiVersion, log)
-Issues a warning to the supplied log if the N-API version is not supported
-by the current Node instance or if the N-API version is not supported
-by the package.
-
-**Kind**: static method of [<code>napi-build-utils</code>](#module_napi-build-utils)  
-
-| Param | Type | Description |
-| --- | --- | --- |
-| napiVersion | <code>string</code> | The N-API version to check. |
-| log | <code>Object</code> | The log object to which the warnings are to be issued. Must implement the `warn` method. |
-
-<a name="module_napi-build-utils.getBestNapiBuildVersion"></a>
-
-### napi-build-utils.getBestNapiBuildVersion() ⇒ <code>number</code> \| <code>undefined</code>
-Returns the best N-API version to build given the highest N-API
-version supported by the current Node instance and the N-API versions
-supported by the package, or undefined if a suitable N-API version
-cannot be determined.
-
-The best build version is the greatest N-API version supported by
-the package that is less than or equal to the highest N-API version
-supported by the current Node instance.
-
-**Kind**: static method of [<code>napi-build-utils</code>](#module_napi-build-utils)  
-<a name="module_napi-build-utils.getNapiBuildVersions"></a>
-
-### napi-build-utils.getNapiBuildVersions() ⇒ <code>Array.&lt;string&gt;</code>
-Returns an array of N-API versions supported by the package.
-
-**Kind**: static method of [<code>napi-build-utils</code>](#module_napi-build-utils)  
-<a name="module_napi-build-utils.getNapiVersion"></a>
-
-### napi-build-utils.getNapiVersion() ⇒ <code>string</code> \| <code>undefined</code>
-Returns the highest N-API version supported by the current node instance
-or undefined if N-API is not supported.
-
-**Kind**: static method of [<code>napi-build-utils</code>](#module_napi-build-utils)  

package/dist/node_modules/napi-build-utils/package.json

@@ -1,41 +0,0 @@
-{
-  "name": "napi-build-utils",
-  "version": "1.0.2",
-  "description": "A set of utilities to assist developers of tools that build N-API native add-ons",
-  "main": "index.js",
-  "scripts": {
-    "doc": "jsdoc2md index.js >index.md",
-    "test": "mocha test/ && npm run lint",
-    "lint": "standard",
-    "prepublishOnly": "npm run test && npm run doc"
-  },
-  "keywords": [
-    "n-api",
-    "prebuild",
-    "prebuild-install"
-  ],
-  "author": "Jim Schlight",
-  "license": "MIT",
-  "homepage": "https://github.com/inspiredware/napi-build-utils#readme",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/inspiredware/napi-build-utils.git"
-  },
-  "bugs": {
-    "url": "https://github.com/inspiredware/napi-build-utils/issues"
-  },
-  "devDependencies": {
-    "chai": "^4.1.2",
-    "jsdoc-to-markdown": "^4.0.1",
-    "mocha": "^5.2.0",
-    "standard": "^12.0.1"
-  },
-  "binary": {
-    "note": "napi-build-tools is not an N-API module. This entry is for unit testing.",
-    "napi_versions": [
-      2,
-      2,
-      3
-    ]
-  }
-}

package/dist/node_modules/node-abi/.circleci/config.yml

@@ -1,45 +0,0 @@
-step-restore-cache: &step-restore-cache
-  restore_cache:
-    keys:
-      - v1-dependencies-{{ arch }}-{{ checksum "yarn.lock" }}
-      - v1-dependencies-{{ arch }}
-
-steps-test: &steps-test
-  steps:
-    - checkout
-    - *step-restore-cache
-    - run: yarn --frozen-lockfile
-    - save_cache:
-        paths:
-          - node_modules
-        key: v1-dependencies-{{ arch }}-{{ checksum "yarn.lock" }}
-    - run: yarn test
-
-version: 2.1
-orbs:
-  cfa: continuousauth/npm@1.0.2
-jobs:
-  test-linux-14:
-    docker:
-      - image: cimg/node:14.21
-    <<: *steps-test
-  test-linux-16:
-    docker:
-      - image: cimg/node:16.19
-    <<: *steps-test
-
-workflows:
-  test_and_release:
-    # Run test jobs first, release only when all the test jobs are successful
-    jobs:
-      - test-linux-14
-      - test-linux-16
-      - cfa/release:
-          requires:
-            - test-linux-14
-            - test-linux-16
-          filters:
-            branches:
-              only:
-                - main
-          context: cfa-release

package/dist/node_modules/node-abi/.github/CODEOWNERS

@@ -1 +0,0 @@
-* @electron/wg-ecosystem @electron/wg-releases @electron/wg-upgrades

package/dist/node_modules/node-abi/.github/workflows/update-abi.yml

@@ -1,42 +0,0 @@
-name: Auto-update ABI JSON file
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: '0 * * * *'
-jobs:
-  autoupdate:
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c  # tag: v3.3.0
-    - uses: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c  # tag: v3.6.0
-      with:
-        node-version: '12.x'
-    - name: Get npm cache directory
-      id: npm-cache
-      run: |
-        echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
-    - uses: actions/cache@627f0f41f6904a5b1efbaed9f96d9eb58e92e920  # tag: v3.2.4
-      with:
-        path: ${{ steps.npm-cache.outputs.dir }}
-        key: ${{ runner.os }}-node-${{ hashFiles('**/package.json') }}
-        restore-keys: |
-          ${{ runner.os }}-node-
-    - run: npm install --no-package-lock
-    - name: Update ABI registry
-      run: npm run update-abi-registry
-    - name: Commit Changes to ABI registry
-      env:
-        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      run: |
-        echo "machine github.com login $GITHUB_ACTOR password $GITHUB_TOKEN" > ~/.netrc
-        chmod 600 ~/.netrc
-        git add abi_registry.json
-        if test -n "$(git status -s)"; then
-          git config user.name "GitHub Actions"
-          git config user.email "github-actions@users.noreply.github.com"
-          git diff --cached
-          git commit -m "feat: update ABI registry"
-          git push origin HEAD:$GITHUB_REF
-        else
-          echo No update needed
-        fi

package/dist/node_modules/node-abi/.releaserc.json

@@ -1,9 +0,0 @@
-{
-    "plugins": [
-      "@semantic-release/commit-analyzer",
-      "@semantic-release/release-notes-generator",
-      "@continuous-auth/semantic-release-npm",
-      "@semantic-release/github"
-    ],
-    "branches": [ "main" ]
-  }

package/dist/node_modules/node-abi/CODE_OF_CONDUCT.md

@@ -1,73 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at lukas.geiger94@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct/
-
-[homepage]: https://www.contributor-covenant.org

package/dist/node_modules/node-abi/CONTRIBUTING.md

@@ -1,62 +0,0 @@
-# Contributing to `node-abi`
-
-:+1::tada: First off, thanks for taking the time to contribute to `node-abi`! :tada::+1:
-
-## Commit Message Guidelines
-
-This module uses [`semantic-release`](https://github.com/semantic-release/semantic-release) to automatically release new versions via [Continuous Auth](https://continuousauth.dev/).
-Therefor we have very precise rules over how our git commit messages can be formatted.
-
-Each commit message consists of a **header**, a **body** and a **footer**.  The header has a special
-format that includes a **type**, a **scope** and a **subject** ([full explanation](https://github.com/stevemao/conventional-changelog-angular/blob/master/convention.md)):
-
-```
-<type>(<scope>): <subject>
-<BLANK LINE>
-<body>
-<BLANK LINE>
-<footer>
-```
-
-### Type
-
-Must be one of the following:
-
-- **feat**: A new feature. **Will trigger a new release**
-- **fix**: A bug fix or a addition to one of the target arrays. **Will trigger a new release**
-- **docs**: Documentation only changes
-- **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
-- **refactor**: A code change that neither fixes a bug nor adds a feature
-- **perf**: A code change that improves performance
-- **test**: Adding missing or correcting existing tests
-- **chore**: Changes to the build process or auxiliary tools and libraries such as documentation generation
-
-
-### Patch Release
-
-```
-fix(electron): Support Electron 1.8.0
-```
-
-### ~~Minor~~ Feature Release
-
-```
-feat: add .getTarget(abi, runtime)
-```
-
-### ~~Major~~ Breaking Release
-
-```
-feat: Add amazing new feature
-
-BREAKING CHANGE: This removes support for Node 0.10 and 0.12.
-```
-
-## Pull request guidelines
-
-Here are some things to keep in mind as you file pull requests to fix bugs, add new features, etc.:
-
-- CircleCI is used to make sure that the project builds packages as expected on the supported platforms, using supported Node.js versions.
-- Unless it's impractical, please write tests for your changes. This will help us so that we can spot regressions much easier.
-- Squashing commits during discussion of the pull request is almost always unnecessary, and makes it more difficult for both the submitters and reviewers to understand what changed in between comments. However, rebasing is encouraged when practical, particularly when there's a merge conflict.
-- If you are continuing the work of another person's PR and need to rebase/squash, please retain the attribution of the original author(s) and continue the work in subsequent commits.