Index: trip-planner-front/node_modules/yargs-parser/README.md
===================================================================
--- trip-planner-front/node_modules/yargs-parser/README.md	(revision 6a3a178323fd905112b5392bd9d3cb83b66ef2d3)
+++ trip-planner-front/node_modules/yargs-parser/README.md	(revision e29cc2ea91f8c99a4329f6d20188305dfd752279)
@@ -1,8 +1,9 @@
 # yargs-parser
 
-![ci](https://github.com/yargs/yargs-parser/workflows/ci/badge.svg)
+[![Build Status](https://travis-ci.org/yargs/yargs-parser.svg)](https://travis-ci.org/yargs/yargs-parser)
+[![Coverage Status](https://coveralls.io/repos/yargs/yargs-parser/badge.svg?branch=)](https://coveralls.io/r/yargs/yargs-parser?branch=master)
 [![NPM version](https://img.shields.io/npm/v/yargs-parser.svg)](https://www.npmjs.com/package/yargs-parser)
-[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
-![nycrc config on GitHub](https://img.shields.io/nycrc/yargs/yargs-parser)
+[![Standard Version](https://img.shields.io/badge/release-standard%20version-brightgreen.svg)](https://github.com/conventional-changelog/standard-version)
+
 
 The mighty option parser used by [yargs](https://github.com/yargs/yargs).
@@ -10,5 +11,5 @@
 visit the [yargs website](http://yargs.js.org/) for more examples, and thorough usage instructions.
 
-<img width="250" src="https://raw.githubusercontent.com/yargs/yargs-parser/main/yargs-logo.png">
+<img width="250" src="https://raw.githubusercontent.com/yargs/yargs-parser/master/yargs-logo.png">
 
 ## Example
@@ -19,10 +20,10 @@
 
 ```js
-const argv = require('yargs-parser')(process.argv.slice(2))
+var argv = require('yargs-parser')(process.argv.slice(2))
 console.log(argv)
 ```
 
-```console
-$ node example.js --foo=33 --bar hello
+```sh
+node example.js --foo=33 --bar hello
 { _: [], foo: 33, bar: 'hello' }
 ```
@@ -31,9 +32,9 @@
 
 ```js
-const argv = require('yargs-parser')('--foo=99 --bar=33')
+var argv = require('./')('--foo=99 --bar=33')
 console.log(argv)
 ```
 
-```console
+```sh
 { _: [], foo: 99, bar: 33 }
 ```
@@ -42,56 +43,12 @@
 
 ```js
-const parse = require('yargs-parser')
+var parse = require('yargs-parser')
 parse(['-f', 11, '--zoom', 55].join(' '))   // <-- array to string
 parse(['-f', 11, '--zoom', 55].map(String)) // <-- array of strings
 ```
 
-## Deno Example
-
-As of `v19` `yargs-parser` supports [Deno](https://github.com/denoland/deno):
-
-```typescript
-import parser from "https://deno.land/x/yargs_parser/deno.ts";
-
-const argv = parser('--foo=99 --bar=9987930', {
-  string: ['bar']
-})
-console.log(argv)
-```
-
-## ESM Example
-
-As of `v19` `yargs-parser` supports ESM (_both in Node.js and in the browser_):
-
-**Node.js:**
-
-```js
-import parser from 'yargs-parser'
-
-const argv = parser('--foo=99 --bar=9987930', {
-  string: ['bar']
-})
-console.log(argv)
-```
-
-**Browsers:**
-
-```html
-<!doctype html>
-<body>
-  <script type="module">
-    import parser from "https://unpkg.com/yargs-parser@19.0.0/browser.js";
-
-    const argv = parser('--foo=99 --bar=9987930', {
-      string: ['bar']
-    })
-    console.log(argv)
-  </script>
-</body>
-```
-
 ## API
 
-### parser(args, opts={})
+### require('yargs-parser')(args, opts={})
 
 Parses command line arguments returning a simple mapping of keys and values.
@@ -143,12 +100,8 @@
   * `key/value`: key value pairs for each argument and their aliases.
   * `_`: an array representing the positional arguments.
-  * [optional] `--`:  an array with arguments after the end-of-options flag `--`.
 * `error`: populated with an error object if an exception occurred during parsing.
 * `aliases`: the inferred list of aliases built by combining lists in `opts.alias`.
-* `newAliases`: any new aliases added via camel-case expansion:
-  * `boolean`: `{ fooBar: true }`
-* `defaulted`: any new argument created by `opts.default`, no aliases included.
-  * `boolean`: `{ foo: true }`
-* `configuration`: given by default settings and `opts.configuration`.
+* `newAliases`: any new aliases added via camel-case expansion.
+* `configuration`: the configuration loaded from the `yargs` stanza in package.json.
 
 <a name="configuration"></a>
@@ -175,6 +128,6 @@
 Should a group of short-options be treated as boolean flags?
 
-```console
-$ node example.js -abc
+```sh
+node example.js -abc
 { _: [], a: true, b: true, c: true }
 ```
@@ -182,6 +135,6 @@
 _if disabled:_
 
-```console
-$ node example.js -abc
+```sh
+node example.js -abc
 { _: [], abc: true }
 ```
@@ -194,6 +147,6 @@
 Should hyphenated arguments be expanded into camel-case aliases?
 
-```console
-$ node example.js --foo-bar
+```sh
+node example.js --foo-bar
 { _: [], 'foo-bar': true, fooBar: true }
 ```
@@ -201,6 +154,6 @@
 _if disabled:_
 
-```console
-$ node example.js --foo-bar
+```sh
+node example.js --foo-bar
 { _: [], 'foo-bar': true }
 ```
@@ -213,6 +166,6 @@
 Should keys that contain `.` be treated as objects?
 
-```console
-$ node example.js --foo.bar
+```sh
+node example.js --foo.bar
 { _: [], foo: { bar: true } }
 ```
@@ -220,6 +173,6 @@
 _if disabled:_
 
-```console
-$ node example.js --foo.bar
+```sh
+node example.js --foo.bar
 { _: [], "foo.bar": true }
 ```
@@ -232,6 +185,6 @@
 Should keys that look like numbers be treated as such?
 
-```console
-$ node example.js --foo=99.3
+```sh
+node example.js --foo=99.3
 { _: [], foo: 99.3 }
 ```
@@ -239,28 +192,9 @@
 _if disabled:_
 
-```console
-$ node example.js --foo=99.3
+```sh
+node example.js --foo=99.3
 { _: [], foo: "99.3" }
 ```
 
-### parse positional numbers
-
-* default: `true`
-* key: `parse-positional-numbers`
-
-Should positional keys that look like numbers be treated as such.
-
-```console
-$ node example.js 99.3
-{ _: [99.3] }
-```
-
-_if disabled:_
-
-```console
-$ node example.js 99.3
-{ _: ['99.3'] }
-```
-
 ### boolean negation
 
@@ -270,6 +204,6 @@
 Should variables prefixed with `--no` be treated as negations?
 
-```console
-$ node example.js --no-foo
+```sh
+node example.js --no-foo
 { _: [], foo: false }
 ```
@@ -277,6 +211,6 @@
 _if disabled:_
 
-```console
-$ node example.js --no-foo
+```sh
+node example.js --no-foo
 { _: [], "no-foo": true }
 ```
@@ -297,6 +231,6 @@
 Should arguments be coerced into an array when duplicated:
 
-```console
-$ node example.js -x 1 -x 2
+```sh
+node example.js -x 1 -x 2
 { _: [], x: [1, 2] }
 ```
@@ -304,6 +238,6 @@
 _if disabled:_
 
-```console
-$ node example.js -x 1 -x 2
+```sh
+node example.js -x 1 -x 2
 { _: [], x: 2 }
 ```
@@ -316,6 +250,6 @@
 Should array arguments be coerced into a single array when duplicated:
 
-```console
-$ node example.js -x 1 2 -x 3 4
+```sh
+node example.js -x 1 2 -x 3 4
 { _: [], x: [1, 2, 3, 4] }
 ```
@@ -323,36 +257,8 @@
 _if disabled:_
 
-```console
-$ node example.js -x 1 2 -x 3 4
+```sh
+node example.js -x 1 2 -x 3 4
 { _: [], x: [[1, 2], [3, 4]] }
 ```
-
-### greedy arrays
-
-* default: `true`
-* key: `greedy-arrays`
-
-Should arrays consume more than one positional argument following their flag.
-
-```console
-$ node example --arr 1 2
-{ _: [], arr: [1, 2] }
-```
-
-_if disabled:_
-
-```console
-$ node example --arr 1 2
-{ _: [2], arr: [1] }
-```
-
-**Note: in `v18.0.0` we are considering defaulting greedy arrays to `false`.**
-
-### nargs eats options
-
-* default: `false`
-* key: `nargs-eats-options`
-
-Should nargs consume dash options as well as positional arguments.
 
 ### negation prefix
@@ -363,6 +269,6 @@
 The prefix to use for negated boolean variables.
 
-```console
-$ node example.js --no-foo
+```sh
+node example.js --no-foo
 { _: [], foo: false }
 ```
@@ -370,6 +276,6 @@
 _if set to `quux`:_
 
-```console
-$ node example.js --quuxfoo
+```sh
+node example.js --quuxfoo
 { _: [], foo: false }
 ```
@@ -384,6 +290,6 @@
 _If disabled:_
 
-```console
-$ node example.js a -b -- x y
+```sh
+node example.js a -b -- x y
 { _: [ 'a', 'x', 'y' ], b: true }
 ```
@@ -391,6 +297,6 @@
 _If enabled:_
 
-```console
-$ node example.js a -b -- x y
+```sh
+node example.js a -b -- x y
 { _: [ 'a' ], '--': [ 'x', 'y' ], b: true }
 ```
@@ -405,6 +311,6 @@
 _If disabled:_
 
-```console
-$ node example.js -a 1 -c 2
+```sh
+node example.js -a 1 -c 2
 { _: [], a: 1, c: 2 }
 ```
@@ -412,6 +318,6 @@
 _If enabled:_
 
-```console
-$ node example.js -a 1 -c 2
+```sh
+node example.js -a 1 -c 2
 { _: [], a: 1, b: undefined, c: 2 }
 ```
@@ -426,6 +332,6 @@
 _If disabled:_
 
-```console
-$ node example.js -a run b -x y
+```sh
+node example.js -a run b -x y
 { _: [ 'b' ], a: 'run', x: 'y' }
 ```
@@ -433,6 +339,6 @@
 _If enabled:_
 
-```console
-$ node example.js -a run b -x y
+```sh
+node example.js -a run b -x y
 { _: [ 'b', '-x', 'y' ], a: 'run' }
 ```
@@ -447,6 +353,6 @@
 _If disabled:_
 
-```console
-$ node example.js --test-field 1
+```sh
+node example.js --test-field 1
 { _: [], 'test-field': 1, testField: 1, 'test-alias': 1, testAlias: 1 }
 ```
@@ -454,6 +360,6 @@
 _If enabled:_
 
-```console
-$ node example.js --test-field 1
+```sh
+node example.js --test-field 1
 { _: [], 'test-field': 1, testField: 1 }
 ```
@@ -465,10 +371,10 @@
 
 Should dashed keys be removed before returning results?  This option has no effect if
-`camel-case-expansion` is disabled.
-
-_If disabled:_
-
-```console
-$ node example.js --test-field 1
+`camel-case-exansion` is disabled.
+
+_If disabled:_
+
+```sh
+node example.js --test-field 1
 { _: [], 'test-field': 1, testField: 1 }
 ```
@@ -476,36 +382,8 @@
 _If enabled:_
 
-```console
-$ node example.js --test-field 1
+```sh
+node example.js --test-field 1
 { _: [], testField: 1 }
 ```
-
-### unknown options as args
-
-* default: `false`
-* key: `unknown-options-as-args`
-
-Should unknown options be treated like regular arguments?  An unknown option is one that is not
-configured in `opts`.
-
-_If disabled_
-
-```console
-$ node example.js --unknown-option --known-option 2 --string-option --unknown-option2
-{ _: [], unknownOption: true, knownOption: 2, stringOption: '', unknownOption2: true }
-```
-
-_If enabled_
-
-```console
-$ node example.js --unknown-option --known-option 2 --string-option --unknown-option2
-{ _: ['--unknown-option'], knownOption: 2, stringOption: '--unknown-option2' }
-```
-
-## Supported Node.js Versions
-
-Libraries in this ecosystem make a best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
-post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 ## Special Thanks
