Bump editions from 1.3.3 to 2.2.0

Bumps editions from 1.3.3 to 2.2.0.

Changelog

*Sourced from [editions's changelog](https://github.com/bevry/editions/blob/master/HISTORY.md).* > ## v2.2.0 2019 September 11 > > - Removed the `browser` edition introduced in v2.0.1 as the Editions Autloader has no use in the web browser > - Updated dependencies > > ## v2.1.3 2018 December 29 > > - Updated `errlop` dependency, should function to fix [issue [#2](https://github-redirect.dependabot.com/bevry/editions/issues/2)](https://github-redirect.dependabot.com/bevry/errlop/issues/2) > > ## v2.1.2 2018 December 29 > > Iternal change of not assuming the error `code` property exists, as on certain node versions its existance is denied. This should fix the following error: > > ``` > ./node_modules/editions/edition-node-0.8/index.js:310 > if (editionError.code.indexOf('unsupported-edition-engines-node-version') === 0) { > ^ > > TypeError: Cannot read property 'indexOf' of undefined > ``` > > ## v2.1.1 2018 December 29 > > Internal change of requiring a specific [Errlop](https://github.com/bevry/errlop) edition, which should function as a workaround for [errlop#2](https://github-redirect.dependabot.com/bevry/errlop/issues/2) to fix the following error: > > ``` > ./node_modules/errlop/index.js:4 > module.exports = require('editions').requirePackage(__dirname, require) > ^ > > TypeError: require(...).requirePackage is not a function > ``` > > ## v2.1.0 2018 November 15 > > - If none of the editions for a package match the current node version, editions will try to find a compatible package by converting strict version ranges likes `4 || 6 || 8 || 10` to looser ones like `>=4`, and if that fails, then it will attempt to load the last edition for the environment. > - This brings editions handling of engines closer in line with how node handles it, which is as a warning/recomendation, rather than a requirement/enforcement. > - This has the benefit that edition authors can specify ranges as the specific versions that they have tested the edition against that pass, rather than having to omit that information for runtime compatibility. > - As such editions will now automatically select the edition with guaranteed support for the environment, and if there are none with guaranteed support, then editions will select the one is most likely supported, and if there are none that are likely supported, then it will try the last edition, which should be the most compatible edition. > - This is timely, as node v11 is now the version most developers use, yet if edition authors specified only LTS releases, then the editions autoloader would reject loading on v11, despite compatibility being likely with the most upper edition. > - This behaviour is dictated by the new `strict` option, which omission of a value enables the above behaviour. > - Change `syntaxes` to `tags`, with backwards compatibility. This applies to edition specifications, as well as for the blacklist environment variable which is now named `EDITIONS_TAG_BLACKLIST`. > - Added codes to the different types of errors we may produce. > - Upgraded babel from v6 to v7 > - Documentation has swapped from Documentation.js to JSDoc with the Minami theme. > > ## v2.0.2 2018 September 3 > > - Fixed `Error: Cannot find module 'editions'` on Windows (caused by edition directories containing `:` which is unsupported on Windows) > - Regression in v2.0.0 > ... (truncated)

Commits

- [`2c6d8f0`](https://github.com/bevry/editions/commit/2c6d8f0789d163b2768493be11f015862366e4bc) v1.2.0 - changelog and version bump - [`b27ec03`](https://github.com/bevry/editions/commit/b27ec033bf9bf39648f87c9a1b13f073a2e395a0) updated base files and editions using boundation - [`10ddeda`](https://github.com/bevry/editions/commit/10ddedac04fae1ca26258f34355ecce8dfe1a9d8) Bump mixin-deep from 1.3.1 to 1.3.2 ([#31](https://github-redirect.dependabot.com/bevry/editions/issues/31)) - [`3c75e4b`](https://github.com/bevry/editions/commit/3c75e4b6d2e7aa4089725e363cd0145ccb4b39a9) Bump eslint-utils from 1.3.1 to 1.4.2 ([#30](https://github-redirect.dependabot.com/bevry/editions/issues/30)) - [`585d505`](https://github.com/bevry/editions/commit/585d50544036e1b0b198df01c2302cd756b12b0e) Bump fstream from 1.0.11 to 1.0.12 ([#28](https://github-redirect.dependabot.com/bevry/editions/issues/28)) - [`008b3ba`](https://github.com/bevry/editions/commit/008b3ba210c65ce2837b7a3f550a6082f6eb6fed) Bump js-yaml from 3.12.0 to 3.13.1 ([#29](https://github-redirect.dependabot.com/bevry/editions/issues/29)) - [`599abdf`](https://github.com/bevry/editions/commit/599abdfb4bbff494dc2649326e388bc2b3a8dbdf) history: fix date for v2.1.3 - [`8598d5e`](https://github.com/bevry/editions/commit/8598d5eb28703daf4715299f660af2ca5cd23229) v2.1.3 - manually updated errlop dependency version - [`84f5363`](https://github.com/bevry/editions/commit/84f536320f7eff6385e867d9f5c1de0dfb92fa88) v2.1.2 - don’t assume editionError.code exists - [`f4d648c`](https://github.com/bevry/editions/commit/f4d648c4eaa46dda47a9ca62d490366076601826) v2.1.1 - changelog and version bump - Additional commits viewable in [compare view](https://github.com/bevry/editions/compare/v1.3.3...v2.2.0)

Maintainer changes

This version was pushed to npm by [bevryme](https://www.npmjs.com/~bevryme), a new releaser for editions since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

bevry / cson

Bump editions from 1.3.3 to 2.2.0 #97