open-index/open-npm huggingface dataset:
npm package: @supabase/pg-admin-js
Description: JS SDK for managing your PostgreSQL Database.
Latest version: 0.0.2

# pg-admin-js

JS SDK for managing your PostgreSQL Database.

## Install

```sh
$ npm install ...
```

## Usage

```js
var pgAdmin = require('pg-admin-js')
var connection = {
  user: 'postgres',
  password: '123',
  host: 'localhost',
  port: 5432,
  database: 'thedb',
}
pgAdmin.toJSON(connection, 'public')
  .then(({ tables, views, constraints, sequences, counts }) => {
    // handle json object
    console.log('tables', tables)
    console.log('views', views)
    console.log('constraints', constraints)
    console.log('sequences', sequences)
    console.log('counts', counts)
  })
  .catch(function(error) {
    // handle error
  })
```

## License

MIT
npm package: @supabase/ssr
Description: Use the Supabase JavaScript library in popular server-side rendering (SSR) frameworks.
Author: Supabase, Inc.
Latest version: 0.10.2

# Supabase clients for use in SSR frameworks

> **Package Consolidation Notice**: This package replaces the deprecated `@supabase/auth-helpers-*` packages. All framework-specific auth-helpers packages have been consolidated into `@supabase/ssr` for better maintenance and consistency.

## Overview

