react-native-kookit 0.1.7 → 0.1.8

package/plugin/node_modules/js-tokens/README.md

@@ -1,240 +0,0 @@
-Overview [![Build Status](https://travis-ci.org/lydell/js-tokens.svg?branch=master)](https://travis-ci.org/lydell/js-tokens)
-========
-
-A regex that tokenizes JavaScript.
-
-```js
-var jsTokens = require("js-tokens").default
-
-var jsString = "var foo=opts.foo;\n..."
-
-jsString.match(jsTokens)
-// ["var", " ", "foo", "=", "opts", ".", "foo", ";", "\n", ...]
-```
-
-
-Installation
-============
-
-`npm install js-tokens`
-
-```js
-import jsTokens from "js-tokens"
-// or:
-var jsTokens = require("js-tokens").default
-```
-
-
-Usage
-=====
-
-### `jsTokens` ###
-
-A regex with the `g` flag that matches JavaScript tokens.
-
-The regex _always_ matches, even invalid JavaScript and the empty string.
-
-The next match is always directly after the previous.
-
-### `var token = matchToToken(match)` ###
-
-```js
-import {matchToToken} from "js-tokens"
-// or:
-var matchToToken = require("js-tokens").matchToToken
-```
-
-Takes a `match` returned by `jsTokens.exec(string)`, and returns a `{type:
-String, value: String}` object. The following types are available:
-
-- string
-- comment
-- regex
-- number
-- name
-- punctuator
-- whitespace
-- invalid
-
-Multi-line comments and strings also have a `closed` property indicating if the
-token was closed or not (see below).
-
-Comments and strings both come in several flavors. To distinguish them, check if
-the token starts with `//`, `/*`, `'`, `"` or `` ` ``.
-
-Names are ECMAScript IdentifierNames, that is, including both identifiers and
-keywords. You may use [is-keyword-js] to tell them apart.
-
-Whitespace includes both line terminators and other whitespace.
-
-[is-keyword-js]: https://github.com/crissdev/is-keyword-js
-
-
-ECMAScript support
-==================
-
-The intention is to always support the latest ECMAScript version whose feature
-set has been finalized.
-
-If adding support for a newer version requires changes, a new version with a
-major verion bump will be released.
-
-Currently, ECMAScript 2018 is supported.
-
-
-Invalid code handling
-=====================
-
-Unterminated strings are still matched as strings. JavaScript strings cannot
-contain (unescaped) newlines, so unterminated strings simply end at the end of
-the line. Unterminated template strings can contain unescaped newlines, though,
-so they go on to the end of input.
-
-Unterminated multi-line comments are also still matched as comments. They
-simply go on to the end of the input.
-
-Unterminated regex literals are likely matched as division and whatever is
-inside the regex.
-
-Invalid ASCII characters have their own capturing group.
-
-Invalid non-ASCII characters are treated as names, to simplify the matching of
-names (except unicode spaces which are treated as whitespace). Note: See also
-the [ES2018](#es2018) section.
-
-Regex literals may contain invalid regex syntax. They are still matched as
-regex literals. They may also contain repeated regex flags, to keep the regex
-simple.
-
-Strings may contain invalid escape sequences.
-
-
-Limitations
-===========
-
-Tokenizing JavaScript using regexes—in fact, _one single regex_—won’t be
-perfect. But that’s not the point either.
-
-You may compare jsTokens with [esprima] by using `esprima-compare.js`.
-See `npm run esprima-compare`!
-
-[esprima]: http://esprima.org/
-
-### Template string interpolation ###
-
-Template strings are matched as single tokens, from the starting `` ` `` to the
-ending `` ` ``, including interpolations (whose tokens are not matched
-individually).
-
-Matching template string interpolations requires recursive balancing of `{` and
-`}`—something that JavaScript regexes cannot do. Only one level of nesting is
-supported.
-
-### Division and regex literals collision ###
-
-Consider this example:
-
-```js
-var g = 9.82
-var number = bar / 2/g
-
-var regex = / 2/g
-```
-
-A human can easily understand that in the `number` line we’re dealing with
-division, and in the `regex` line we’re dealing with a regex literal. How come?
-Because humans can look at the whole code to put the `/` characters in context.
-A JavaScript regex cannot. It only sees forwards. (Well, ES2018 regexes can also
-look backwards. See the [ES2018](#es2018) section).
-
-When the `jsTokens` regex scans throught the above, it will see the following
-at the end of both the `number` and `regex` rows:
-
-```js
-/ 2/g
-```
-
-It is then impossible to know if that is a regex literal, or part of an
-expression dealing with division.
-
-Here is a similar case:
-
-```js
-foo /= 2/g
-foo(/= 2/g)
-```
-
-The first line divides the `foo` variable with `2/g`. The second line calls the
-`foo` function with the regex literal `/= 2/g`. Again, since `jsTokens` only
-sees forwards, it cannot tell the two cases apart.
-
-There are some cases where we _can_ tell division and regex literals apart,
-though.
-
-First off, we have the simple cases where there’s only one slash in the line:
-
-```js
-var foo = 2/g
-foo /= 2
-```
-
-Regex literals cannot contain newlines, so the above cases are correctly
-identified as division. Things are only problematic when there are more than
-one non-comment slash in a single line.
-
-Secondly, not every character is a valid regex flag.
-
-```js
-var number = bar / 2/e
-```
-
-The above example is also correctly identified as division, because `e` is not a
-valid regex flag. I initially wanted to future-proof by allowing `[a-zA-Z]*`
-(any letter) as flags, but it is not worth it since it increases the amount of
-ambigous cases. So only the standard `g`, `m`, `i`, `y` and `u` flags are
-allowed. This means that the above example will be identified as division as
-long as you don’t rename the `e` variable to some permutation of `gmiyus` 1 to 6
-characters long.
-
-Lastly, we can look _forward_ for information.
-
-- If the token following what looks like a regex literal is not valid after a
-  regex literal, but is valid in a division expression, then the regex literal
-  is treated as division instead. For example, a flagless regex cannot be
-  followed by a string, number or name, but all of those three can be the
-  denominator of a division.
-- Generally, if what looks like a regex literal is followed by an operator, the
-  regex literal is treated as division instead. This is because regexes are
-  seldomly used with operators (such as `+`, `*`, `&&` and `==`), but division
-  could likely be part of such an expression.
-
-Please consult the regex source and the test cases for precise information on
-when regex or division is matched (should you need to know). In short, you
-could sum it up as:
-
-If the end of a statement looks like a regex literal (even if it isn’t), it
-will be treated as one. Otherwise it should work as expected (if you write sane
-code).
-
-### ES2018 ###
-
-ES2018 added some nice regex improvements to the language.
-
-- [Unicode property escapes] should allow telling names and invalid non-ASCII
-  characters apart without blowing up the regex size.
-- [Lookbehind assertions] should allow matching telling division and regex
-  literals apart in more cases.
-- [Named capture groups] might simplify some things.
-
-These things would be nice to do, but are not critical. They probably have to
-wait until the oldest maintained Node.js LTS release supports those features.
-
-[Unicode property escapes]: http://2ality.com/2017/07/regexp-unicode-property-escapes.html
-[Lookbehind assertions]: http://2ality.com/2017/05/regexp-lookbehind-assertions.html
-[Named capture groups]: http://2ality.com/2017/05/regexp-named-capture-groups.html
-
-
-License
-=======
-
-[MIT](LICENSE).

package/plugin/node_modules/js-tokens/index.js

@@ -1,23 +0,0 @@
-// Copyright 2014, 2015, 2016, 2017, 2018 Simon Lydell
-// License: MIT. (See LICENSE.)
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-})
-
-// This regex comes from regex.coffee, and is inserted here by generate-index.js
-// (run `npm run build`).
-exports.default = /((['"])(?:(?!\2|\\).|\\(?:\r\n|[\s\S]))*(\2)?|`(?:[^`\\$]|\\[\s\S]|\$(?!\{)|\$\{(?:[^{}]|\{[^}]*\}?)*\}?)*(`)?)|(\/\/.*)|(\/\*(?:[^*]|\*(?!\/))*(\*\/)?)|(\/(?!\*)(?:\[(?:(?![\]\\]).|\\.)*\]|(?![\/\]\\]).|\\.)+\/(?:(?!\s*(?:\b|[\u0080-\uFFFF$\\'"~({]|[+\-!](?!=)|\.?\d))|[gmiyus]{1,6}\b(?![\u0080-\uFFFF$\\]|\s*(?:[+\-*%&|^<>!=?({]|\/(?![\/*])))))|(0[xX][\da-fA-F]+|0[oO][0-7]+|0[bB][01]+|(?:\d*\.\d+|\d+\.?)(?:[eE][+-]?\d+)?)|((?!\d)(?:(?!\s)[$\w\u0080-\uFFFF]|\\u[\da-fA-F]{4}|\\u\{[\da-fA-F]+\})+)|(--|\+\+|&&|\|\||=>|\.{3}|(?:[+\-\/%&|^]|\*{1,2}|<{1,2}|>{1,3}|!=?|={1,2})=?|[?~.,:;[\](){}])|(\s+)|(^$|[\s\S])/g
-
-exports.matchToToken = function(match) {
-  var token = {type: "invalid", value: match[0], closed: undefined}
-       if (match[ 1]) token.type = "string" , token.closed = !!(match[3] || match[4])
-  else if (match[ 5]) token.type = "comment"
-  else if (match[ 6]) token.type = "comment", token.closed = !!match[7]
-  else if (match[ 8]) token.type = "regex"
-  else if (match[ 9]) token.type = "number"
-  else if (match[10]) token.type = "name"
-  else if (match[11]) token.type = "punctuator"
-  else if (match[12]) token.type = "whitespace"
-  return token
-}

package/plugin/node_modules/js-tokens/package.json

@@ -1,30 +0,0 @@
-{
-  "name": "js-tokens",
-  "version": "4.0.0",
-  "author": "Simon Lydell",
-  "license": "MIT",
-  "description": "A regex that tokenizes JavaScript.",
-  "keywords": [
-    "JavaScript",
-    "js",
-    "token",
-    "tokenize",
-    "regex"
-  ],
-  "files": [
-    "index.js"
-  ],
-  "repository": "lydell/js-tokens",
-  "scripts": {
-    "test": "mocha --ui tdd",
-    "esprima-compare": "node esprima-compare ./index.js everything.js/es5.js",
-    "build": "node generate-index.js",
-    "dev": "npm run build && npm test"
-  },
-  "devDependencies": {
-    "coffeescript": "2.1.1",
-    "esprima": "4.0.0",
-    "everything.js": "1.0.3",
-    "mocha": "5.0.0"
-  }
-}

package/plugin/node_modules/json5/LICENSE.md

@@ -1,23 +0,0 @@
-MIT License
-
-Copyright (c) 2012-2018 Aseem Kishore, and [others].
-
-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.
-
-[others]: https://github.com/json5/json5/contributors

package/plugin/node_modules/json5/README.md

@@ -1,282 +0,0 @@
-# JSON5 – JSON for Humans
-
-[![Build Status](https://app.travis-ci.com/json5/json5.svg?branch=main)][Build
-Status] [![Coverage
-Status](https://coveralls.io/repos/github/json5/json5/badge.svg)][Coverage
-Status]
-
-JSON5 is an extension to the popular [JSON] file format that aims to be
-easier to **write and maintain _by hand_ (e.g. for config files)**.
-It is _not intended_ to be used for machine-to-machine communication.
-(Keep using JSON or other file formats for that. 🙂)
-
-JSON5 was started in 2012, and as of 2022, now gets **[>65M downloads/week](https://www.npmjs.com/package/json5)**,
-ranks in the **[top 0.1%](https://gist.github.com/anvaka/8e8fa57c7ee1350e3491)** of the most depended-upon packages on npm,
-and has been adopted by major projects like
-**[Chromium](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/runtime_enabled_features.json5;drc=5de823b36e68fd99009a29281b17bc3a1d6b329c),
-[Next.js](https://github.com/vercel/next.js/blob/b88f20c90bf4659b8ad5cb2a27956005eac2c7e8/packages/next/lib/find-config.ts#L43-L46),
-[Babel](https://babeljs.io/docs/en/config-files#supported-file-extensions),
-[Retool](https://community.retool.com/t/i-am-attempting-to-append-several-text-fields-to-a-google-sheet-but-receiving-a-json5-invalid-character-error/7626),
-[WebStorm](https://www.jetbrains.com/help/webstorm/json.html),
-and [more](https://github.com/json5/json5/wiki/In-the-Wild)**.
-It's also natively supported on **[Apple platforms](https://developer.apple.com/documentation/foundation/jsondecoder/3766916-allowsjson5)**
-like **MacOS** and **iOS**.
-
-Formally, the **[JSON5 Data Interchange Format](https://spec.json5.org/)** is a superset of JSON
-(so valid JSON files will always be valid JSON5 files)
-that expands its syntax to include some productions from [ECMAScript 5.1] (ES5).
-It's also a strict _subset_ of ES5, so valid JSON5 files will always be valid ES5.
-
-This JavaScript library is a reference implementation for JSON5 parsing and serialization,
-and is directly used in many of the popular projects mentioned above
-(where e.g. extreme performance isn't necessary),
-but others have created [many other libraries](https://github.com/json5/json5/wiki/In-the-Wild)
-across many other platforms.
-
-[Build Status]: https://app.travis-ci.com/json5/json5
-
-[Coverage Status]: https://coveralls.io/github/json5/json5
-
-[JSON]: https://tools.ietf.org/html/rfc7159
-
-[ECMAScript 5.1]: https://www.ecma-international.org/ecma-262/5.1/
-
-## Summary of Features
-The following ECMAScript 5.1 features, which are not supported in JSON, have
-been extended to JSON5.
-
-### Objects
-- Object keys may be an ECMAScript 5.1 _[IdentifierName]_.
-- Objects may have a single trailing comma.
-
-### Arrays
-- Arrays may have a single trailing comma.
-
-### Strings
-- Strings may be single quoted.
-- Strings may span multiple lines by escaping new line characters.
-- Strings may include character escapes.
-
-### Numbers
-- Numbers may be hexadecimal.
-- Numbers may have a leading or trailing decimal point.
-- Numbers may be [IEEE 754] positive infinity, negative infinity, and NaN.
-- Numbers may begin with an explicit plus sign.
-
-### Comments
-- Single and multi-line comments are allowed.
-
-### White Space
-- Additional white space characters are allowed.
-
-[IdentifierName]: https://www.ecma-international.org/ecma-262/5.1/#sec-7.6
-
-[IEEE 754]: http://ieeexplore.ieee.org/servlet/opac?punumber=4610933
-
-## Example
-Kitchen-sink example:
-
-```js
-{
-  // comments
-  unquoted: 'and you can quote me on that',
-  singleQuotes: 'I can use "double quotes" here',
-  lineBreaks: "Look, Mom! \
-No \\n's!",
-  hexadecimal: 0xdecaf,
-  leadingDecimalPoint: .8675309, andTrailing: 8675309.,
-  positiveSign: +1,
-  trailingComma: 'in objects', andIn: ['arrays',],
-  "backwardsCompatible": "with JSON",
-}
-```
-
-A more real-world example is [this config file](https://github.com/chromium/chromium/blob/feb3c9f670515edf9a88f185301cbd7794ee3e52/third_party/blink/renderer/platform/runtime_enabled_features.json5)
-from the Chromium/Blink project.
-
-## Specification
-For a detailed explanation of the JSON5 format, please read the [official
-specification](https://json5.github.io/json5-spec/).
-
-## Installation and Usage
-### Node.js
-```sh
-npm install json5
-```
-
-#### CommonJS
-```js
-const JSON5 = require('json5')
-```
-
-#### Modules
-```js
-import JSON5 from 'json5'
-```
-
-### Browsers
-#### UMD
-```html
-<!-- This will create a global `JSON5` variable. -->
-<script src="https://unpkg.com/json5@2/dist/index.min.js"></script>
-```
-
-#### Modules
-```html
-<script type="module">
-  import JSON5 from 'https://unpkg.com/json5@2/dist/index.min.mjs'
-</script>
-```
-
-## API
-The JSON5 API is compatible with the [JSON API].
-
-[JSON API]:
-https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON
-
-### JSON5.parse()
-Parses a JSON5 string, constructing the JavaScript value or object described by
-the string. An optional reviver function can be provided to perform a
-transformation on the resulting object before it is returned.
-
-#### Syntax
-    JSON5.parse(text[, reviver])
-
-#### Parameters
-- `text`: The string to parse as JSON5.
-- `reviver`: If a function, this prescribes how the value originally produced by
-  parsing is transformed, before being returned.
-
-#### Return value
-The object corresponding to the given JSON5 text.
-
-### JSON5.stringify()
-Converts a JavaScript value to a JSON5 string, optionally replacing values if a
-replacer function is specified, or optionally including only the specified
-properties if a replacer array is specified.
-
-#### Syntax
-    JSON5.stringify(value[, replacer[, space]])
-    JSON5.stringify(value[, options])
-
-#### Parameters
-- `value`: The value to convert to a JSON5 string.
-- `replacer`: A function that alters the behavior of the stringification
-  process, or an array of String and Number objects that serve as a whitelist
-  for selecting/filtering the properties of the value object to be included in
-  the JSON5 string. If this value is null or not provided, all properties of the
-  object are included in the resulting JSON5 string.
-- `space`: A String or Number object that's used to insert white space into the
-  output JSON5 string for readability purposes. If this is a Number, it
-  indicates the number of space characters to use as white space; this number is
-  capped at 10 (if it is greater, the value is just 10). Values less than 1
-  indicate that no space should be used. If this is a String, the string (or the
-  first 10 characters of the string, if it's longer than that) is used as white
-  space. If this parameter is not provided (or is null), no white space is used.
-  If white space is used, trailing commas will be used in objects and arrays.
-- `options`: An object with the following properties:
-  - `replacer`: Same as the `replacer` parameter.
-  - `space`: Same as the `space` parameter.
-  - `quote`: A String representing the quote character to use when serializing
-    strings.
-
-#### Return value
-A JSON5 string representing the value.
-
-### Node.js `require()` JSON5 files
-When using Node.js, you can `require()` JSON5 files by adding the following
-statement.
-
-```js
-require('json5/lib/register')
-```
-
-Then you can load a JSON5 file with a Node.js `require()` statement. For
-example:
-
-```js
-const config = require('./config.json5')
-```
-
-## CLI
-Since JSON is more widely used than JSON5, this package includes a CLI for
-converting JSON5 to JSON and for validating the syntax of JSON5 documents.
-
-### Installation
-```sh
-npm install --global json5
-```
-
-### Usage
-```sh
-json5 [options] <file>
-```
-
-If `<file>` is not provided, then STDIN is used.
-
-#### Options:
-- `-s`, `--space`: The number of spaces to indent or `t` for tabs
-- `-o`, `--out-file [file]`: Output to the specified file, otherwise STDOUT
-- `-v`, `--validate`: Validate JSON5 but do not output JSON
-- `-V`, `--version`: Output the version number
-- `-h`, `--help`: Output usage information
-
-## Contributing
-### Development
-```sh
-git clone https://github.com/json5/json5
-cd json5
-npm install
-```
-
-When contributing code, please write relevant tests and run `npm test` and `npm
-run lint` before submitting pull requests. Please use an editor that supports
-[EditorConfig](http://editorconfig.org/).
-
-### Issues
-To report bugs or request features regarding the JSON5 **data format**,
-please submit an issue to the official
-**[_specification_ repository](https://github.com/json5/json5-spec)**.
-
-Note that we will never add any features that make JSON5 incompatible with ES5;
-that compatibility is a fundamental premise of JSON5.
-
-To report bugs or request features regarding this **JavaScript implementation**
-of JSON5, please submit an issue to **_this_ repository**.
-
-### Security Vulnerabilities and Disclosures
-To report a security vulnerability, please follow the follow the guidelines
-described in our [security policy](./SECURITY.md).
-
-## License
-MIT. See [LICENSE.md](./LICENSE.md) for details.
-
-## Credits
-[Aseem Kishore](https://github.com/aseemk) founded this project.
-He wrote a [blog post](https://aseemk.substack.com/p/ignore-the-f-ing-haters-json5)
-about the journey and lessons learned 10 years in.
-
-[Michael Bolin](http://bolinfest.com/) independently arrived at and published
-some of these same ideas with awesome explanations and detail. Recommended
-reading: [Suggested Improvements to JSON](http://bolinfest.com/essays/json.html)
-
-[Douglas Crockford](http://www.crockford.com/) of course designed and built
-JSON, but his state machine diagrams on the [JSON website](http://json.org/), as
-cheesy as it may sound, gave us motivation and confidence that building a new
-parser to implement these ideas was within reach! The original
-implementation of JSON5 was also modeled directly off of Doug’s open-source
-[json_parse.js] parser. We’re grateful for that clean and well-documented
-code.
-
-[json_parse.js]:
-https://github.com/douglascrockford/JSON-js/blob/03157639c7a7cddd2e9f032537f346f1a87c0f6d/json_parse.js
-
-[Max Nanasy](https://github.com/MaxNanasy) has been an early and prolific
-supporter, contributing multiple patches and ideas.
-
-[Andrew Eisenberg](https://github.com/aeisenberg) contributed the original
-`stringify` method.
-
-[Jordan Tucker](https://github.com/jordanbtucker) has aligned JSON5 more closely
-with ES5, wrote the official JSON5 specification, completely rewrote the
-codebase from the ground up, and is actively maintaining this project.