@hasna/connectors 1.3.24 → 1.3.25

package/connectors/connect-yousign/node_modules/bun-types/docs/pm/scopes-registries.mdx

@@ -1,35 +0,0 @@
----
-title: "Scopes and registries"
-description: "Configure private registries and scoped packages"
----
-
-The default registry is `registry.npmjs.org`. This can be globally configured in `bunfig.toml`:
-
-```toml bunfig.toml icon="settings"
-[install]
-# set default registry as a string
-registry = "https://registry.npmjs.org"
-# set a token
-registry = { url = "https://registry.npmjs.org", token = "123456" }
-# set a username/password
-registry = "https://username:password@registry.npmjs.org"
-```
-
-To configure a private registry scoped to a particular organization:
-
-```toml bunfig.toml icon="settings"
-[install.scopes]
-# registry as string
-"@myorg1" = "https://username:password@registry.myorg.com/"
-
-# registry with username/password
-# you can reference environment variables
-"@myorg2" = { username = "myusername", password = "$NPM_PASS", url = "https://registry.myorg.com/" }
-
-# registry with token
-"@myorg3" = { token = "$npm_token", url = "https://registry.myorg.com/" }
-```
-
-### `.npmrc`
-
-Bun also reads `.npmrc` files, [learn more](/docs/pm/npmrc).

package/connectors/connect-yousign/node_modules/bun-types/docs/pm/security-scanner-api.mdx

