@cloudbase/framework-plugin-low-code 0.4.45 → 0.5.1

package/template/node_modules/comlink/CONTRIBUTING

@@ -1,27 +0,0 @@
-Want to contribute? Great! First, read this page (including the small print at the end).
-
-### Before you contribute
-Before we can use your code, you must sign the
-[Google Individual Contributor License Agreement]
-(https://cla.developers.google.com/about/google-individual)
-(CLA), which you can do online. The CLA is necessary mainly because you own the
-copyright to your changes, even after your contribution becomes part of our
-codebase, so we need your permission to use and distribute your code. We also
-need to be sure of various other things—for instance that you'll tell us if you
-know that your code infringes on other people's patents. You don't have to sign
-the CLA until after you've submitted your code for review and a member has
-approved it, but you must do it before we can put your code into our codebase.
-Before you start working on a larger contribution, you should get in touch with
-us first through the issue tracker with your idea so that we can help out and
-possibly guide you. Coordinating up front makes it much easier to avoid
-frustration later on.
-
-### Code reviews
-All submissions, including submissions by project members, require review. We
-use Github pull requests for this purpose.
-
-### The small print
-Contributions made by corporations are covered by a different agreement than
-the one above, the
-[Software Grant and Corporate Contributor License Agreement]
-(https://cla.developers.google.com/about/google-corporate).

package/template/node_modules/comlink/CONTRIBUTORS

@@ -1,11 +0,0 @@
-# People who have agreed to one of the CLAs and can contribute patches.
-# The AUTHORS file lists the copyright holders; this file
-# lists people.  For example, Google employees are listed here
-# but not in AUTHORS, because Google holds the copyright.
-#
-# https://developers.google.com/open-source/cla/individual
-# https://developers.google.com/open-source/cla/corporate
-#
-# Names should be added to this file as:
-#     Name <email address>
-Surma <surma@google.com>

package/template/node_modules/comlink/Dockerfile

@@ -1,19 +0,0 @@
-FROM selenium/node-chrome:latest@sha256:31be7ba7ebe6db9f9b266c10fc5f6fce7568791a6ade91b6b6d20a29a988ef5b
-
-USER root
-
-RUN apt-get update -qqy \
-  && rm -rf /var/lib/apt/lists/* /var/cache/apt/* \
-  && rm /bin/sh && ln -s /bin/bash /bin/sh \
-  && chown seluser /usr/local
-
-ENV NVM_DIR /usr/local/nvm
-RUN wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash \
-  && source $NVM_DIR/nvm.sh \
-  && nvm install v11
-
-ENV CHROME_BIN /opt/google/chrome/chrome
-ENV INSIDE_DOCKER=1
-
-WORKDIR /usr/src
-ENTRYPOINT source $NVM_DIR/nvm.sh && npm i && npm test

package/template/node_modules/comlink/LICENSE

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright 2017 Google Inc.
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

package/template/node_modules/comlink/README.md

@@ -1,270 +0,0 @@
-# Comlink
-
-Comlink makes [WebWorkers][webworker] enjoyable. Comlink is a **tiny library (1.1kB)**, that removes the mental barrier of thinking about `postMessage` and hides the fact that you are working with workers.
-
-At a more abstract level it is an RPC implementation for `postMessage` and [ES6 Proxies][es6 proxy].
-
-```
-$ npm install --save comlink
-```
-
-![Comlink in action](https://user-images.githubusercontent.com/234957/54164510-cdab2d80-4454-11e9-92d0-7356aa6c5746.png)
-
-## Browsers support & bundle size
-
-![Chrome 56+](https://img.shields.io/badge/Chrome-56+-green.svg?style=flat-square)
-![Edge 15+](https://img.shields.io/badge/Edge-15+-green.svg?style=flat-square)
-![Firefox 52+](https://img.shields.io/badge/Firefox-52+-green.svg?style=flat-square)
-![Opera 43+](https://img.shields.io/badge/Opera-43+-green.svg?style=flat-square)
-![Safari 10.1+](https://img.shields.io/badge/Safari-10.1+-green.svg?style=flat-square)
-![Samsung Internet 6.0+](https://img.shields.io/badge/Samsung_Internet-6.0+-green.svg?style=flat-square)
-
-Browsers without [ES6 Proxy] support can use the [proxy-polyfill].
-
-**Size**: ~2.5k, ~1.2k gzip’d, ~1.1k brotli’d
-
-## Introduction
-
-On mobile phones, and especially on low-end mobile phones, it is important to keep the main thread as idle as possible so it can respond to user interactions quickly and provide a jank-free experience. **The UI thread ought to be for UI work only**. WebWorkers are a web API that allow you to run code in a separate thread. To communicate with another thread, WebWorkers offer the `postMessage` API. You can send JavaScript objects as messages using `myWorker.postMessage(someObject)`, triggering a `message` event inside the worker.
-
-Comlink turns this messaged-based API into a something more developer-friendly by providing an RPC implementation: Values from one thread can be used within the other thread (and vice versa) just like local values.
-
-## Examples
-
-### [Running a simple function](https://github.com/GoogleChromeLabs/comlink/tree/master/docs/examples/01-simple-example)
-
-**main.js**
-
-```javascript
-import * as Comlink from "https://unpkg.com/comlink/dist/esm/comlink.mjs";
-async function init() {
-  const worker = new Worker("worker.js");
-  // WebWorkers use `postMessage` and therefore work with Comlink.
-  const obj = Comlink.wrap(worker);
-  alert(`Counter: ${await obj.counter}`);
-  await obj.inc();
-  alert(`Counter: ${await obj.counter}`);
-}
-init();
-```
-
-**worker.js**
-
-```javascript
-importScripts("https://unpkg.com/comlink/dist/umd/comlink.js");
-// importScripts("../../../dist/umd/comlink.js");
-
-const obj = {
-  counter: 0,
-  inc() {
-    this.counter++;
-  },
-};
-
-Comlink.expose(obj);
-```
-
-### [Callbacks](https://github.com/torch2424/comlink/tree/master/docs/examples/02-callback-example)
-
-**main.js**
-
-```javascript
-import * as Comlink from "https://unpkg.com/comlink/dist/esm/comlink.mjs";
-// import * as Comlink from "../../../dist/esm/comlink.mjs";
-function callback(value) {
-  alert(`Result: ${value}`);
-}
-async function init() {
-  const remoteFunction = Comlink.wrap(new Worker("worker.js"));
-  await remoteFunction(Comlink.proxy(callback));
-}
-init();
-```
-
-**worker.js**
-
-```javascript
-importScripts("https://unpkg.com/comlink/dist/umd/comlink.js");
-// importScripts("../../../dist/umd/comlink.js");
-
-async function remoteFunction(cb) {
-  await cb("A string from a worker");
-}
-
-Comlink.expose(remoteFunction);
-```
-
-### [`SharedWorker`](./docs/examples/07-sharedworker-example)
-
-When using Comlink with a [`SharedWorker`](https://developer.mozilla.org/en-US/docs/Web/API/SharedWorker) you have to:
-
-1. Use the [`port`](https://developer.mozilla.org/en-US/docs/Web/API/SharedWorker/port) property, of the `SharedWorker` instance, when calling `Comlink.wrap`.
-2. Call `Comlink.expose` within the [`onconnect`](https://developer.mozilla.org/en-US/docs/Web/API/SharedWorkerGlobalScope/onconnect) callback of the shared worker.
-
-**Pro tip:** You can access DevTools for any shared worker currently running in Chrome by going to: **chrome://inspect/#workers**
-
-**main.js**
-
-```javascript
-import * as Comlink from "https://unpkg.com/comlink/dist/esm/comlink.mjs";
-async function init() {
-  const worker = new SharedWorker("worker.js");
-  /**
-   * SharedWorkers communicate via the `postMessage` function in their `port` property.
-   * Therefore you must use the SharedWorker's `port` property when calling `Comlink.wrap`.
-   */
-  const obj = Comlink.wrap(worker.port);
-  alert(`Counter: ${await obj.counter}`);
-  await obj.inc();
-  alert(`Counter: ${await obj.counter}`);
-}
-init();
-```
-
-**worker.js**
-
-```javascript
-importScripts("https://unpkg.com/comlink/dist/umd/comlink.js");
-// importScripts("../../../dist/umd/comlink.js");
-
-const obj = {
-  counter: 0,
-  inc() {
-    this.counter++;
-  },
-};
-
-/**
- * When a connection is made into this shared worker, expose `obj`
- * via the connection `port`.
- */
-onconnect = function (event) {
-  const port = event.ports[0];
-
-  Comlink.expose(obj, port);
-};
-
-// Single line alternative:
-// onconnect = (e) => Comlink.expose(obj, e.ports[0]);
-```
-
-**For additional examples, please see the [docs/examples](./docs/examples) directory in the project.**
-
-## API
-
-### `Comlink.wrap(endpoint)` and `Comlink.expose(value, endpoint?)`
-
-Comlink’s goal is to make _exposed_ values from one thread available in the other. `expose` exposes `value` on `endpoint`, where `endpoint` is a [`postMessage`-like interface][endpoint].
-
-`wrap` wraps the _other_ end of the message channel and returns a proxy. The proxy will have all properties and functions of the exposed value, but access and invocations are inherently asynchronous. This means that a function that returns a number will now return _a promise_ for a number. **As a rule of thumb: If you are using the proxy, put `await` in front of it.** Exceptions will be caught and re-thrown on the other side.
-
-### `Comlink.transfer(value, transferables)` and `Comlink.proxy(value)`
-
-By default, every function parameter, return value and object property value is copied, in the sense of [structured cloning]. Structured cloning can be thought of as deep copying, but has some limitations. See [this table][structured clone table] for details.
-
-If you want a value to be transferred rather than copied — provided the value is or contains a [`Transferable`][transferable] — you can wrap the value in a `transfer()` call and provide a list of transferable values:
-
-```js
-const data = new Uint8Array([1, 2, 3, 4, 5]);
-await myProxy.someFunction(Comlink.transfer(data, [data.buffer]));
-```
-
-Lastly, you can use `Comlink.proxy(value)`. When using this Comlink will neither copy nor transfer the value, but instead send a proxy. Both threads now work on the same value. This is useful for callbacks, for example, as functions are neither structured cloneable nor transferable.
-
-```js
-myProxy.onready = Comlink.proxy((data) => {
-  /* ... */
-});
-```
-
-### Transfer handlers and event listeners
-
-It is common that you want to use Comlink to add an event listener, where the event source is on another thread:
-
-```js
-button.addEventListener("click", myProxy.onClick.bind(myProxy));
-```
-
-While this won’t throw immediately, `onClick` will never actually be called. This is because [`Event`][event] is neither structured cloneable nor transferable. As a workaround, Comlink offers transfer handlers.
-
-Each function parameter and return value is given to _all_ registered transfer handlers. If one of the event handler signals that it can process the value by returning `true` from `canHandle()`, it is now responsible for serializing the value to structured cloneable data and for deserializing the value. A transfer handler has be set up on _both sides_ of the message channel. Here’s an example transfer handler for events:
-
-```js
-Comlink.transferHandlers.set("EVENT", {
-  canHandle: (obj) => obj instanceof Event,
-  serialize: (ev) => {
-    return [
-      {
-        target: {
-          id: ev.target.id,
-          classList: [...ev.target.classList],
-        },
-      },
-      [],
-    ];
-  },
-  deserialize: (obj) => obj,
-});
-```
-
-Note that this particular transfer handler won’t create an actual `Event`, but just an object that has the `event.target.id` and `event.target.classList` property. Often, this is enough. If not, the transfer handler can be easily augmented to provide all necessary data.
-
-### `Comlink.releaseProxy`
-
-Every proxy created by Comlink has the `[releaseProxy]` method.
-Calling it will detach the proxy and the exposed object from the message channel, allowing both ends to be garbage collected.
-
-```js
-const proxy = Comlink.wrap(port);
-// ... use the proxy ...
-proxy[Comlink.releaseProxy]();
-```
-
-### `Comlink.createEndpoint`
-
-Every proxy created by Comlink has the `[createEndpoint]` method.
-Calling it will return a new `MessagePort`, that has been hooked up to the same object as the proxy that `[createEndpoint]` has been called on.
-
-```js
-const port = myProxy[Comlink.createEndpoint]();
-const newProxy = Comlink.wrap(port);
-```
-
-### `Comlink.windowEndpoint(window, context = self, targetOrigin = "*")`
-
-Windows and Web Workers have a slightly different variants of `postMessage`. If you want to use Comlink to communicate with an iframe or another window, you need to wrap it with `windowEndpoint()`.
-
-`window` is the window that should be communicate with. `context` is the `EventTarget` on which messages _from_ the `window` can be received (often `self`). `targetOrigin` is passed through to `postMessage` and allows to filter messages by origin. For details, see the documentation for [`Window.postMessage`](https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage).
-
-For a usage example, take a look at the non-worker examples in the `docs` folder.
-
-## TypeScript
-
-Comlink does provide TypeScript types. When you `expose()` something of type `T`, the corresponding `wrap()` call will return something of type `Comlink.Remote<T>`. While this type has been battle-tested over some time now, it is implemented on a best-effort basis. There are some nuances that are incredibly hard if not impossible to encode correctly in TypeScript’s type system. It _may_ sometimes be necessary to force a certain type using `as unknown as <type>`.
-
-## Node
-
-Comlink works with Node’s [`worker_threads`][worker_threads] module. Take a look at the example in the `docs` folder.
-
-[webworker]: https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API
-[umd]: https://github.com/umdjs/umd
-[transferable]: https://developer.mozilla.org/en-US/docs/Web/API/Transferable
-[messageport]: https://developer.mozilla.org/en-US/docs/Web/API/MessagePort
-[examples]: https://github.com/GoogleChromeLabs/comlink/tree/master/docs/examples
-[dist]: https://github.com/GoogleChromeLabs/comlink/tree/master/dist
-[delivrjs]: https://cdn.jsdelivr.net/
-[es6 proxy]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy
-[proxy-polyfill]: https://github.com/GoogleChrome/proxy-polyfill
-[endpoint]: src/protocol.ts
-[structured cloning]: https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm
-[structured clone table]: structured-clone-table.md
-[event]: https://developer.mozilla.org/en-US/docs/Web/API/Event
-[worker_threads]: https://nodejs.org/api/worker_threads.html
-
-## Additional Resources
-
-- [Simplify Web Worker code with Comlink](https://davidea.st/articles/comlink-simple-web-worker)
-
----
-
-License Apache-2.0