This package provides a framework-agnostic way to use the [Supabase JavaScript library](https://supabase.com/docs/reference/javascript/introduction) in server-side rendering (SSR) frameworks.

## Installation

```bash
npm i @supabase/ssr
```

## Deprecated Packages

The following packages have been deprecated and consolidated into `@supabase/ssr`:

- `@supabase/auth-helpers-nextjs` → Use `@supabase/ssr`
- `@supabase/auth-helpers-react` → Use `@supabase/ssr`
- `@supabase/auth-helpers-remix` → Use `@supabase/ssr`
- `@supabase/auth-helpers-sveltekit` → Use `@supabase/ssr`

If you're currently using any of these packages, please update your dependencies to use `@supabase/ssr` directly.

## Documentation

Please refer to the [official server-side rendering guides](https://supabase.com/docs/guides/auth/server-side) for the latest best practices on using this package in your SSR framework of choice.

## Known patterns and limitations

### `getSession()` vs `getUser()` vs `getClaims()`

`getSession()` returns the session directly from cookies — no network call is
made. The user object it contains is **not verified by the Auth server** and
must not be used for authorization decisions; a malicious client could craft a
cookie with a spoofed user ID. **Do not use `getSession()` for authorization decisions.**

`getClaims()` validates the access token either locally (using the project's
JWKS endpoint for asymmetric keys) or by calling the Auth server, and returns
the verified JWT claims. Use it when you need to gate access to resources but
don't need a fresh user record from the database.

`getUser()` contacts the Supabase Auth server on every call and returns the
most up-to-date user record, including any changes made since the token was
issued. Use it when you need fresh user data (e.g. checking current roles,
email, or whether the session is still active server-side).

### Concurrent requests with the same expired session

Supabase refresh tokens are single-use. If two requests arrive simultaneously
with the same expired session cookie (e.g. from two browser tabs opening at
the same time), both will attempt a token refresh. The second request's
refresh will fail because the token was already consumed by the first. The
second request will receive `session: null` until the browser syncs the
updated cookie from the first response.

The **middleware pattern** mitigates this for the common case: middleware runs
once per navigation and refreshes the session before the page renders, so
subsequent requests within the same navigation see a valid token. For parallel
requests (e.g. parallel `fetch()` calls from the client), handle `null`
sessions gracefully and retry or re-authenticate as needed.
npm package: @supacool/sv
Description: sv add-on for @supacool/sv
Latest version: 0.1.2

# [sv](https://svelte.dev/docs/cli/overview) community add-on: `@supacool/sv`

> [!IMPORTANT]
> Svelte maintainers have not reviewed community add-ons for malicious code. Use at your discretion

## Usage

To install the add-on, run:

```shell
npx sv add "@supacool"
```

## What you get

- A nice message, check it out!
npm package: @supadata/langchain-js
Description: Supadata document loader integration for LangChain JS
Author: Mudassir
Latest version: 0.1.0

# Supadata LangChain JS Loader

Supadata document loader integration for LangChain JS.

This package provides a `SupadataLoader` that wraps the official `@supadata/js` SDK and exposes it as a LangChain `BaseDocumentLoader`.

Supported operations:

- Transcript: fetch transcript for a supported social media video/post URL.
- Metadata: fetch structured metadata for a supported social media video/post URL.

Supported URLs are video/post URLs from: YouTube, TikTok, Instagram, Facebook, Twitter/X.

Set your Supadata API key:

```bash
export SUPADATA_API_KEY="your_api_key_here"
```

## Usage

```ts
import { SupadataLoader } from "@supadata/langchain-js";

const loader = new SupadataLoader({
  apiKey: process.env.SUPADATA_API_KEY,
});

const docs = await loader.load({
  url: "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
  operation: "transcript",
  lang: "en",
  text: true,
  mode: "auto",
});

console.log(docs[0].pageContent);
console.log(docs[0].metadata);
```

### Metadata example

```ts
import { SupadataLoader } from "@supadata/langchain-js";

const loader = new SupadataLoader({
  apiKey: process.env.SUPADATA_API_KEY,
});

const docs = await loader.load({
  url: "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
  operation: "metadata",
});

console.log(docs[0].pageContent);
```

## API

```ts
type SupadataOperation = "metadata" | "transcript";

type SupadataTranscriptMode = "native" | "auto" | "generate";

interface SupadataLoaderInit {
  apiKey?: string;
}

interface SupadataLoaderLoadInput {
  url: string;
  operation?: SupadataOperation;
  lang?: string;
  text?: boolean;
  mode?: SupadataTranscriptMode;
  params?: Record<string, unknown>;
}

class SupadataLoader extends BaseDocumentLoader {
  constructor(init?: SupadataLoaderInit);

  load(input: SupadataLoaderLoadInput): Promise<Document[]>;
}
```
npm package: @supafeed/sdk
Description: Drop-in feedback widget with AI-powered follow-up conversations
Author: SupaFeed
Latest version: 0.1.2

# @supafeed/sdk

Drop-in feedback widget for web apps. It launches a bottom-corner feedback UI,
runs a short conversational flow, and sends sessions to the SupaFeed backend.

## Install

```bash
npm install @supafeed/sdk
```

## Quick start

```ts
import { init } from "@supafeed/sdk";

init({
  apiKey: "ff_live_xxx",
  position: "bottom-right",
});
```

The widget theme is resolved server-side from your SupaFeed organization settings
using the API key. Configure styling in the SupaFeed dashboard.

## API

- `init(config)` mounts the widget and returns the instance.
- `destroy()` unmounts the widget and cleans up all listeners.

## React provider usage

```tsx
import { SupaFeedProvider } from "@supafeed/sdk/react";

export function AppProviders({ children }: { children: React.ReactNode }) {
  return (
    <SupaFeedProvider
      config={{
        apiKey: "ff_live_xxx",
      }}
    >
      {children}
    </SupaFeedProvider>
  );
}
```

### Config

- `apiKey` (`string`, required): Your SupaFeed API key.
- `position` (`"bottom-right" | "bottom-left"`): trigger placement.
- `user` (`UserInfo`, optional): metadata about the current user.

### Pass user info

```tsx
<SupaFeedProvider
  config={{
    apiKey: "ff_live_xxx",
    user: {
      id: currentUser.id,
      email: currentUser.email,
      name: currentUser.name,
    },
  }}
>
  {children}
</SupaFeedProvider>
```