@@ -1,95 +0,0 @@
----
-title: Security Scanner API
-description:
----
-
-Bun's package manager can scan packages for security vulnerabilities before installation, helping protect your applications from supply chain attacks and known vulnerabilities.
-
----
-
-## Quick Start
-
-Configure a security scanner in your `bunfig.toml`:
-
-```toml bunfig.toml icon="settings"
-[install.security]
-scanner = "@acme/bun-security-scanner"
-```
-
-When configured, Bun will:
-
-- Scan all packages before installation
-- Display security warnings and advisories
-- Cancel installation if critical vulnerabilities are found
-- Automatically disable auto-install for security
-
----
-
-## How It Works
-
-Security scanners analyze packages during `bun install`, `bun add`, and other package operations. They can detect:
-
-- Known security vulnerabilities (CVEs)
-- Malicious packages
-- License compliance issues
-- ...and more!
-
-### Security Levels
-
-Scanners report issues at two severity levels:
-
-- **`fatal`** - Installation stops immediately, exits with non-zero code
-- **`warn`** - In interactive terminals, prompts to continue; in CI, exits immediately
-
----
-
-## Using Pre-built Scanners
-
-Many security companies publish Bun security scanners as npm packages that you can install and use immediately.
-
-### Installing a Scanner
-
-Install a security scanner from npm:
-
-```bash terminal icon="terminal"
-bun add -d @acme/bun-security-scanner
-```
-
-<Note>
-  Consult your security scanner's documentation for their specific package name and installation instructions. Most
-  scanners will be installed with `bun add`.
-</Note>
-
-### Configuring the Scanner
-
-After installation, configure it in your `bunfig.toml`:
-
-```toml bunfig.toml icon="settings"
-[install.security]
-scanner = "@acme/bun-security-scanner"
-```
-
-### Enterprise Configuration
-
-Some enterprise scanners might support authentication and/or configuration through environment variables:
-
-```bash terminal icon="terminal"
-# This might go in ~/.bashrc, for example
-export SECURITY_API_KEY="your-api-key"
-
-# The scanner will now use these credentials automatically
-bun install
-```
-
-Consult your security scanner's documentation to learn which environment variables to set and if any additional configuration is required.
-
-### Authoring your own scanner
-
-For a complete example with tests and CI setup, see the official template:
-[github.com/oven-sh/security-scanner-template](https://github.com/oven-sh/security-scanner-template)
-
-## Related
-
-- [Configuration (bunfig.toml)](/docs/runtime/bunfig#install-security-scanner)
-- [Package Manager](/docs/installation)
-- [Security Scanner Template](https://github.com/oven-sh/security-scanner-template)

package/connectors/connect-yousign/node_modules/bun-types/docs/pm/workspaces.mdx

@@ -1,115 +0,0 @@
----
-title: "Workspaces"
-description: "Develop complex monorepos with multiple independent packages"
----
-
-Bun supports [`workspaces`](https://docs.npmjs.com/cli/v9/using-npm/workspaces?v=true#description) in `package.json`. Workspaces make it easy to develop complex software as a _monorepo_ consisting of several independent packages.
-
-It's common for a monorepo to have the following structure:
-
-```txt File Tree icon="folder-tree"
-<root>
-├── README.md
-├── bun.lock
-├── package.json
-├── tsconfig.json
-└── packages
-    ├── pkg-a
-    │   ├── index.ts
-    │   ├── package.json
-    │   └── tsconfig.json
-    ├── pkg-b
-    │   ├── index.ts
-    │   ├── package.json
-    │   └── tsconfig.json
-    └── pkg-c
-        ├── index.ts
-        ├── package.json
-        └── tsconfig.json
-```
-
-In the root `package.json`, the `"workspaces"` key is used to indicate which subdirectories should be considered packages/workspaces within the monorepo. It's conventional to place all the workspace in a directory called `packages`.
-
-```json package.json icon="file-json"
-{
-  "name": "my-project",
-  "version": "1.0.0",
-  "workspaces": ["packages/*"],
-  "devDependencies": {
-    "example-package-in-monorepo": "workspace:*"
-  }
-}
-```
-
-<Note>
-  **Glob support** — Bun supports full glob syntax in `"workspaces"`, including negative patterns (e.g.
-  `!**/excluded/**`). See [here](/docs/runtime/glob#supported-glob-patterns) for a comprehensive list of supported syntax.
-</Note>
-
-```json package.json icon="file-json"
-{
-  "name": "my-project",
-  "version": "1.0.0",
-  "workspaces": ["packages/**", "!packages/**/test/**", "!packages/**/template/**"]
-}
-```
-
-Each workspace has it's own `package.json`. When referencing other packages in the monorepo, semver or workspace protocols (e.g. `workspace:*`) can be used as the version field in your `package.json`.
-
-```json packages/pkg-a/package.json icon="file-json"
-{
-  "name": "pkg-a",
-  "version": "1.0.0",
-  "dependencies": {
-    "pkg-b": "workspace:*"
-  }
-}
-```
-
-`bun install` will install dependencies for all workspaces in the monorepo, de-duplicating packages if possible. If you only want to install dependencies for specific workspaces, you can use the `--filter` flag.
-
-```bash
-# Install dependencies for all workspaces starting with `pkg-` except for `pkg-c`
-bun install --filter "pkg-*" --filter "!pkg-c"
-
-# Paths can also be used. This is equivalent to the command above.
-bun install --filter "./packages/pkg-*" --filter "!pkg-c" # or --filter "!./packages/pkg-c"
-```
-
-When publishing, `workspace:` versions are replaced by the package's `package.json` version,
-
-```
-"workspace:*" -> "1.0.1"
-"workspace:^" -> "^1.0.1"
-"workspace:~" -> "~1.0.1"
-```
-
-Setting a specific version takes precedence over the package's `package.json` version,
-
-```
-"workspace:1.0.2" -> "1.0.2" // Even if current version is 1.0.1
-```
-
-Workspaces have a couple major benefits.
-
-- **Code can be split into logical parts.** If one package relies on another, you can simply add it as a dependency in `package.json`. If package `b` depends on `a`, `bun install` will install your local `packages/a` directory into `node_modules` instead of downloading it from the npm registry.
-- **Dependencies can be de-duplicated.** If `a` and `b` share a common dependency, it will be _hoisted_ to the root `node_modules` directory. This reduces redundant disk usage and minimizes "dependency hell" issues associated with having multiple versions of a package installed simultaneously.
-- **Run scripts in multiple packages.** You can use the [`--filter` flag](/docs/pm/filter) to easily run `package.json` scripts in multiple packages in your workspace, , or `--workspaces` to run scripts across all workspaces.
-
-## Share versions with Catalogs
-
-When many packages need the same dependency versions, catalogs let you define
-those versions once in the root `package.json` and reference them from your
-workspaces using the `catalog:` protocol. Updating the catalog automatically
-updates every package that references it. See
-[Catalogs](/docs/pm/catalogs) for details.
-
-<Note>
-⚡️ **Speed** — Installs are fast, even for big monorepos. Bun installs the [Remix](https://github.com/remix-run/remix) monorepo in about `500ms` on Linux.
-
-- 28x faster than `npm install`
-- 12x faster than `yarn install` (v1)
-- 8x faster than `pnpm install`
-
-<Image src="https://user-images.githubusercontent.com/709451/212829600-77df9544-7c9f-4d8d-a984-b2cd0fd2aa52.png" />
-</Note>

package/connectors/connect-yousign/node_modules/bun-types/docs/project/benchmarking.mdx

@@ -1,296 +0,0 @@
----
-title: Benchmarking
-description: How to benchmark Bun
----
-
-Bun is designed for speed. Hot paths are extensively profiled and benchmarked. The source code for all of Bun's public benchmarks can be found in the [`/bench`](https://github.com/oven-sh/bun/tree/main/bench) directory of the Bun repo.
-
-## Measuring time
-
-To precisely measure time, Bun offers two runtime APIs functions:
-
-1. The Web-standard [`performance.now()`](https://developer.mozilla.org/en-US/docs/Web/API/Performance/now) function
-2. `Bun.nanoseconds()` which is similar to `performance.now()` except it returns the current time since the application started in nanoseconds. You can use `performance.timeOrigin` to convert this to a Unix timestamp.
-
-## Benchmarking tools
-
-When writing your own benchmarks, it's important to choose the right tool.
-
-- For microbenchmarks, a great general-purpose tool is [`mitata`](https://github.com/evanwashere/mitata).
-- For load testing, you _must use_ an HTTP benchmarking tool that is at least as fast as `Bun.serve()`, or your results will be skewed. Some popular Node.js-based benchmarking tools like [`autocannon`](https://github.com/mcollina/autocannon) are not fast enough. We recommend one of the following:
-  - [`bombardier`](https://github.com/codesenberg/bombardier)
-  - [`oha`](https://github.com/hatoo/oha)
-  - [`http_load_test`](https://github.com/uNetworking/uSockets/blob/master/examples/http_load_test.c)
-- For benchmarking scripts or CLI commands, we recommend [`hyperfine`](https://github.com/sharkdp/hyperfine).
-
-## Measuring memory usage
-
-Bun has two heaps. One heap is for the JavaScript runtime and the other heap is for everything else.
-
-### JavaScript heap stats
-
-The `bun:jsc` module exposes a few functions for measuring memory usage:
-
-```ts
-import { heapStats } from "bun:jsc";
-console.log(heapStats());
-```
-
-<Accordion title="View example statistics">
-
-```ts expandable icon="/icons/typescript.svg"
-{
-  heapSize: 1657575,
-  heapCapacity: 2872775,
-  extraMemorySize: 598199,
-  objectCount: 13790,
-  protectedObjectCount: 62,
-  globalObjectCount: 1,
-  protectedGlobalObjectCount: 1,
-  // A count of every object type in the heap
-  objectTypeCounts: {
-    CallbackObject: 25,
-    FunctionExecutable: 2078,
-    AsyncGeneratorFunction: 2,
-    'RegExp String Iterator': 1,
-    FunctionCodeBlock: 188,
-    ModuleProgramExecutable: 13,
-    String: 1,
-    UnlinkedModuleProgramCodeBlock: 13,
-    JSON: 1,
-    AsyncGenerator: 1,
-    Symbol: 1,
-    GetterSetter: 68,
-    ImportMeta: 10,
-    DOMAttributeGetterSetter: 1,
-    UnlinkedFunctionCodeBlock: 174,
-    RegExp: 52,
-    ModuleLoader: 1,
-    Intl: 1,
-    WeakMap: 4,
-    Generator: 2,
-    PropertyTable: 95,
-    'Array Iterator': 1,
-    JSLexicalEnvironment: 75,
-    UnlinkedFunctionExecutable: 2067,
-    WeakSet: 1,
-    console: 1,
-    Map: 23,
-    SparseArrayValueMap: 14,
-    StructureChain: 19,
-    Set: 18,
-    'String Iterator': 1,
-    FunctionRareData: 3,
-    JSGlobalLexicalEnvironment: 1,
-    Object: 481,
-    BigInt: 2,
-    StructureRareData: 55,
-    Array: 179,
-    AbortController: 2,
-    ModuleNamespaceObject: 11,
-    ShadowRealm: 1,
-    'Immutable Butterfly': 103,
-    Primordials: 1,
-    'Set Iterator': 1,
-    JSGlobalProxy: 1,
-    AsyncFromSyncIterator: 1,
-    ModuleRecord: 13,
-    FinalizationRegistry: 1,
-    AsyncIterator: 1,
-    InternalPromise: 22,
-    Iterator: 1,
-    CustomGetterSetter: 65,
-    Promise: 19,
-    WeakRef: 1,
-    InternalPromisePrototype: 1,
-    Function: 2381,
-    AsyncFunction: 2,
-    GlobalObject: 1,
-    ArrayBuffer: 2,
-    Boolean: 1,
-    Math: 1,
-    CallbackConstructor: 1,
-    Error: 2,
-    JSModuleEnvironment: 13,
-    WebAssembly: 1,
-    HashMapBucket: 300,
-    Callee: 3,
-    symbol: 37,
-    string: 2484,
-    Performance: 1,
-    ModuleProgramCodeBlock: 12,
-    JSSourceCode: 13,
-    JSPropertyNameEnumerator: 3,
-    NativeExecutable: 290,
-    Number: 1,
-    Structure: 1550,
-    SymbolTable: 108,
-    GeneratorFunction: 2,
-    'Map Iterator': 1
-  },
-  protectedObjectTypeCounts: {
-    CallbackConstructor: 1,
-    BigInt: 1,
-    RegExp: 2,
-    GlobalObject: 1,
-    UnlinkedModuleProgramCodeBlock: 13,
-    HashMapBucket: 2,
-    Structure: 41,
-    JSPropertyNameEnumerator: 1
-  }
-}
-```
-
-</Accordion>
-
-JavaScript is a garbage-collected language, not reference counted. It's normal and correct for objects to not be freed immediately in all cases, though it's not normal for objects to never be freed.
-
-To force garbage collection to run manually:
-
-```ts
-Bun.gc(true); // synchronous
-Bun.gc(false); // asynchronous
-```
-
-Heap snapshots let you inspect what objects are not being freed. You can use the `bun:jsc` module to take a heap snapshot and then view it with Safari or WebKit GTK developer tools. To generate a heap snapshot:
-
-```ts
-import { generateHeapSnapshot } from "bun";
-
-const snapshot = generateHeapSnapshot();
-await Bun.write("heap.json", JSON.stringify(snapshot, null, 2));
-```
-
-To view the snapshot, open the `heap.json` file in Safari's Developer Tools (or WebKit GTK)
-
-1. Open the Developer Tools
-2. Click "Timeline"
-3. Click "JavaScript Allocations" in the menu on the left. It might not be visible until you click the pencil icon to show all the timelines
-4. Click "Import" and select your heap snapshot JSON
-
-<Frame>
-  <img
-    src="https://user-images.githubusercontent.com/709451/204428943-ba999e8f-8984-4f23-97cb-b4e3e280363e.png"
-    alt="Importing a heap snapshot"
-  />
-</Frame>
-
-Once imported, you should see something like this:
-
-<Frame>
-  <img
-    alt="Viewing heap snapshot in Safari"
-    src="https://user-images.githubusercontent.com/709451/204429337-b0d8935f-3509-4071-b991-217794d1fb27.png"
-    caption="Viewing heap snapshot in Safari Dev Tools"
-  />
-</Frame>
-
-> The [web debugger](/docs/runtime/debugger#inspect) also offers the timeline feature which allows you to track and examine the memory usage of the running debug session.
-
-### Native heap stats
-
-Bun uses mimalloc for the other heap. To report a summary of non-JavaScript memory usage, set the `MIMALLOC_SHOW_STATS=1` environment variable. and stats will print on exit.
-
-```sh terminal icon="terminal"
-MIMALLOC_SHOW_STATS=1 bun script.js
-```
-
-```txt
-heap stats:    peak      total      freed    current       unit      count
-  reserved:   64.0 MiB   64.0 MiB      0       64.0 MiB                        not all freed!
- committed:   64.0 MiB   64.0 MiB      0       64.0 MiB                        not all freed!
-     reset:      0          0          0          0                            ok
-   touched:  128.5 KiB  128.5 KiB    5.4 MiB   -5.3 MiB                        ok
-  segments:      1          1          0          1                            not all freed!
--abandoned:      0          0          0          0                            ok
-   -cached:      0          0          0          0                            ok
-     pages:      0          0         53        -53                            ok
--abandoned:      0          0          0          0                            ok
- -extended:      0
- -noretire:      0
-     mmaps:      0
-   commits:      0
-   threads:      0          0          0          0                            ok
-  searches:     0.0 avg
-numa nodes:       1
-   elapsed:       0.068 s
-   process: user: 0.061 s, system: 0.014 s, faults: 0, rss: 57.4 MiB, commit: 64.0 MiB
-```
-
-## CPU profiling
-
-Profile JavaScript execution to identify performance bottlenecks with the `--cpu-prof` flag.
-
-```sh terminal icon="terminal"
-bun --cpu-prof script.js
-```
-
-This generates a `.cpuprofile` file you can open in Chrome DevTools (Performance tab → Load profile) or VS Code's CPU profiler.
-
-### Markdown output
-
-Use `--cpu-prof-md` to generate a markdown CPU profile, which is grep-friendly and designed for LLM analysis:
-
-```sh terminal icon="terminal"
-bun --cpu-prof-md script.js
-```
-
-Both `--cpu-prof` and `--cpu-prof-md` can be used together to generate both formats at once:
-
-```sh terminal icon="terminal"
-bun --cpu-prof --cpu-prof-md script.js
-```
-
-You can also trigger profiling via the `BUN_OPTIONS` environment variable:
-
-```sh terminal icon="terminal"
-BUN_OPTIONS="--cpu-prof-md" bun script.js
-```
-
-### Options
-
-```sh terminal icon="terminal"
-bun --cpu-prof --cpu-prof-name my-profile.cpuprofile script.js
-bun --cpu-prof --cpu-prof-dir ./profiles script.js
-```
-
-| Flag                         | Description                                                 |
-| ---------------------------- | ----------------------------------------------------------- |
-| `--cpu-prof`                 | Generate a `.cpuprofile` JSON file (Chrome DevTools format) |
-| `--cpu-prof-md`              | Generate a markdown CPU profile (grep/LLM-friendly)         |
-| `--cpu-prof-name <filename>` | Set output filename                                         |
-| `--cpu-prof-dir <dir>`       | Set output directory                                        |
-
-## Heap profiling
-
-Generate heap snapshots on exit to analyze memory usage and find memory leaks.
-
-```sh terminal icon="terminal"
-bun --heap-prof script.js
-```
-
-This generates a V8 `.heapsnapshot` file that can be loaded in Chrome DevTools (Memory tab → Load).
-
-### Markdown output
-
-Use `--heap-prof-md` to generate a markdown heap profile for CLI analysis:
-
-```sh terminal icon="terminal"
-bun --heap-prof-md script.js
-```
-
-<Note>If both `--heap-prof` and `--heap-prof-md` are specified, the markdown format is used.</Note>
-
-### Options
-
-```sh terminal icon="terminal"
-bun --heap-prof --heap-prof-name my-snapshot.heapsnapshot script.js
-bun --heap-prof --heap-prof-dir ./profiles script.js
-```
-
-| Flag                          | Description                                |
-| ----------------------------- | ------------------------------------------ |
-| `--heap-prof`                 | Generate a V8 `.heapsnapshot` file on exit |
-| `--heap-prof-md`              | Generate a markdown heap profile on exit   |
-| `--heap-prof-name <filename>` | Set output filename                        |
-| `--heap-prof-dir <dir>`       | Set output directory                       |