open-index/open-npm huggingface dataset:
npm package: @prisma/engines-version
Description: This package exports the Prisma Engines version to be downloaded from Prisma CDN.
Author: Tim Suchanek
Latest version: 7.8.0-1.7b80cc56c645c6e03c7541474e6a7c8d91b70d4e

# `@prisma/engines-version`

This package exports the Prisma Engines version to be downloaded from Prisma CDN.

⚠️ **Warning**: This package is intended for Prisma's internal use.
Its release cycle does not follow SemVer, which means we might release breaking changes (change APIs, remove functionality) without any prior warning.

See its companion, [`@prisma/engines` npm package](https://www.npmjs.com/package/@prisma/engines).
npm package: @prisma/mini-proxy
Description: This package is intended for Prisma's internal use.
Latest version: 0.9.5

# mini-proxy

[![npm version](https://img.shields.io/npm/v/@prisma/mini-proxy.svg?style=flat)](https://www.npmjs.com/package/@prisma/mini-proxy)

> ⚠️ **Warning**: This package is intended for Prisma's internal use.
> Its release cycle does not follow SemVer, which means we might release breaking changes (change APIs, remove functionality) without any prior warning.

This package is used by [Prisma Client](https://github.com/prisma/prisma) for testing purposes only.

Docs are currently private and accessible on [GitHub](https://github.com/prisma/mini-proxy/blob/master/docs/README.md).
npm package: @prisma/ppg-tunnel
Description: A CLI for tunneling TCP traffic to Prisma Postgres
Latest version: 0.4.0

# Prisma Postgres TCP Tunnel

> [!WARNING]  
> **This package has been deprecated in favor of [direct TCP connections](https://www.prisma.io/docs/postgres/database/direct-connections)**, please use those if you want to interact with Prisma Postgres with another library/tool than Prisma ORM.

`@prisma/ppg-tunnel` is an authentication proxy for [Prisma Postgres](https://www.prisma.io/postgres). It uses a Prisma Data Platform API key to connect to a secure proxy while opening a local TCP server for client connections. This enables secure connections from local tools while automatically routing traffic to and authenticating with the correct Prisma Postgres instance.

## Usage

### Standard mode

In this mode, the tunnel opens a connection to the database and waits for client tooling to connect.

The tunnel expects either a `PDP_API_KEY` or `DATABASE_URL` environment variable to be set. `PDP_API_KEY` is expected to be a Prisma Data Platform API key. `DATABASE_URL` is expected to be Prisma Postgres connection string. If both are set, `PDP_API_KEY` has precedence.

To start the proxy server, run the following command:

```bash
npx @prisma/ppg-tunnel
```

This will start the tunnel on a randomly assigned TCP port for client connections. The proxy handles authentication for you, so any database credentials are allowed. The tunnel will also handle encryption of traffic, so clients should be set to not require SSL.

By default, the tunnel will listen on 127.0.0.1 and a randomly assigned port. Since the tunnel provides access to your Prisma Postgres database, it should only be exposed to a trusted network. You can override the default host and port bindings with the `--host` and `--port` flags:

```bash
npx @prisma/ppg-tunnel --host 0.0.0.0 --port 5432
```

### Interactive mode

This mode can help upgrade a Prisma Postgres Early Access database to a fresh Prisma Postgres General Availability database:

```bash
npx @prisma/ppg-tunnel migrate-from-ea
```

The tunnel will ask for a `DATABASE_URL` or API key, then use `pg_dump` to download the early-access database to a file in the current working directory. When the dump is finished, the tunnel will ask for an API key for the new Prisma Postgres database, and use `pg_restore` to migrate the dump file.

Interactive mode does not accept arguments or read API keys from the environment. It requires version 16 of the [PostgreSQL client tools](https://www.postgresql.org/docs/16/reference-client.html). You can read more about migrating from an early-access database in [the official documentation](https://pris.ly/ppg-upgrade-from-ea).
npm package: @prisma/prisma-fmt-wasm
Description: The WASM package for prisma-fmt
Author: Prisma
Latest version: 4.17.0-16.27eb2449f178cd9fe1a4b892d732cc4795f75085

# @prisma/prisma-fmt-wasm

[![Publish pipeline](https://github.com/prisma/prisma-engines/actions/workflows/publish-prisma-fmt-wasm.yml/badge.svg)](https://github.com/prisma/prisma-engines/actions/workflows/publish-prisma-fmt-wasm.yml)
[![npm package](https://img.shields.io/npm/v/@prisma/prisma-fmt-wasm/latest)](https://www.npmjs.com/package/@prisma/prisma-fmt-wasm)
[![install size](https://packagephobia.com/badge?p=@prisma/prisma-fmt-wasm)](https://packagephobia.com/result?p=@prisma/prisma-fmt-wasm)

This directory only contains build logic to package the `prisma-fmt` engine
into a Node package as a WASM module. All the functionality is implemented in
other parts of prisma-engines.

The published NPM package is internal to Prisma. Its API will break without prior warning.

## Example

```bash
node -e "const prismaFmt = require('@prisma/prisma-fmt-wasm'); console.log(prismaFmt.version())"
```

## Components

- The GitHub Actions workflow that publishes the NPM package: https://github.com/prisma/prisma-engines/blob/main/.github/workflows/publish-prisma-fmt-wasm.yml
    - It is triggered from the https://github.com/prisma/engines-wrapper publish action.
- The [Rust source code](https://github.com/prisma/prisma-engines/tree/main/prisma-fmt-wasm/src) for the wasm module
- The [nix build definition](https://github.com/prisma/prisma-engines/blob/main/prisma-fmt-wasm/default.nix)
    - It gives us a fully reproducible, thoroughly described build process and environment. The alternative would be a bash script with installs through `rustup`, `cargo install` and `apt`, with underspecified system dependencies and best-effort version pinning.
    - You can read more about nix on [nix.dev](https://nix.dev/) and the [official website](https://nixos.org/).

## Local Dev with Language-Tools
When implementing features for `language-tools` in `prisma-engines`, to sync with your local dev environment for the `language-server`, one can do the following:

### On first setup
```
# Install the latest Rust version with `rustup`
# or update the latest Rust version with `rustup`
rustup update
rustup target add wasm32-unknown-unknown
cargo update -p wasm-bindgen
# Check the version defined in `prisma-fmt-wasm/cargo.toml` for `wasm-bindgen` and replace `version` below:
cargo install -f wasm-bindgen-cli@version
```

### On Changes

```bash
./prisma-fmt-wasm/scripts/update-fmt-wasm.sh
```

This script has the following expectations:
- `language-tools` is in the same dir as `prisma-engines`
  - i.e. `dir/{prisma-engines,language-tools}`
- it's run in the `prisma-engines` root folder
npm package: @prisma/prisma-schema-wasm
Description: The Wasm package for prisma-fmt
Author: Prisma
Latest version: 7.8.0-1.7b80cc56c645c6e03c7541474e6a7c8d91b70d4e

# @prisma/prisma-schema-wasm

[![Publish pipeline](https://github.com/prisma/prisma-engines/actions/workflows/publish-prisma-schema-wasm.yml/badge.svg)](https://github.com/prisma/prisma-engines/actions/workflows/publish-prisma-schema-wasm.yml)
[![npm package](https://img.shields.io/npm/v/@prisma/prisma-schema-wasm/latest)](https://www.npmjs.com/package/@prisma/prisma-schema-wasm)
[![install size](https://packagephobia.com/badge?p=@prisma/prisma-schema-wasm)](https://packagephobia.com/result?p=@prisma/prisma-schema-wasm)

This directory only contains build logic to package the `prisma-fmt` engine
into a Node package as a Wasm module. All the functionality is implemented in
other parts of prisma-engines.

The published NPM package is internal to Prisma. Its API will break without prior warning.

## Example

```bash
node -e "const prismaSchema = require('@prisma/prisma-schema-wasm'); console.log(prismaSchema.version())"
```

## Components

- The GitHub Actions workflow that publishes the NPM package: https://github.com/prisma/prisma-engines/blob/main/.github/workflows/publish-prisma-schema-wasm.yml
    - It is triggered from the https://github.com/prisma/engines-wrapper publish action.
- The [Rust source code](https://github.com/prisma/prisma-engines/tree/main/prisma-schema-wasm/src) for the wasm module
- The [nix build definition](https://github.com/prisma/prisma-engines/blob/main/prisma-schema-wasm/default.nix)
    - It gives us a fully reproducible, thoroughly described build process and environment. The alternative would be a bash script with installs through `rustup`, `cargo install` and `apt`, with underspecified system dependencies and best-effort version pinning.
    - You can read more about nix on [nix.dev](https://nix.dev/) and the [official website](https://nixos.org/).

## Local Dev with Language-Tools
When implementing features for `language-tools` in `prisma-engines`, to sync with your local dev environment for the `language-server`, one can do the following:

### On first setup
```
# Install the latest Rust version with `rustup`
# or update the latest Rust version with `rustup`
rustup update
rustup target add wasm32-unknown-unknown
cargo update -p wasm-bindgen
# Check the version defined in `prisma-schema-wasm/cargo.toml` for `wasm-bindgen` and replace `version` below:
cargo install -f wasm-bindgen-cli@version
```

### On Changes

```bash
./prisma-schema-wasm/scripts/update-schema-wasm.sh
```

This script has the following expectations:
- `language-tools` is in the same dir as `prisma-engines`
  - i.e. `dir/{prisma-engines,language-tools}`
- it's run in the `prisma-engines` root folder