void 0.10.12 → 0.20.0

package/skills/void/docs/node_modules/void/node_modules/better-auth/LICENSE.md

@@ -1,20 +0,0 @@
-The MIT License (MIT)
-Copyright (c) 2024 - present, Bereket Engida
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the “Software”), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
-DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
-ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
-DEALINGS IN THE SOFTWARE.

package/skills/void/docs/node_modules/void/node_modules/better-auth/README.md

@@ -1,32 +0,0 @@
-<div align="center">
-  <picture>
-    <source srcset="https://github.com/better-auth/better-auth/blob/main/banner-dark.png?raw=true" media="(prefers-color-scheme: dark)"/>
-    <source srcset="https://github.com/better-auth/better-auth/blob/main/banner-light.png?raw=true" media="(prefers-color-scheme: light)"/>
-    <img src="https://github.com/better-auth/better-auth/blob/main/banner-light.png?raw=true" alt="Better Auth Logo"/>
-  </picture>
-
-  [![npm](https://img.shields.io/npm/dm/better-auth?style=flat&colorA=000000&colorB=000000)](https://npm.chart.dev/better-auth?primary=neutral&gray=neutral&theme=dark)
-  [![npm version](https://img.shields.io/npm/v/better-auth.svg?style=flat&colorA=000000&colorB=000000)](https://www.npmjs.com/package/better-auth)
-  [![GitHub stars](https://img.shields.io/github/stars/better-auth/better-auth?style=flat&colorA=000000&colorB=000000)](https://github.com/better-auth/better-auth/stargazers)
-
-  <p>
-    <a href="https://discord.gg/better-auth">Discord</a>
-    ·
-    <a href="https://better-auth.com">Website</a>
-    ·
-    <a href="https://github.com/better-auth/better-auth/issues">Issues</a>
-  </p>
-</div>
-
-## Better Auth
-
-Better Auth is a framework-agnostic authentication (and authorization) framework for TypeScript. It provides a comprehensive set of features out of the box and includes a plugin ecosystem that simplifies adding advanced functionalities with minimal code in a short amount of time. Whether you need 2FA, multi-tenant support, or other complex features, it lets you focus on building your actual application instead of reinventing the wheel.
-
-## Getting Started
-
-```bash
-npm i better-auth
-```
-
-Read the [Installation Guide](https://better-auth.com/docs/installation) to
-learn more.

package/skills/void/docs/node_modules/void/node_modules/better-sqlite3/README.md

@@ -1,99 +0,0 @@
-# better-sqlite3 [![Build Status](https://github.com/JoshuaWise/better-sqlite3/actions/workflows/build.yml/badge.svg)](https://github.com/JoshuaWise/better-sqlite3/actions/workflows/build.yml?query=branch%3Amaster)
-
-The fastest and simplest library for SQLite in Node.js.
-
-- Full transaction support
-- High performance, efficiency, and safety
-- Easy-to-use synchronous API *(better concurrency than an asynchronous API... yes, you read that correctly)*
-- Support for user-defined functions, aggregates, virtual tables, and extensions
-- 64-bit integers *(invisible until you need them)*
-- Worker thread support *(for large/slow queries)*
-
-## Help this project stay strong! 💪
-
-`better-sqlite3` is used by thousands of developers and engineers on a daily basis. Long nights and weekends were spent keeping this project strong and dependable, with no ask for compensation or funding, until now. If your company uses `better-sqlite3`, ask your manager to consider supporting the project:
-
-- [Become a GitHub sponsor](https://github.com/sponsors/JoshuaWise)
-- [Become a backer on Patreon](https://www.patreon.com/joshuawise)
-- [Make a one-time donation on PayPal](https://www.paypal.me/joshuathomaswise)
-
-## How other libraries compare
-
-|   |select 1 row  `get()` |select 100 rows   `all()`  |select 100 rows `iterate()` 1-by-1|insert 1 row `run()`|insert 100 rows in a transaction|
-|---|---|---|---|---|---|
-|better-sqlite3|1x|1x|1x|1x|1x|
-|[sqlite](https://www.npmjs.com/package/sqlite) and [sqlite3](https://www.npmjs.com/package/sqlite3)|11.7x slower|2.9x slower|24.4x slower|2.8x slower|15.6x slower|
-
-> You can verify these results by [running the benchmark yourself](./docs/benchmark.md).
-
-## Installation
-
-```bash
-npm install better-sqlite3
-```
-
-> Requires a [currently supported Node.js](https://nodejs.org/en/about/previous-releases) version. Prebuilt binaries are available for [LTS versions](https://nodejs.org/en/about/previous-releases). If you have trouble installing, check the [troubleshooting guide](./docs/troubleshooting.md).
-
-## Usage
-
-```js
-const db = require('better-sqlite3')('foobar.db', options);
-
-const row = db.prepare('SELECT * FROM users WHERE id = ?').get(userId);
-console.log(row.firstName, row.lastName, row.email);
-```
-
-Though not required, [it is generally important to set the WAL pragma for performance reasons](https://github.com/WiseLibs/better-sqlite3/blob/master/docs/performance.md).
-
-```js
-db.pragma('journal_mode = WAL');
-```
-
-##### In ES6 module notation:
-
-```js
-import Database from 'better-sqlite3';
-const db = new Database('foobar.db', options);
-db.pragma('journal_mode = WAL');
-```
-
-## Why should I use this instead of [node-sqlite3](https://github.com/mapbox/node-sqlite3)?
-
-- `node-sqlite3` uses asynchronous APIs for tasks that are either CPU-bound or serialized. That's not only bad design, but it wastes tons of resources. It also causes [mutex thrashing](https://en.wikipedia.org/wiki/Resource_contention) which has devastating effects on performance.
-- `node-sqlite3` exposes low-level (C language) memory management functions. `better-sqlite3` does it the JavaScript way, allowing the garbage collector to worry about memory management.
-- `better-sqlite3` is simpler to use, and it provides nice utilities for some operations that are very difficult or impossible in `node-sqlite3`.
-- `better-sqlite3` is much faster than `node-sqlite3` in most cases, and just as fast in all other cases.
-
-#### When is this library not appropriate?
-
-In most cases, if you're attempting something that cannot be reasonably accomplished with `better-sqlite3`, it probably cannot be reasonably accomplished with SQLite in general. For example, if you're executing queries that take one second to complete, and you expect to have many concurrent users executing those queries, no amount of asynchronicity will save you from SQLite's serialized nature. Fortunately, SQLite is very *very* fast. With proper indexing, we've been able to achieve upward of 2000 queries per second with 5-way-joins in a 60 GB database, where each query was handling 5–50 kilobytes of real data.
-
-If you have a performance problem, the most likely causes are inefficient queries, improper indexing, or a lack of [WAL mode](./docs/performance.md)—not `better-sqlite3` itself. However, there are some cases where `better-sqlite3` could be inappropriate:
-
-- If you expect a high volume of concurrent reads each returning many megabytes of data (i.e., videos)
-- If you expect a high volume of concurrent writes (i.e., a social media site)
-- If your database's size is near the terabyte range
-
-For these situations, you should probably use a full-fledged RDBMS such as [PostgreSQL](https://www.postgresql.org/).
-
-## Upgrading
-
-Upgrading your `better-sqlite3` dependency can potentially introduce breaking changes, either in the `better-sqlite3` API (if you upgrade to a new [major version](https://semver.org/)), or between your existing database(s) and the underlying version of SQLite. Before upgrading, review:
-
-* [`better-sqlite3` release notes](https://github.com/WiseLibs/better-sqlite3/releases)
-* [SQLite release history](https://www.sqlite.org/changes.html)
-
-# Documentation
-
-- [API documentation](./docs/api.md)
-- [Performance](./docs/performance.md) (also see [benchmark results](./docs/benchmark.md))
-- [64-bit integer support](./docs/integer.md)
-- [Worker thread support](./docs/threads.md)
-- [Unsafe mode (advanced)](./docs/unsafe.md)
-- [SQLite compilation (advanced)](./docs/compilation.md)
-- [Contribution rules](./docs/contribution.md)
-- [Code of conduct](./docs/conduct.md)
-
-# License
-
-[MIT](./LICENSE)

package/skills/void/docs/node_modules/void/node_modules/blake3-jit/README.md

@@ -1,108 +0,0 @@
-# blake3-jit
-
-[![CI](https://github.com/Brooooooklyn/blake3-jit/actions/workflows/ci.yml/badge.svg)](https://github.com/Brooooooklyn/blake3-jit/actions/workflows/ci.yml)
-
-High-performance BLAKE3 implementation with runtime JIT WASM SIMD.
-
-## Features
-
-- **1.38 GB/s** peak throughput on large inputs
-- **Pure JS + JIT WASM SIMD** - no `.wasm` files to ship
-- All BLAKE3 modes: hash, keyed (MAC), derive_key
-- XOF (eXtendable Output Function) support
-- Zero dependencies, tree-shakeable
-
-## Installation
-
-```bash
-npm install blake3-jit
-```
-
-## Usage
-
-```typescript
-import { hash, createHasher, createKeyed, createDeriveKey } from "blake3-jit";
-
-// One-shot hashing
-const digest = hash(new Uint8Array([1, 2, 3]));
-
-// Incremental hashing
-const hasher = createHasher();
-hasher.update(chunk1);
-hasher.update(chunk2);
-const result = hasher.finalize();
-
-// Keyed hashing (MAC)
-const mac = createKeyed(key).update(message).finalize();
-
-// Key derivation
-const derived = createDeriveKey("my-app v1").update(material).finalize(32);
-```
-
-## API
-
-### One-shot Functions
-
-```typescript
-hash(input: Uint8Array, outputLength?: number): Uint8Array
-hashInto(input: Uint8Array, output: Uint8Array, outputLength?: number): void
-```
-
-### Incremental Hashing
-
-```typescript
-createHasher(): Hasher
-createKeyed(key: Uint8Array): Hasher    // 32-byte key for MAC
-createDeriveKey(context: string): Hasher // Key derivation
-
-class Hasher {
-  update(data: Uint8Array): this
-  finalize(outputLength?: number): Uint8Array
-  finalizeXof(): XofReader
-}
-
-class XofReader {
-  read(length: number): Uint8Array
-}
-```
-
-### SIMD Control
-
-```typescript
-warmupSimd(): boolean  // Pre-initialize WASM SIMD
-```
-
-## Architecture
-
-```
-blake3-jit
-├── JS Path (<4KB)      Pure JavaScript, SMI-optimized compress
-└── WASM SIMD (>=4KB)   4-way parallel, JIT-generated at runtime
-    ├── compress4x      Single block x 4 chunks
-    ├── compressChunks4x 16 blocks x 4 chunks batched
-    └── compressParent   Merkle tree merges
-```
-
-**Key optimizations:**
-
-- SMI variables force V8 32-bit integer ALU
-- Arena pattern: all buffers in WASM linear memory (zero GC)
-- Runtime WASM codegen eliminates `.wasm` file dependency
-
-## Benchmarks
-
-Compared against native Rust (`@napi-rs/blake-hash`):
-
-| Size | blake3-jit | @napi-rs  | Notes           |
-| ---- | ---------- | --------- | --------------- |
-| 96B  | 362 MB/s   | 149 MB/s  | **2.4x faster** |
-| 512B | 748 MB/s   | 521 MB/s  | **1.4x faster** |
-| 1KB  | 811 MB/s   | 701 MB/s  | **1.2x faster** |
-| 32KB | 1.36 GB/s  | 1.97 GB/s | native wins     |
-| 1MB  | 1.38 GB/s  | 2.06 GB/s | native wins     |
-
-**Pure JS beats native Rust for small inputs** due to FFI overhead.
-
-## License
-
-MIT

package/skills/void/docs/node_modules/void/node_modules/drizzle-arktype/README.md

@@ -1,51 +0,0 @@
-`drizzle-arktype` is a plugin for [Drizzle ORM](https://github.com/drizzle-team/drizzle-orm) that allows you to generate [arktype](https://arktype.io/) schemas from Drizzle ORM schemas.
-
-**Features**
-
-- Create a select schema for tables, views and enums.
-- Create insert and update schemas for tables.
-- Supports all dialects: PostgreSQL, MySQL and SQLite.
-
-# Usage
-
-```ts
-import { pgEnum, pgTable, serial, text, timestamp } from 'drizzle-orm/pg-core';
-import { createInsertSchema, createSelectSchema } from 'drizzle-arktype';
-import { type } from 'arktype';
-
-const users = pgTable('users', {
-	id: serial('id').primaryKey(),
-	name: text('name').notNull(),
-	email: text('email').notNull(),
-	role: text('role', { enum: ['admin', 'user'] }).notNull(),
-	createdAt: timestamp('created_at').notNull().defaultNow(),
-});
-
-// Schema for inserting a user - can be used to validate API requests
-const insertUserSchema = createInsertSchema(users);
-
-// Schema for updating a user - can be used to validate API requests
-const updateUserSchema = createUpdateSchema(users);
-
-// Schema for selecting a user - can be used to validate API responses
-const selectUserSchema = createSelectSchema(users);
-
-// Overriding the fields
-const insertUserSchema = createInsertSchema(users, {
-	role: type('string'),
-});
-
-// Refining the fields - useful if you want to change the fields before they become nullable/optional in the final schema
-const insertUserSchema = createInsertSchema(users, {
-	id: (schema) => schema.atLeast(1),
-	role: type('string'),
-});
-
-// Usage
-
-const isUserValid = parse(insertUserSchema, {
-	name: 'John Doe',
-	email: 'johndoe@test.com',
-	role: 'admin',
-});
-```

package/skills/void/docs/node_modules/void/node_modules/drizzle-kit/README.md

@@ -1,79 +0,0 @@
-## Drizzle Kit
-
-Drizzle Kit is a CLI migrator tool for Drizzle ORM. It is probably the one and only tool that lets you completely automatically generate SQL migrations and covers ~95% of the common cases like deletions and renames by prompting user input.
-<https://github.com/drizzle-team/drizzle-kit-mirror> - is a mirror repository for issues.
-
-## Documentation
-
-Check the full documentation on [the website](https://orm.drizzle.team/kit-docs/overview).
-
-### How it works
-
-Drizzle Kit traverses a schema module and generates a snapshot to compare with the previous version, if there is one.
-Based on the difference, it will generate all needed SQL migrations. If there are any cases that can't be resolved automatically, such as renames, it will prompt the user for input.
-
-For example, for this schema module:
-
-```typescript
-// src/db/schema.ts
-
-import { integer, pgTable, serial, text, varchar } from "drizzle-orm/pg-core";
-
-const users = pgTable("users", {
-    id: serial("id").primaryKey(),
-    fullName: varchar("full_name", { length: 256 }),
-  }, (table) => ({
-    nameIdx: index("name_idx", table.fullName),
-  })
-);
-
-export const authOtp = pgTable("auth_otp", {
-  id: serial("id").primaryKey(),
-  phone: varchar("phone", { length: 256 }),
-  userId: integer("user_id").references(() => users.id),
-});
-```
-
-It will generate:
-
-```SQL
-CREATE TABLE IF NOT EXISTS auth_otp (
- "id" SERIAL PRIMARY KEY,
- "phone" character varying(256),
- "user_id" INT
-);
-
-CREATE TABLE IF NOT EXISTS users (
- "id" SERIAL PRIMARY KEY,
- "full_name" character varying(256)
-);
-
-DO $$ BEGIN
- ALTER TABLE auth_otp ADD CONSTRAINT auth_otp_user_id_fkey FOREIGN KEY ("user_id") REFERENCES users(id);
-EXCEPTION
- WHEN duplicate_object THEN null;
-END $$;
-
-CREATE INDEX IF NOT EXISTS users_full_name_index ON users (full_name);
-```
-
-### Installation & configuration
-
-```shell
-npm install -D drizzle-kit
-```
-
-Running with CLI options:
-
-```jsonc
-// package.json
-{
- "scripts": {
-  "generate": "drizzle-kit generate --out migrations-folder --schema src/db/schema.ts"
- }
-}
-```
-
-```shell
-npm run generate
-```

package/skills/void/docs/node_modules/void/node_modules/drizzle-orm/README.md

@@ -1,44 +0,0 @@
-<div align="center">
-  <img src="./misc/readme/logo-github-sq-dark.svg#gh-dark-mode-only" />
-  <img src="./misc/readme/logo-github-sq-light.svg#gh-light-mode-only" />
-</div>
-
-<br/>
-<div align="center">
-  <h3>Headless ORM for NodeJS, TypeScript and JavaScript 🚀</h3>
-  <a href="https://orm.drizzle.team">Website</a> •
-  <a href="https://orm.drizzle.team/docs/overview">Documentation</a> •
-  <a href="https://x.com/drizzleorm">Twitter</a> •
-  <a href="https://driz.link/discord">Discord</a>
-</div>
-
-<br/>
-<br/>
-
-### What's Drizzle?
-Drizzle is a modern TypeScript ORM developers [wanna use in their next project](https://stateofdb.com/tools/drizzle). 
-It is [lightweight](https://bundlephobia.com/package/drizzle-orm) at only ~7.4kb minified+gzipped, and it's tree shakeable with exactly 0 dependencies. 
-
-**Drizzle supports every PostgreSQL, MySQL and SQLite database**, including serverless ones like [Turso](https://orm.drizzle.team/docs/get-started-sqlite#turso), [Neon](https://orm.drizzle.team/docs/get-started-postgresql#neon), [Xata](https://orm.drizzle.team/docs/connect-xata), [PlanetScale](https://orm.drizzle.team/docs/get-started-mysql#planetscale), [Cloudflare D1](https://orm.drizzle.team/docs/get-started-sqlite#cloudflare-d1), [FlyIO LiteFS](https://fly.io/docs/litefs/), [Vercel Postgres](https://orm.drizzle.team/docs/get-started-postgresql#vercel-postgres), [Supabase](https://orm.drizzle.team/docs/get-started-postgresql#supabase) and [AWS Data API](https://orm.drizzle.team/docs/get-started-postgresql#aws-data-api). No bells and whistles, no Rust binaries, no serverless adapters, everything just works out of the box.
-
-**Drizzle is serverless-ready by design**. It works in every major JavaScript runtime like NodeJS, Bun, Deno, Cloudflare Workers, Supabase functions, any Edge runtime, and even in browsers.  
-With Drizzle you can be [**fast out of the box**](https://orm.drizzle.team/benchmarks) and save time and costs while never introducing any data proxies into your infrastructure. 
-
-While you can use Drizzle as a JavaScript library, it shines with TypeScript. It lets you [**declare SQL schemas**](https://orm.drizzle.team/docs/sql-schema-declaration) and build both [**relational**](https://orm.drizzle.team/docs/rqb) and [**SQL-like queries**](https://orm.drizzle.team/docs/select), while keeping the balance between type-safety and extensibility for toolmakers to build on top.  
-
-### Ecosystem
-While Drizzle ORM remains a thin typed layer on top of SQL, we made a set of tools for people to have best possible developer experience.  
-  
-Drizzle comes with a powerful [**Drizzle Kit**](https://orm.drizzle.team/kit-docs/overview) CLI companion for you to have hassle-free migrations. It can generate SQL migration files for you or apply schema changes directly to the database.  
-  
-We also have [**Drizzle Studio**](https://orm.drizzle.team/drizzle-studio/overview) for you to effortlessly browse and manipulate data in your database of choice.
-
-### Documentation
-Check out the full documentation on [the website](https://orm.drizzle.team/docs/overview).
-
-### Our sponsors ❤️
-<p align="center">
-<a href="https://drizzle.team" target="_blank">
-<img src='https://api.drizzle.team/v2/sponsors/svg'/>
-</a>
-</p>

package/skills/void/docs/node_modules/void/node_modules/drizzle-valibot/README.md

@@ -1,51 +0,0 @@
-`drizzle-valibot` is a plugin for [Drizzle ORM](https://github.com/drizzle-team/drizzle-orm) that allows you to generate [valibot](https://valibot.dev/) schemas from Drizzle ORM schemas.
-
-**Features**
-
-- Create a select schema for tables, views and enums.
-- Create insert and update schemas for tables.
-- Supports all dialects: PostgreSQL, MySQL and SQLite.
-
-# Usage
-
-```ts
-import { pgEnum, pgTable, serial, text, timestamp } from 'drizzle-orm/pg-core';
-import { createInsertSchema, createSelectSchema } from 'drizzle-valibot';
-import { string, parse, number, pipe } from 'valibot';
-
-const users = pgTable('users', {
-	id: serial('id').primaryKey(),
-	name: text('name').notNull(),
-	email: text('email').notNull(),
-	role: text('role', { enum: ['admin', 'user'] }).notNull(),
-	createdAt: timestamp('created_at').notNull().defaultNow(),
-});
-
-// Schema for inserting a user - can be used to validate API requests
-const insertUserSchema = createInsertSchema(users);
-
-// Schema for updating a user - can be used to validate API requests
-const updateUserSchema = createUpdateSchema(users);
-
-// Schema for selecting a user - can be used to validate API responses
-const selectUserSchema = createSelectSchema(users);
-
-// Overriding the fields
-const insertUserSchema = createInsertSchema(users, {
-	role: string(),
-});
-
-// Refining the fields - useful if you want to change the fields before they become nullable/optional in the final schema
-const insertUserSchema = createInsertSchema(users, {
-	id: (schema) => pipe([schema, minValue(0)]),
-	role: string(),
-});
-
-// Usage
-
-const isUserValid = parse(insertUserSchema, {
-	name: 'John Doe',
-	email: 'johndoe@test.com',
-	role: 'admin',
-});
-```

package/skills/void/docs/node_modules/void/node_modules/drizzle-zod/README.md

@@ -1,65 +0,0 @@
-<div align='center'>
-<h1>drizzle-zod <a href=''><img alt='npm' src='https://img.shields.io/npm/v/drizzle-zod?label='></a></h1>
-<img alt='npm' src='https://img.shields.io/npm/dm/drizzle-zod'>
-<img alt='npm bundle size' src='https://img.shields.io/bundlephobia/min/drizzle-zod'>
-<a href='https://discord.gg/yfjTbVXMW4'><img alt='Discord' src='https://img.shields.io/discord/1043890932593987624'></a>
-<img alt='License' src='https://img.shields.io/npm/l/drizzle-zod'>
-<h6><i>If you know SQL, you know Drizzle ORM</i></h6>
-<hr />
-</div>
-
-`drizzle-zod` is a plugin for [Drizzle ORM](https://github.com/drizzle-team/drizzle-orm) that allows you to generate [Zod](https://zod.dev/) schemas from Drizzle ORM schemas.
-
-**Features**
-
-- Create a select schema for tables, views and enums.
-- Create insert and update schemas for tables.
-- Supports all dialects: PostgreSQL, MySQL and SQLite.
-
-# Usage
-
-```ts
-import { pgEnum, pgTable, serial, text, timestamp } from 'drizzle-orm/pg-core';
-import { createInsertSchema, createSelectSchema } from 'drizzle-zod';
-import { z } from 'zod';
-
-const users = pgTable('users', {
-  id: serial('id').primaryKey(),
-  name: text('name').notNull(),
-  email: text('email').notNull(),
-  role: text('role', { enum: ['admin', 'user'] }).notNull(),
-  createdAt: timestamp('created_at').notNull().defaultNow(),
-});
-
-// Schema for inserting a user - can be used to validate API requests
-const insertUserSchema = createInsertSchema(users);
-
-// Schema for updating a user - can be used to validate API requests
-const updateUserSchema = createUpdateSchema(users);
-
-// Schema for selecting a user - can be used to validate API responses
-const selectUserSchema = createSelectSchema(users);
-
-// Overriding the fields
-const insertUserSchema = createInsertSchema(users, {
-  role: z.string(),
-});
-
-// Refining the fields - useful if you want to change the fields before they become nullable/optional in the final schema
-const insertUserSchema = createInsertSchema(users, {
-  id: (schema) => schema.positive(),
-  email: (schema) => schema.email(),
-  role: z.string(),
-});
-
-// Usage
-
-const user = insertUserSchema.parse({
-  name: 'John Doe',
-  email: 'johndoe@test.com',
-  role: 'admin',
-});
-
-// Zod schema type is also inferred from the table schema, so you have full type safety
-const requestSchema = insertUserSchema.pick({ name: true, email: true });
-```