@hasna/connectors 1.3.31 → 1.3.33

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/ecosystem/upstash.mdx

@@ -1,87 +0,0 @@
----
-title: Bun Redis with Upstash
-sidebarTitle: Upstash with Bun
-mode: center
----
-
-[Upstash](https://upstash.com/) is a fully managed Redis database as a service. Upstash works with the Redis® API, which means you can use Bun's native Redis client to connect to your Upstash database.
-
-<Note>TLS is enabled by default for all Upstash Redis databases.</Note>
-
----
-
-<Steps>
-  <Step title="Create a new project">
-    Create a new project by running `bun init`:
-    
-    ```sh terminal icon="terminal"
-    bun init bun-upstash-redis
-    cd bun-upstash-redis
-    ```
-  </Step>
-  <Step title="Create an Upstash Redis database">
-    Go to the [Upstash dashboard](https://console.upstash.com/) and create a new Redis database. After completing the [getting started guide](https://upstash.com/docs/redis/overall/getstarted), you'll see your database page with connection information.
-
-    The database page displays two connection methods; HTTP and TLS. For Bun's Redis client, you need the **TLS** connection details. This URL starts with `rediss://`.
-
-    	<Frame>
-    		![Upstash Redis database page](https://bun.com/images/guides/upstash-1.png)
-    	</Frame>
-
-  </Step>
-  <Step title="Connect using Bun's Redis client">
-		You can connect to Upstash by setting environment variables with Bun's default `redis` client.
-
-    Set the `REDIS_URL` environment variable in your `.env` file using the Redis endpoint (not the REST URL):
-
-    ```ini .env icon="settings"
-    REDIS_URL=rediss://********@********.upstash.io:6379
-    ```
-
-    Bun's Redis client reads connection information from `REDIS_URL` by default:
-
-    ```ts index.ts icon="/icons/typescript.svg"
-    import { redis } from "bun";
-
-    // Reads from process.env.REDIS_URL automatically
-    await redis.set("counter", "0"); // [!code ++]
-    ```
-
-    Alternatively, you can create a custom client using `RedisClient`:
-
-    ```ts index.ts icon="/icons/typescript.svg"
-    import { RedisClient } from "bun";
-
-    const redis = new RedisClient(process.env.REDIS_URL); // [!code ++]
-    ```
-
-  </Step>
-	<Step title="Use the Redis client">
-		You can now use the Redis client to interact with your Upstash Redis database:
-
-    	```ts index.ts icon="/icons/typescript.svg"
-    	import { redis } from "bun";
-
-    	// Get a value
-    	let counter = await redis.get("counter");
-
-    	// Set a value if it doesn't exist
-    	if (!counter) {
-    		await redis.set("counter", "0");
-    	}
-
-    	// Increment the counter
-    	await redis.incr("counter");
-
-    	// Get the updated value
-    	counter = await redis.get("counter");
-    	console.log(counter);
-    	```
-    	```txt
-    	1
-    	```
-
-    	The Redis client automatically handles connections in the background. No need to manually connect or disconnect for basic operations.
-    </Step>
-
-</Steps>

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/ecosystem/vite.mdx

@@ -1,77 +0,0 @@
----
-title: Build a frontend using Vite and Bun
-sidebarTitle: "Vite with Bun"
-mode: center
----
-
-<Note>
-  You can use Vite with Bun, but many projects get faster builds & drop hundreds of dependencies by switching to [HTML
-  imports](/docs/bundler/html-static).
-</Note>
-
----
-
-Vite works out of the box with Bun. Get started with one of Vite's templates.
-
-```bash terminal icon="terminal"
-bun create vite my-app
-```
-
-```txt
-✔ Select a framework: › React
-✔ Select a variant: › TypeScript + SWC
-Scaffolding project in /path/to/my-app...
-```
-
----
-
-Then `cd` into the project directory and install dependencies.
-
-```bash terminal icon="terminal"
-cd my-app
-bun install
-```
-
----
-
-Start the development server with the `vite` CLI using `bunx`.
-
-The `--bun` flag tells Bun to run Vite's CLI using `bun` instead of `node`; by default Bun respects Vite's `#!/usr/bin/env node` [shebang line](<https://en.wikipedia.org/wiki/Shebang_(Unix)>).
-
-```bash terminal icon="terminal"
-bunx --bun vite
-```
-
----
-
-To simplify this command, update the `"dev"` script in `package.json` to the following.
-
-```json package.json icon="file-json"
-  "scripts": {
-    "dev": "vite", // [!code --]
-    "dev": "bunx --bun vite", // [!code ++]
-    "build": "vite build",
-    "serve": "vite preview"
-  },
-  // ...
-```
-
----
-
-Now you can start the development server with `bun run dev`.
-
-```bash terminal icon="terminal"
-bun run dev
-```
-
----
-
-The following command will build your app for production.
-
-```sh terminal icon="terminal"
-bunx --bun vite build
-```
-
----
-
-This is a stripped down guide to get you started with Vite + Bun. For more information, see the [Vite documentation](https://vite.dev/guide/).

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/html-rewriter/extract-links.mdx

@@ -1,71 +0,0 @@
----
-title: Extract links from a webpage using HTMLRewriter
-sidebarTitle: Extract links using HTMLRewriter
-mode: center
----
-
-## Extract links from a webpage
-
-Bun's [HTMLRewriter](/docs/runtime/html-rewriter) API can be used to efficiently extract links from HTML content. It works by chaining together CSS selectors to match the elements, text, and attributes you want to process. Here is an example of how to extract links from a webpage. You can pass `.transform` a `Response`, `Blob`, or `string`.
-
-```ts extract-links.ts icon="/icons/typescript.svg"
-async function extractLinks(url: string) {
-  const links = new Set<string>();
-  const response = await fetch(url);
-
-  const rewriter = new HTMLRewriter().on("a[href]", {
-    element(el) {
-      const href = el.getAttribute("href");
-      if (href) {
-        links.add(href);
-      }
-    },
-  });
-
-  // Wait for the response to be processed
-  await rewriter.transform(response).blob();
-  console.log([...links]); // ["https://bun.com", "/docs", ...]
-}
-
-// Extract all links from the Bun website
-await extractLinks("https://bun.com");
-```
-
----
-
-## Convert relative URLs to absolute
-
-When scraping websites, you often want to convert relative URLs (like `/docs`) to absolute URLs. Here's how to handle URL resolution:
-
-{/* prettier-ignore */}
-```ts extract-links.ts icon="/icons/typescript.svg"
-async function extractLinksFromURL(url: string) {
-  const response = await fetch(url);
-  const links = new Set<string>();
-
-  const rewriter = new HTMLRewriter().on("a[href]", {
-    element(el) {
-      const href = el.getAttribute("href");
-      if (href) {
-        // Convert relative URLs to absolute // [!code ++]
-        try { // [!code ++]
-          const absoluteURL = new URL(href, url).href; // [!code ++]
-          links.add(absoluteURL);
-        } catch { // [!code ++]
-          links.add(href); // [!code ++]
-        } // [!code ++]
-      }
-    },
-  });
-
-  // Wait for the response to be processed
-  await rewriter.transform(response).blob();
-  return [...links];
-}
-
-const websiteLinks = await extractLinksFromURL("https://example.com");
-```
-
----
-
-See [Docs > API > HTMLRewriter](/docs/runtime/html-rewriter) for complete documentation on HTML transformation with Bun.

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/html-rewriter/extract-social-meta.mdx

@@ -1,97 +0,0 @@
----
-title: Extract social share images and Open Graph tags
-sidebarTitle: OpenGraph tags
-mode: center
----
-
-## Extract social share images and Open Graph tags
-
-Bun's [HTMLRewriter](/docs/runtime/html-rewriter) API can be used to efficiently extract social share images and Open Graph metadata from HTML content. This is particularly useful for building link preview features, social media cards, or web scrapers. We can use HTMLRewriter to match CSS selectors to HTML elements, text, and attributes we want to process.
-
-```ts extract-social-meta.ts icon="/icons/typescript.svg"
-interface SocialMetadata {
-  title?: string;
-  description?: string;
-  image?: string;
-  url?: string;
-  siteName?: string;
-  type?: string;
-}
-
-async function extractSocialMetadata(url: string): Promise<SocialMetadata> {
-  const metadata: SocialMetadata = {};
-  const response = await fetch(url);
-
-  const rewriter = new HTMLRewriter()
-    // Extract Open Graph meta tags
-    .on('meta[property^="og:"]', {
-      element(el) {
-        const property = el.getAttribute("property");
-        const content = el.getAttribute("content");
-        if (property && content) {
-          // Convert "og:image" to "image" etc.
-          const key = property.replace("og:", "") as keyof SocialMetadata;
-          metadata[key] = content;
-        }
-      },
-    })
-    // Extract Twitter Card meta tags as fallback
-    .on('meta[name^="twitter:"]', {
-      element(el) {
-        const name = el.getAttribute("name");
-        const content = el.getAttribute("content");
-        if (name && content) {
-          const key = name.replace("twitter:", "") as keyof SocialMetadata;
-          // Only use Twitter Card data if we don't have OG data
-          if (!metadata[key]) {
-            metadata[key] = content;
-          }
-        }
-      },
-    })
-    // Fallback to regular meta tags
-    .on('meta[name="description"]', {
-      element(el) {
-        const content = el.getAttribute("content");
-        if (content && !metadata.description) {
-          metadata.description = content;
-        }
-      },
-    })
-    // Fallback to title tag
-    .on("title", {
-      text(text) {
-        if (!metadata.title) {
-          metadata.title = text.text;
-        }
-      },
-    });
-
-  // Process the response
-  await rewriter.transform(response).blob();
-
-  // Convert relative image URLs to absolute
-  if (metadata.image && !metadata.image.startsWith("http")) {
-    try {
-      metadata.image = new URL(metadata.image, url).href;
-    } catch {
-      // Keep the original URL if parsing fails
-    }
-  }
-
-  return metadata;
-}
-```
-
-```ts Example Usage icon="/icons/typescript.svg"
-// Example usage
-const metadata = await extractSocialMetadata("https://bun.com");
-console.log(metadata);
-// {
-//   title: "Bun — A fast all-in-one JavaScript runtime",
-//   description: "Bundle, transpile, install and run JavaScript & TypeScript projects — all in Bun. Bun is a fast all-in-one JavaScript runtime & toolkit designed for speed, complete with a bundler, test runner, and Node.js-compatible package manager.",
-//   image: "https://bun.com/share.jpg",
-//   type: "website",
-//   ...
-// }
-```

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/http/cluster.mdx

@@ -1,69 +0,0 @@
----
-title: Start a cluster of HTTP servers
-description: Run multiple HTTP servers concurrently via the "reusePort" option to share the same port across multiple processes
-sidebarTitle: Start a cluster of HTTP servers
-mode: center
----
-
-To run multiple HTTP servers concurrently, use the `reusePort` option in `Bun.serve()` which shares the same port across multiple processes.
-
-This automatically load balances incoming requests across multiple instances of Bun.
-
-```ts server.ts icon="/icons/typescript.svg"
-import { serve } from "bun";
-
-const id = Math.random().toString(36).slice(2);
-
-serve({
-  port: process.env.PORT || 8080,
-  development: false,
-
-  // Share the same port across multiple processes
-  // This is the important part!
-  reusePort: true,
-
-  async fetch(request) {
-    return new Response("Hello from Bun #" + id + "!\n");
-  },
-});
-```
-
----
-
-<Note>
-  **Linux only** &mdash; Windows and macOS ignore the `reusePort` option. This is an operating system limitation with
-  `SO_REUSEPORT`, unfortunately.
-</Note>
-
-After saving the file, start your servers on the same port.
-
-Under the hood, this uses the Linux `SO_REUSEPORT` and `SO_REUSEADDR` socket options to ensure fair load balancing across multiple processes. [Learn more about `SO_REUSEPORT` and `SO_REUSEADDR`](https://lwn.net/Articles/542629/)
-
-```ts cluster.ts icon="/icons/typescript.svg"
-import { spawn } from "bun";
-
-const cpus = navigator.hardwareConcurrency; // Number of CPU cores
-const buns = new Array(cpus);
-
-for (let i = 0; i < cpus; i++) {
-  buns[i] = spawn({
-    cmd: ["bun", "./server.ts"],
-    stdout: "inherit",
-    stderr: "inherit",
-    stdin: "inherit",
-  });
-}
-
-function kill() {
-  for (const bun of buns) {
-    bun.kill();
-  }
-}
-
-process.on("SIGINT", kill);
-process.on("exit", kill);
-```
-
----
-
-Bun has also implemented the `node:cluster` module, but this is a faster and more limited alternative.

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/http/fetch-unix.mdx

@@ -1,35 +0,0 @@
----
-title: fetch with unix domain sockets in Bun
-sidebarTitle: Fetch with unix domain sockets
-mode: center
----
-
-In Bun, the `unix` option in `fetch()` lets you send HTTP requests over a [unix domain socket](https://en.wikipedia.org/wiki/Unix_domain_socket).
-
-```ts fetch-unix.ts icon="/icons/typescript.svg"
-const unix = "/var/run/docker.sock";
-
-const response = await fetch("http://localhost/info", { unix });
-
-const body = await response.json();
-console.log(body); // { ... }
-```
-
----
-
-The `unix` option is a string that specifies the local file path to a unix domain socket. The `fetch()` function will use the socket to send the request to the server instead of using a TCP network connection. `https` is also supported by using the `https://` protocol in the URL instead of `http://`.
-
-To send a `POST` request to an API endpoint over a unix domain socket:
-
-```ts fetch-unix.ts icon="/icons/typescript.svg"
-const response = await fetch("https://hostname/a/path", {
-  unix: "/var/run/path/to/unix.sock",
-  method: "POST",
-  body: JSON.stringify({ message: "Hello from Bun!" }),
-  headers: {
-    "Content-Type": "application/json",
-  },
-});
-
-const body = await response.json();
-```

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/http/fetch.mdx

@@ -1,26 +0,0 @@
----
-title: Send an HTTP request using fetch
-sidebarTitle: Fetch with Bun
-mode: center
----
-
-Bun implements the Web-standard [`fetch`](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) API for sending HTTP requests. To send a simple `GET` request to a URL:
-
-```ts fetch.ts icon="/icons/typescript.svg"
-const response = await fetch("https://bun.com");
-const html = await response.text(); // HTML string
-```
-
----
-
-To send a `POST` request to an API endpoint.
-
-```ts fetch.ts icon="/icons/typescript.svg"
-const response = await fetch("https://bun.com/api", {
-  method: "POST",
-  body: JSON.stringify({ message: "Hello from Bun!" }),
-  headers: { "Content-Type": "application/json" },
-});
-
-const body = await response.json();
-```

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/http/file-uploads.mdx

@@ -1,97 +0,0 @@
----
-title: Upload files via HTTP using FormData
-sidebarTitle: Upload files via HTTP using FormData
-mode: center
----
-
-To upload files via HTTP with Bun, use the [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData) API. Let's start with an HTTP server that serves an HTML web form.
-
-```ts index.ts icon="/icons/typescript.svg"
-const server = Bun.serve({
-  port: 4000,
-  async fetch(req) {
-    const url = new URL(req.url);
-
-    // return index.html for root path
-    if (url.pathname === "/")
-      return new Response(Bun.file("index.html"), {
-        headers: {
-          "Content-Type": "text/html",
-        },
-      });
-
-    return new Response("Not Found", { status: 404 });
-  },
-});
-
-console.log(`Listening on http://localhost:${server.port}`);
-```
-
----
-
-We can define our HTML form in another file, `index.html`.
-
-```html index.html icon="file-code"
-<!DOCTYPE html>
-<html>
-  <head>
-    <meta charset="utf-8" />
-    <title>Form</title>
-  </head>
-  <body>
-    <form action="/action" method="post" enctype="multipart/form-data">
-      <input type="text" name="name" placeholder="Name" />
-      <input type="file" name="profilePicture" />
-      <input type="submit" value="Submit" />
-    </form>
-  </body>
-</html>
-```
-
----
-
-At this point, we can run the server and visit [`localhost:4000`](http://localhost:4000) to see our form.
-
-```bash
-bun run index.ts
-Listening on http://localhost:4000
-```
-
----
-
-Our form will send a `POST` request to the `/action` endpoint with the form data. Let's handle that request in our server.
-
-First we use the [`.formData()`](https://developer.mozilla.org/en-US/docs/Web/API/Request/formData) method on the incoming `Request` to asynchronously parse its contents to a `FormData` instance. Then we can use the [`.get()`](https://developer.mozilla.org/en-US/docs/Web/API/FormData/get) method to extract the value of the `name` and `profilePicture` fields. Here `name` corresponds to a `string` and `profilePicture` is a `Blob`.
-
-Finally, we write the `Blob` to disk using [`Bun.write()`](/docs/runtime/file-io#writing-files-bun-write).
-
-{/* prettier-ignore */}
-```ts index.ts icon="/icons/typescript.svg"
-const server = Bun.serve({
-  port: 4000,
-  async fetch(req) {
-    const url = new URL(req.url);
-
-    // return index.html for root path
-    if (url.pathname === "/")
-      return new Response(Bun.file("index.html"), {
-        headers: {
-          "Content-Type": "text/html",
-        },
-      });
-
-    // parse formdata at /action // [!code ++]
-    if (url.pathname === "/action") { // [!code ++]
-      const formdata = await req.formData(); // [!code ++]
-      const name = formdata.get("name"); // [!code ++]
-      const profilePicture = formdata.get("profilePicture"); // [!code ++]
-      if (!profilePicture) throw new Error("Must upload a profile picture."); // [!code ++]
-      // write profilePicture to disk // [!code ++]
-      await Bun.write("profilePicture.png", profilePicture); // [!code ++]
-      return new Response("Success"); // [!code ++]
-    } // [!code ++]
-
-    return new Response("Not Found", { status: 404 });
-  },
-});
-```

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/http/hot.mdx

@@ -1,28 +0,0 @@
----
-title: Hot reload an HTTP server
-sidebarTitle: Hot reload an HTTP server
-mode: center
----
-
-Bun supports the [`--hot`](/docs/runtime/watch-mode#hot-mode) flag to run a file with hot reloading enabled. When any module or file changes, Bun re-runs the file.
-
-```sh terminal icon="terminal"
-bun --hot run index.ts
-```
-
----
-
-Bun detects when you are running an HTTP server with `Bun.serve()`. It reloads your fetch handler when source files change, _without_ restarting the `bun` process. This makes hot reloads nearly instantaneous.
-
-<Note>
-Note that this doesn't reload the page on your browser.
-</Note>
- 
-```ts index.ts icon="/icons/typescript.svg"
-Bun.serve({
-  port: 3000,
-  fetch(req) {
-    return new Response("Hello world");
-  },
-});
-```

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/http/proxy.mdx

@@ -1,50 +0,0 @@
----
-title: Proxy HTTP requests using fetch()
-sidebarTitle: Proxy HTTP requests using fetch()
-mode: center
----
-
-In Bun, `fetch` supports sending requests through an HTTP or HTTPS proxy. This is useful on corporate networks or when you need to ensure a request is sent through a specific IP address.
-
-```ts proxy.ts icon="/icons/typescript.svg"
-await fetch("https://example.com", {
-  // The URL of the proxy server
-  proxy: "https://username:password@proxy.example.com:8080",
-});
-```
-
----
-
-The `proxy` option can be a URL string or an object with `url` and optional `headers`. The URL can include the username and password if the proxy requires authentication. It can be `http://` or `https://`.
-
----
-
-## Custom proxy headers
-
-To send custom headers to the proxy server (useful for proxy authentication tokens, custom routing, etc.), use the object format:
-
-```ts proxy-headers.ts icon="/icons/typescript.svg"
-await fetch("https://example.com", {
-  proxy: {
-    url: "https://proxy.example.com:8080",
-    headers: {
-      "Proxy-Authorization": "Bearer my-token",
-      "X-Proxy-Region": "us-east-1",
-    },
-  },
-});
-```
-
-The `headers` property accepts a plain object or a `Headers` instance. These headers are sent directly to the proxy server in `CONNECT` requests (for HTTPS targets) or in the proxy request (for HTTP targets).
-
-If you provide a `Proxy-Authorization` header, it will override any credentials specified in the proxy URL.
-
----
-
-## Environment variables
-
-You can also set the `$HTTP_PROXY` or `$HTTPS_PROXY` environment variable to the proxy URL. This is useful when you want to use the same proxy for all requests.
-
-```sh terminal icon="terminal"
-HTTPS_PROXY=https://username:password@proxy.example.com:8080 bun run index.ts
-```

package/connectors/connect-imessage/node_modules/bun-types/docs/guides/http/server.mdx

@@ -1,48 +0,0 @@
----
-title: Common HTTP server usage
-sidebarTitle: HTTP Server with Bun
-mode: center
----
-
-This starts an HTTP server listening on port `3000`. It demonstrates basic routing with a number of common responses and also handles POST data from standard forms or as JSON.
-
-See [`Bun.serve`](/docs/runtime/http/server) for details.
-
-```ts server.ts icon="/icons/typescript.svg"
-const server = Bun.serve({
-  async fetch(req) {
-    const path = new URL(req.url).pathname;
-
-    // respond with text/html
-    if (path === "/") return new Response("Welcome to Bun!");
-
-    // redirect
-    if (path === "/abc") return Response.redirect("/source", 301);
-
-    // send back a file (in this case, *this* file)
-    if (path === "/source") return new Response(Bun.file(import.meta.path));
-
-    // respond with JSON
-    if (path === "/api") return Response.json({ some: "buns", for: "you" });
-
-    // receive JSON data to a POST request
-    if (req.method === "POST" && path === "/api/post") {
-      const data = await req.json();
-      console.log("Received JSON:", data);
-      return Response.json({ success: true, data });
-    }
-
-    // receive POST data from a form
-    if (req.method === "POST" && path === "/form") {
-      const data = await req.formData();
-      console.log(data.get("someField"));
-      return new Response("Success");
-    }
-
-    // 404s
-    return new Response("Page not found", { status: 404 });
-  },
-});
-
-console.log(`Listening on ${server.url}`);
-```