@openfn/language-mysql 1.1.2 → 1.3.0

package/node_modules/@openfn/language-common/node_modules/jsonpath-plus/CHANGES.md

@@ -1,252 +0,0 @@
-# CHANGES for jsonpath-plus
-
-## 4.0.0 (2020-04-09)
-
-- Breaking change/fix: Disallow `resultType` from being lower-cased
-    (broke `parentProperty`)
-- Breaking change: Expect Node >= 10
-- Build: As per latest rollup
-- Linting: Check hidden files; update as per latest ash-nazg
-- Docs: Update coverage badge
-- npm: Update devDeps
-
-## 3.0.0 (2020-01-13)
-
-- Breaking change: Expect Node >= 8
-- Fix: Require `json` as "own" property
-- Fix: wrap: false returning inconsistent data types (@CacheControl)
-- Fix: Ensure throwing with a bad result type
-- Fix: Allow empty string keys
-- Fix: Avoid erring when value before parent selector is falsey
-- Fix: If `resultType` is "all", if path resolves internally to a
-    non-array (string), ensure it is converted to an array before
-    converting to pointer for `pointer`
-- Enhancement: Allow path as array in non-object signature
-- Docs: Add locally-generated badges for testing, coverage, etc.
-- Linting (ESLint): As per latest ash-nazg
-- Linting (ESLint): Remove redundant "use strict" with switch to ESM
-- Maintenance: 2 sp. for package.json
-- Testing: Add nyc for coverage
-- Testing: Test against source (using `esm`)
-- Testing: Improve coverage (more type operator tests)
-- Testing: Check vm
-- npm: Add `test-cov` script
-- npm: Update devDeps
-
-## 2.0.0 (2019-11-23)
-
-- Breaking change: Throw `TypeError` instead of `Error` for missing
-    `otherTypeCallback` when using `@other`
-- Breaking change: Throw `TypeError` instead of `Error` for missing `path`
-- Enhancement: Throw `TypeError` for missing `json` (fixes #110)
-- Enhancement: Use more efficient `new Function` over `eval`;
-    also allows use of cyclic context objects
-- Maintenance: Add `.editorconfig`
-- Docs: Document options in jsdoc; add return values to callbacks;
-    fix constructor doc sig.
-- Testing: Add test for missing `path` or `json`
-- Testing: Remove unneeded closures
-- npm: Update devDeps
-
-## 1.2.0 (October 13, 2019)
-
-- Enhancement: Add `@root` filter selector
-- Enhancement: Use more efficient `new Function` over `eval`;
-    also allows use of cyclic context objects
-- npm: Update devDeps and `package-lock.json`
-
-## 1.1.0 (September 26, 2019)
-
-- Enhancement: Add explicit 'any' to `evaluate()` declaration (for use
-  with `noImplicitAny` TypeScript option)
-- Build: Update minified build files
-- Travis: Update to check Node 6, 10, 12
-- npm: Ignore `.idea`/`.remarkrc` files
-- npm: Update devDeps (Babel, linting, Rollup, TypeScript related)
-- npm: Avoid eslint script within test script
-- npm: Ignore typescript docs
-
-## 1.0.0 (August 7, 2019)
-
-- Add TypeScript declaration
-
-## 0.20.1 (June 12, 2019)
-
-- npm: Avoid adding `core-js-bundle` as peerDep. (fixes #95)
-
-## 0.20.0 (June 4, 2019)
-
-- Build: Add `browserslist` for Babel builds
-- Linting: Conform to ESLint updates (jsdoc)
-- Testing: Switch from end-of-lifed nodeunit to Mocha
-- Testing: Add performance test to browser, but bump duration
-- npm: Update devDeps; add core-js-bundle to peerDependencies
-- npm: Ignore some unneeded files
-- Bump Node version in Travis to avoid erring with object rest
-    in eslint-plugin-node routine
-
-## 0.19.0 (May 16, 2019)
-
-- Docs (README): Indicate features, including performance (removing old note)
-- Docs (README): Add headings for setup and fix headings levels
-- Docs (README): Indicate parent selector was not present in original spec
-    (not just not documented)
-- Docs (README): Fix escaping
-- Linting: Switch to Unix line breaks and other changes per ash-nazg, including linting Markdown JS
-- Linting: Use recommended `.json` extension
-- Linting: Switch to ash-nazg
-- Linting: Add lgtm.yml file for lgtm.com
-- npm: Update devDeps, and update per security audit
-
-## 0.18.1 (May 14, 2019)
-
-- Fix: Expose `pointer` on `resultType: "all"`
-
-## 0.18.0 (October 20, 2018)
-
-- Security enhancement: Use global eval instead of regular eval
-- Fix: Handle React-Native environment's lack of support for
-    Node vm (@simon-scherzinger); closes #87
-- Refactoring: Use arrow functions, for-of, declare block scope vars
-    closer to block
-- Docs: Clarify current `wrap` behavior
-- npm: Add Rollup to test scripts
-
-## 0.17.0 (October 19, 2018)
-
-- Breaking change: With Node use, must now use
-    `require('jsonpath-plus').JSONPath`.
-- Breaking change: Stop including polyfills for array and string `includes`
-    (can get with `@babel/polyfill` or own)
-- Breaking change: Remove deprecated `JSONPath.eval`
-- License: Remove old and unneeded license portion from within source file
-    (already have external file)
-- Fix: Support object shorthand functions on sandbox objects
-    (`toString()` had not been working properly with them)
-- Enhancement: Add Rollup/Babel/Terser and `module` in `package.json`
-- Refactoring: Use ES6 features such as object shorthand
-- Linting: prefer const and no var
-- Testing: Replace custom server code with `node-static` and add `opn-cli`;
-    mostly switch to ESM
-- npm: Update devDeps; add `package-lock.json`; remove non-functioning remark
-
-## 0.16.0 (January 14, 2017)
-
-- Breaking change: Give preference to treating special chars in a property
-    as special (override with backtick operator)
-- Breaking feature: Add custom \` operator to allow unambiguous literal
-    sequences (if an initial backtick is needed, an additional one must
-    now be added)
-- Fix: `toPathArray` caching bug
-- Improvements: Performance optimizations
-- Dev testing: Rename test file
-
-## 0.15.0 (Mar 15, 2016)
-
-- Fix: Fixing support for sandbox in the case of functions
-- Feature: Use `this` if present for global export
-- Docs: Clarify function signature
-- Docs: Update testing section
-- Dev testing: Add in missing test for browser testing
-- Dev testing: Add remark linting to testing process (#70)
-- Dev testing: Lint JS test support files
-- Dev testing: Split out tests into `eslint`, `remark`, `lint`, `nodeunit`
-- Dev testing: Remove need for nodeunit build step
-- Dev testing: Simplify nodeunit usage and make available
-  as `npm run browser-test`
-
-## 0.14.0 (Jan 10, 2016)
-
-- Feature: Add `@scalar()` type operator (in JavaScript mode, will also
-    include)
-
-## 0.13.1 (Jan 5, 2016)
-
-- Fix: Avoid double-encoding path in results
-
-## 0.13.0 (Dec 13, 2015)
-
-- Breaking change (from version 0.11): Silently strip `~` and `^` operators
-  and type operators such as `@string()` in `JSONPath.toPathString()` calls.
-- Breaking change: Remove `Array.isArray` polyfill as no longer
-  supporting IE <= 8
-- Feature: Allow omission of options first argument to `JSONPath`
-- Feature: Add `JSONPath.toPointer()` and "pointer" `resultType` option.
-- Fix: Correctly support `callback` and `otherTypeCallback` as numbered
-  arguments to `JSONPath`.
-- Fix: Enhance Node checking to avoid issue reported with angular-mock
-- Fix: Allow for `@` or other special characters in at-sign-prefixed
-  property names (by use of `[?(@['...'])]` or  `[(@['...'])]`).
-
-## 0.12.0 (Dec 12, 2015 10:39pm)
-
-- Breaking change: Problems with upper-case letters in npm is causing
-  us to rename the package, so have renamed package to "jsonpath-plus"
-  (there are already package with lower-case "jsonpath" or "json-path").
-  The new name also reflects that there have been changes to the
-  original spec.
-
-## 0.11.2 (Dec 12, 2015 10:36pm)
-
-- Docs: Actually add the warning in the README that problems in npm
-  with upper-case letters is causing us to rename to "jsonpath-plus"
-  (next version will actually apply the change).
-
-## 0.11.1 (Dec 12, 2015 10:11pm)
-
-- Docs: Give warning in README that problems in npm with upper-case letters
-  is causing us to rename to "jsonpath-plus" (next version will actually
-  apply the change).
-
-## 0.11.0 (Dec 12, 2015)
-
-- Breaking change: For unwrapped results, return `undefined` instead
-  of `false` upon failure to find path (to allow distinguishing of
-  `undefined`--a non-allowed JSON value--from the valid JSON values,
-  `null` or `false`) and return the exact value upon falsy single
-  results (in order to allow return of `null`)
-- Deprecated: Use of `jsonPath.eval()`; use new class-based API instead
-- Feature: AMD export
-- Feature: By using `self` instead of `window` export, allow JSONPath
-  to be trivially imported into web workers, without breaking
-  compatibility in normal scenarios. See [MDN on self](https://developer.mozilla.org/en-US/docs/Web/API/Window/self)
-- Feature: Offer new class-based API and object-based arguments (with
-  option to run new queries via `evaluate()` method without resupplying config)
-- Feature: Allow new `preventEval=true` and `autostart=false` option
-- Feature: Allow new callback option to allow a callback function to execute as
-  each final result node is obtained
-- Feature: Allow type operators: JavaScript types (`@boolean()`, `@number()`,
-  `@string()`), other fundamental JavaScript types (`@null()`, `@object()`,
-  `@array()`), the JSONSchema-added type, `@integer()`, and the following
-  non-JSON types that can nevertheless be used with JSONPath when querying
-  non-JSON JavaScript objects (`@undefined()`, `@function()`, `@nonFinite()`).
-  Finally, `@other()` is made available in conjunction with a new callback
-  option, `otherTypeCallback`, can be used to allow user-defined type
-  detection (at least until JSON Schema awareness may be provided).
-- Feature: Support "parent" and "parentProperty" for resultType along with
-  "all" (which also includes "path" and "value" together)
-- Feature: Support custom `@parent`, `@parentProperty`, `@property` (in
-  addition to custom property `@path`) inside evaluations
-- Feature: Support a custom operator (`~`) to allow grabbing of property names
-- Feature: Support `$` for retrieval of root, and document this as well as
-  `$..` behavior
-- Feature: Expose cache on `JSONPath.cache` for those who wish to preserve and
-  reuse it
-- Feature: Expose class methods `toPathString` for converting a path as array
-  into a (normalized) path as string and `toPathArray` for the reverse (though
-  accepting unnormalized strings as well as normalized)
-- Fix: Allow `^` as property name
-- Fix: Support `.` within properties
-- Fix: `@path` in index/property evaluations
-
-## 0.10.0 (Oct 23, 2013)
-
-- Feature: Support for parent selection via `^`
-- Feature: Access current path via `@path` in test statements
-- Feature: Allowing for multi-statement evals
-- Improvements: Performance
-
-## 0.9.0 (Mar 28, 2012)
-
-- Feature: Support a sandbox arg to eval
-- Improvements: Use `vm.runInNewContext` in place of eval

package/node_modules/@openfn/language-common/node_modules/jsonpath-plus/LICENSE-MIT.txt

@@ -1,22 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2011-2019 Stefan Goessner, Subbu Allamaraju, Mike Brevoort,
-Robert Krahn, Brett Zamir, Richard Schneider
-
-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/node_modules/@openfn/language-common/node_modules/jsonpath-plus/README.md

@@ -1,376 +0,0 @@
-[![npm](https://img.shields.io/npm/v/jsonpath-plus.svg)](https://www.npmjs.com/package/jsonpath-plus)
-[![Dependencies](https://img.shields.io/david/s3u/JSONPath.svg)](https://david-dm.org/s3u/JSONPath)
-[![devDependencies](https://img.shields.io/david/dev/s3u/JSONPath.svg)](https://david-dm.org/s3u/JSONPath?type=dev)
-
-[![testing badge](https://raw.githubusercontent.com/s3u/JSONPath/master/badges/tests-badge.svg?sanitize=true)](badges/tests-badge.svg)
-[![coverage badge](https://raw.githubusercontent.com/s3u/JSONPath/master/badges/coverage-badge.svg?sanitize=true)](badges/coverage-badge.svg)
-
-[![Known Vulnerabilities](https://snyk.io/test/github/s3u/JSONPath/badge.svg)](https://snyk.io/test/github/s3u/JSONPath)
-[![Total Alerts](https://img.shields.io/lgtm/alerts/g/s3u/JSONPath.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/s3u/JSONPath/alerts)
-[![Code Quality: Javascript](https://img.shields.io/lgtm/grade/javascript/g/s3u/JSONPath.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/s3u/JSONPath/context:javascript)
-
-<!--[![License](https://img.shields.io/npm/l/JSONPath.svg)](LICENSE-MIT.txt)-->
-[![Licenses badge](https://raw.githubusercontent.com/s3u/JSONPath/master/badges/licenses-badge.svg?sanitize=true)](badges/licenses-badge.svg)
-
-<small>(see also [licenses for dev. deps.](https://raw.githubusercontent.com/s3u/JSONPath/master/badges/licenses-badge-dev.svg?sanitize=true))</small>
-
-# JSONPath Plus [![build status](https://secure.travis-ci.org/s3u/JSONPath.png)](http://travis-ci.org/s3u/JSONPath)
-
-Analyse, transform, and selectively extract data from JSON
-documents (and JavaScript objects).
-
-`jsonpath-plus` expands on the original specification to add some
-additional operators and makes explicit some behaviors the original
-did not spell out.
-
-## Features
-
-* **Compliant** with the original jsonpath spec
-* Convenient **additions or elaborations** not provided in the original spec:
-    * `^` for grabbing the **parent** of a matching item
-    * `~` for grabbing **property names** of matching items (as array)
-    * **Type selectors** for obtaining:
-        * Basic JSON types: `@null()`, `@boolean()`, `@number()`, `@string()`, `@array()`, `@object()`
-        * `@integer()`
-        * The compound type `@scalar()` (which also accepts `undefined` and
-            non-finite numbers when querying JavaScript objects as well as all of the basic non-object/non-function types)
-        * `@other()` usable in conjunction with a user-defined `otherTypeCallback`
-        * Non-JSON types that can nevertheless be used when querying
-            non-JSON JavaScript objects (`@undefined()`, `@function()`, `@nonFinite()`)
-    * `@path`/`@parent`/`@property`/`@parentProperty`/`@root` **shorthand selectors** within filters
-    * **Escaping**
-        * `` ` `` for escaping remaining sequence
-        * `@['...']`/`?@['...']` syntax for escaping special characters within
-        property names in filters
-    * Documents `$..` (**getting all parent components**)
-* **ESM** and **UMD** export formats
-* In addition to queried values, **can return various meta-information**
-    including paths or pointers to the value, as well as the parent
-    object and parent property name (to allow for modification).
-* **Utilities for converting** between paths, arrays, and pointers
-* Option to **prevent evaluations** permitted in the original spec or supply
-    a **sandbox** for evaluated values.
-* Option for **callback to handle results** as they are obtained.
-
-## Benchmarking
-
-`jsonpath-plus` is consistently performant with both large and small datasets compared to other json querying libraries per [json-querying-performance-testing](https://github.com/andykais/json-querying-performance-testing). You can verify these findings by [running the project yourself](https://github.com/andykais/json-querying-performance-testing#how-to-run) and adding more perf cases.
-
-## Install
-
-```shell
-npm install jsonpath-plus
-```
-
-## Setup
-
-### Node.js
-
-```js
-const {JSONPath} = require('jsonpath-plus');
-
-const result = JSONPath({path: '...', json});
-```
-
-### Browser
-
-For browser usage you can directly include `dist/index-umd.js`; no Browserify
-magic is necessary:
-
-```html
-<!-- Polyfill recommended by Babel for items not covered for older
-      browsers in dist -->
-<script src="node_modules/core-js-bundle/minified.js"></script>
-
-<script src="node_modules/jsonpath-plus/dist/index-umd.js"></script>
-<script>
-const result = JSONPath.JSONPath({path: '...', json: ...});
-</script>
-```
-
-### ESM (Modern browsers)
-
-You may also use ES6 Module imports (for modern browsers):
-
-```html
-<script type="module">
-import {JSONPath} from './node_modules/jsonpath-plus/dist/index-es.js';
-const result = JSONPath({path: '...', json: ...});
-</script>
-```
-
-### ESM (Bundlers)
-
-Or if you are bundling your JavaScript (e.g., with Rollup), just use:
-
-```js
-import {JSONPath} from 'jsonpath-plus';
-
-const result = JSONPath({path: '...', json});
-```
-
-## Usage
-
-The full signature available is:
-
-```
-const result = JSONPath([options,] path, json, callback, otherTypeCallback);
-```
-
-The arguments `path`, `json`, `callback`, and `otherTypeCallback`
-can alternatively be expressed (along with any other of the
-available properties) on `options`.
-
-Note that `result` will contain all items found (optionally
-wrapped into an array) whereas `callback` can be used if you
-wish to perform some operation as each item is discovered, with
-the callback function being executed 0 to N times depending
-on the number of independent items to be found in the result.
-See the docs below for more on `JSONPath`'s available arguments.
-
-### Properties
-
-The properties that can be supplied on the options object or
-evaluate method (as the first argument) include:
-
-- ***path*** (**required**) - The JSONPath expression as a (normalized
-  or unnormalized) string or array
-- ***json*** (**required**) - The JSON object to evaluate (whether of
-  null, boolean, number, string, object, or array type).
-- ***autostart*** (**default: true**) - If this is supplied as `false`,
-  one may call the `evaluate` method manually.
-- ***flatten*** (**default: false**) - Whether the returned array of results
-  will be flattened to a single dimension array.
-- ***resultType*** (**default: "value"**) - Can be case-insensitive form of
-  "value", "path", "pointer", "parent", or "parentProperty" to determine
-  respectively whether to return results as the values of the found items,
-  as their absolute paths, as [JSON Pointers](http://www.rfc-base.org/txt/rfc-6901.txt)
-  to the absolute paths, as their parent objects, or as their parent's
-  property name. If set to "all", all of these types will be returned on
-  an object with the type as key name.
-- ***sandbox*** (**default: {}**) - Key-value map of variables to be
-  available to code evaluations such as filtering expressions. (Note
-  that the current path and value will also be available to those
-  expressions; see the Syntax section for details.)
-- ***wrap*** (**default: true**) - Whether or not to wrap the results
-  in an array. If `wrap` is set to `false`, and no results are found,
-  `undefined` will be returned (as opposed to an empty array when
-  `wrap` is set to true). If `wrap` is set to `false` and a single
-  non-array result is found, that result will be the only item returned
-  (not within an array). An array will still be returned if multiple
-  results are found, however. To avoid ambiguities (in the case where
-  it is necessary to distinguish between a result which is a failure
-  and one which is an empty array), it is recommended to switch the
-  default to `false`.
-- ***preventEval*** (**default: false**) - Although JavaScript evaluation
-  expressions are allowed by default, for security reasons (if one is
-  operating on untrusted user input, for example), one may wish to
-  set this option to `true` to throw exceptions when these expressions
-  are attempted.
-- ***parent*** (**default: null**) - In the event that a query could be
-  made to return the root node, this allows the parent of that root node
-  to be returned within results.
-- ***parentProperty*** (**default: null**) - In the event that a query
-  could be made to return the root node, this allows the `parentProperty`
-  of that root node to be returned within results.
-- ***callback*** (**default: (none)**) - If supplied, a callback will be
-  called immediately upon retrieval of an end point value. The three arguments
-  supplied will be the value of the payload (according to `resultType`),
-  the type of the payload (whether it is a normal "value" or a "property"
-  name), and a full payload object (with all `resultType`s).
-- ***otherTypeCallback*** (**default: \<A function that throws an error**
-  **when @other() is encountered\>**) - In the current absence of JSON
-  Schema support, one can determine types beyond the built-in types by
-  adding the operator `@other()` at the end of one's query. If such a
-  path is encountered, the `otherTypeCallback` will be invoked with the
-  value of the item, its path, its parent, and its parent's property name,
-  and it should return a boolean indicating whether the supplied value
-  belongs to the "other" type or not (or it may handle transformations and
-  return false).
-
-### Instance methods
-
-- ***evaluate(path, json, callback, otherTypeCallback)*** OR
-  ***evaluate({path: \<path\>, json: \<json object\>, callback:***
-  ***\<callback function\>, otherTypeCallback:***
-  ***\<otherTypeCallback function\>})*** - This method is only
-  necessary if the `autostart` property is set to `false`. It
-  can be used for repeated evaluations using the same configuration.
-  Besides the listed properties, the latter method pattern can
-  accept any of the other allowed instance properties (except
-  for `autostart` which would have no relevance here).
-
-### Class properties and methods
-
-- ***JSONPath.cache*** - Exposes the cache object for those who wish
-  to preserve and reuse it for optimization purposes.
-- ***JSONPath.toPathArray(pathAsString)*** - Accepts a normalized or
-  unnormalized path as string and converts to an array: for
-  example, `['$', 'aProperty', 'anotherProperty']`.
-- ***JSONPath.toPathString(pathAsArray)*** - Accepts a path array and
-  converts to a normalized path string. The string will be in a form
-  like: `$['aProperty']['anotherProperty][0]`. The JSONPath terminal
-  constructions `~` and `^` and type operators like `@string()` are
-  silently stripped.
-- ***JSONPath.toPointer(pathAsArray)*** - Accepts a path array and
-  converts to a [JSON Pointer](http://www.rfc-base.org/txt/rfc-6901.txt).
-  The string will be in a form like: `/aProperty/anotherProperty/0`
-  (with any `~` and `/` internal characters escaped as per the JSON
-  Pointer spec). The JSONPath terminal constructions `~` and `^` and
-  type operators like `@string()` are silently stripped.
-
-## Syntax through examples
-
-Given the following JSON, taken from <http://goessner.net/articles/JsonPath/>:
-
-```json
-{
-"store": {
-  "book": [
-    {
-      "category": "reference",
-      "author": "Nigel Rees",
-      "title": "Sayings of the Century",
-      "price": 8.95
-    },
-    {
-      "category": "fiction",
-      "author": "Evelyn Waugh",
-      "title": "Sword of Honour",
-      "price": 12.99
-    },
-    {
-      "category": "fiction",
-      "author": "Herman Melville",
-      "title": "Moby Dick",
-      "isbn": "0-553-21311-3",
-      "price": 8.99
-    },
-    {
-      "category": "fiction",
-      "author": "J. R. R. Tolkien",
-      "title": "The Lord of the Rings",
-      "isbn": "0-395-19395-8",
-      "price": 22.99
-    }
-  ],
-  "bicycle": {
-    "color": "red",
-    "price": 19.95
-  }
-}
-}
-```
-
-and the following XML representation:
-
-```xml
-<store>
-    <book>
-        <category>reference</category>
-        <author>Nigel Rees</author>
-        <title>Sayings of the Century</title>
-        <price>8.95</price>
-    </book>
-    <book>
-        <category>fiction</category>
-        <author>Evelyn Waugh</author>
-        <title>Sword of Honour</title>
-        <price>12.99</price>
-    </book>
-    <book>
-        <category>fiction</category>
-        <author>Herman Melville</author>
-        <title>Moby Dick</title>
-        <isbn>0-553-21311-3</isbn>
-        <price>8.99</price>
-    </book>
-    <book>
-        <category>fiction</category>
-        <author>J. R. R. Tolkien</author>
-        <title>The Lord of the Rings</title>
-        <isbn>0-395-19395-8</isbn>
-        <price>22.99</price>
-    </book>
-    <bicycle>
-        <color>red</color>
-        <price>19.95</price>
-    </bicycle>
-</store>
-```
-
-Please note that the XPath examples below do not distinguish between
-retrieving elements and their text content (except where useful for
-comparisons or to prevent ambiguity).
-
-| XPath             | JSONPath               | Result                                | Notes |
-| ----------------- | ---------------------- | ------------------------------------- | ----- |
-/store/book/author  | $.store.book\[*].author | The authors of all books in the store | Can also be represented without the `$.` as `store.book[*].author` (though this is not present in the original spec); note that some character literals (`$` and `@`) require escaping, however
-//author            | $..author              | All authors                           |
-/store/*            | $.store.*              | All things in store, which are its books (a book array) and a red bicycle (a bicycle object).|
-/store//price       | $.store..price         | The price of everything in the store. |
-//book\[3]           | $..book\[2]             | The third book (book object)          |
-//book\[last()]      | $..book\[(@.length-1)]<br>$..book\[-1:]  | The last book in order.| To access a property with a special character, utilize `[(@['...'])]` for the filter (this particular feature is not present in the original spec)
-//book\[position()<3]| $..book\[0,1]<br>$..book\[:2]| The first two books               |
-//book/*\[self::category\|self::author] or //book/(category,author) in XPath 2.0 | $..book\[0]\[category,author]| The categories and authors of all books |
-//book\[isbn]        | $..book\[?(@.isbn)]     | Filter all books with an ISBN number     | To access a property with a special character, utilize `[?@['...']]` for the filter (this particular feature is not present in the original spec)
-//book\[price<10]    | $..book\[?(@.price<10)] | Filter all books cheaper than 10     |
-| //\*\[name() = 'price' and . != 8.95] | $..\*\[?(@property === 'price' && @ !== 8.95)] | Obtain all property values of objects whose property is price and which does not equal 8.95 | With the bare `@` allowing filtering objects by property value (not necessarily within arrays), you can add `^` after the expression to get at the object possessing the filtered properties
-/                   | $                      | The root of the JSON object (i.e., the whole object itself) | To get a literal `$` (by itself or anywhere in the path), you must use the backtick escape
-//\*/\*\|//\*/\*/text()  | $..*                   | All Elements (and text) beneath root in an XML document. All members of a JSON structure beneath the root. |
-//*                 | $..                    | All Elements in an XML document. All parent components of a JSON structure including root. | This behavior was not directly specified in the original spec
-//*\[price>19]/..    | $..\[?(@.price>19)]^    | Parent of those specific items with a price greater than 19 (i.e., the store value as the parent of the bicycle and the book array as parent of an individual book) | Parent (caret) not present in the original spec
-/store/*/name() (in XPath 2.0)  | $.store.*~ | The property names of the store sub-object ("book" and "bicycle"). Useful with wildcard properties. | Property name (tilde) is not present in the original spec
-/store/book\[not(. is /store/book\[1\])\] (in XPath 2.0) | $.store.book\[?(@path !== "$\[\'store\']\[\'book\']\[0]")] | All books besides that at the path pointing to the first | @path not present in the original spec
-//book\[parent::\*/bicycle/color = "red"]/category | $..book\[?(@parent.bicycle && @parent.bicycle.color === "red")].category | Grabs all categories of books where the parent object of the book has a bicycle child whose color is red (i.e., all the books) | @parent is not present in the original spec
-//book/*\[name() != 'category']     | $..book.*\[?(@property !== "category")] | Grabs all children of "book" except for "category" ones  | @property is not present in the original spec
-//book/*\[position() != 0]    | $..book\[?(@property !== 0)] | Grabs all books whose property (which, being that we are reaching inside an array, is the numeric index) is not 0 | @property is not present in the original spec
-/store/\*/\*\[name(parent::*) != 'book'] | $.store.*\[?(@parentProperty !== "book")] | Grabs the grandchildren of store whose parent property is not book (i.e., bicycle's children, "color" and "price") | @parentProperty is not present in the original spec
-//book\[count(preceding-sibling::\*) != 0]/\*/text() | $..book.*\[?(@parentProperty !== 0)]  | Get the property values of all book instances whereby the parent property of these values (i.e., the array index holding the book item parent object) is not 0 | @parentProperty is not present in the original spec
-//book\[price = /store/book\[3]/price] | $..book\[?(@.price === @root.store.book\[2].price)] | Filter all books whose price equals the price of the third book | @root is not present in the original spec
-//book/../\*\[. instance of element(\*, xs:decimal)\] (in XPath 2.0) | $..book..\*@number() | Get the numeric values within the book array | @number(), the other basic types (@boolean(), @string()), other low-level derived types (@null(), @object(), @array()), the JSONSchema-added type, @integer(), the compound type @scalar() (which also accepts `undefined` and non-finite numbers for JavaScript objects as well as all of the basic non-object/non-function types), the type, @other(), to be used in conjunction with a user-defined callback (see `otherTypeCallback`) and the following non-JSON types that can nevertheless be used with JSONPath when querying non-JSON JavaScript objects (@undefined(), @function(), @nonFinite()) are not present in the original spec
-| | `` ` `` (e.g., `` `$`` to match a property literally named `$`) | Escapes the entire sequence following (to be treated as a literal) | `` ` `` is not present in the original spec; to get a literal backtick, use an additional backtick to escape
-
-Any additional variables supplied as properties on the optional "sandbox"
-object option are also available to (parenthetical-based)
-evaluations.
-
-## Potential sources of confusion for XPath users
-
-1. In JSONPath, a filter expression, in addition to its `@` being a
-reference to its children, actually selects the immediate children
-as well, whereas in XPath, filter conditions do not select the children
-but delimit which of its parent nodes will be obtained in the result.
-1. In JSONPath, array indexes are, as in JavaScript, 0-based (they begin
-from 0), whereas in XPath, they are 1-based.
-1. In JSONPath, equality tests utilize (as per JavaScript) multiple equal signs
-whereas in XPath, they use a single equal sign.
-
-## Ideas
-
-1. Support OR outside of filters (as in XPath `|`) and grouping.
-1. Create syntax to work like XPath filters in not selecting children?
-1. Allow option for parentNode equivalent (maintaining entire chain of
-    parent-and-parentProperty objects up to root)
-
-## Development
-
-Running the tests on Node:
-
-```shell
-npm test
-```
-
-For in-browser tests:
-
-- Serve the js/html files:
-
-```shell
-npm run browser-test
-```
-
-- Visit [http://localhost:8082/test/](http://localhost:8082/test/).
-
-## License
-
-[MIT License](http://www.opensource.org/licenses/mit-license.php).

package/node_modules/@openfn/language-common/node_modules/jsonpath-plus/demo/index.css

@@ -1,19 +0,0 @@
-#jsonpath {
-  width: 90%;
-  margin-bottom: 10px;
-}
-
-.container {
-  float: left;
-  width: 48%;
-}
-
-.container textarea {
-  margin: 2%;
-  width: 98%;
-  height: 565px;
-}
-
-#demoNode {
-  font-size: small;
-}