SatoshiQaziMuhammed a80c7c30d1 build: drop vite-plugin-node-polyfills and its elliptic dependency (#59)
The plugin pulled node-stdlib-browser -> crypto-browserify ->
browserify-sign/create-ecdh -> elliptic (GHSA-848j-6mx2-7j84, no
patched release) into the runtime dependency tree.

Nothing in the app imports a Node builtin. In the production build the
plugin only injected shims at four call sites, each already guarded by a
typeof check with a browser fallback:

- @supabase/storage-js toBase64 (Buffer; falls back to btoa, and the app
  does not use Supabase Storage)
- @supabase/realtime-js WebSocketFactory (global; native WebSocket is
  detected first)
- @pezkuwi/x-global (global; globalThis is checked first)
- js-sha3 (process; only used to detect Node)

The crypto, stream and util polyfills were never reached by any module,
so removing the plugin drops 97 packages from the lockfile, including
elliptic, and the feross buffer copy from the bundle.
2026-11-15 06:26:08 +04:00

Pezkuwi Telegram Mini App

Telegram Mini App for Pezkuwichain - Forum, Announcements, Rewards, and Wallet integration.

Tech Stack

  • Frontend: React 18 + TypeScript + Vite
  • Styling: Tailwind CSS + shadcn/ui patterns
  • State: TanStack Query (React Query)
  • Backend: Supabase (PostgreSQL + Auth + Edge Functions)
  • Testing: Vitest + Testing Library
  • CI/CD: GitHub Actions

Getting Started

Prerequisites

  • Node.js >= 18
  • npm >= 9
  • Supabase account

Installation

# Clone the repo
git clone https://github.com/pezkuwichain/pezkuwi-telegram-miniapp.git
cd pezkuwi-telegram-miniapp

# Install dependencies
npm install

# Copy environment template
cp .env.example .env

# Add your Supabase credentials to .env

Development

# Start dev server
npm run dev

# Run tests
npm run test

# Type check
npm run typecheck

# Lint
npm run lint

# Format code
npm run format

# Full validation (typecheck + lint + test + build)
npm run validate

Build

npm run build

Output will be in dist/ directory.

Project Structure

src/
├── contexts/       # React contexts (Auth)
├── hooks/          # Custom hooks (Supabase, Telegram)
├── lib/            # Utilities (env, supabase client)
├── sections/       # Main app sections
│   ├── Announcements.tsx
│   ├── Forum.tsx
│   ├── Rewards.tsx
│   └── Wallet.tsx
├── test/           # Test setup
├── types/          # TypeScript types
├── App.tsx         # Main app component
└── main.tsx        # Entry point

Database Schema

Tables (prefixed with tg_ to avoid conflicts):

  • tg_users - Telegram users
  • tg_announcements - Admin announcements
  • tg_announcement_reactions - Like/dislike reactions
  • tg_threads - Forum threads
  • tg_thread_likes - Thread likes
  • tg_replies - Thread replies
  • tg_reply_likes - Reply likes

Environment Variables

Variable Description
VITE_SUPABASE_URL Supabase project URL
VITE_SUPABASE_ANON_KEY Supabase anon/public key

Telegram Setup

  1. Create bot via @BotFather
  2. Enable Mini App in bot settings
  3. Set Mini App URL to deployment URL
  4. Deploy telegram-auth Edge Function to Supabase

License

MIT

S
Description
No description provided
Readme MIT
7.9 MiB
1 Watchers 0 Forks
Languages
TypeScript 90.8%
Python 3.1%
PLpgSQL 2.4%
JavaScript 2.1%
Shell 1.1%
Other 0.4%