langctl 0.1.1 → 0.2.0

package/package.json

@@ -1,14 +1,14 @@
 {
   "name": "langctl",
-  "version": "0.1.1",
-  "description": "CLI-first translation management for developers. Affordable, AI-powered, and built for modern workflows.",
+  "version": "0.2.0",
+  "description": "Translation management CLI for developers. Manage i18n translations, export to 6 formats (iOS, Android, Flutter, i18next), import translations, and collaborate with teams. Affordable alternative to Lokalise and Crowdin.",
   "main": "dist/index.js",
   "type": "module",
   "bin": {
-    "langctl": "./dist/index.js"
+    "langctl": "dist/index.js"
   },
   "scripts": {
-    "build": "tsc",
+    "build": "rm -rf dist && tsc",
     "dev": "tsx src/index.ts",
     "start": "node dist/index.js",
     "prepublishOnly": "npm run build",
@@ -24,13 +24,60 @@
     "translations",
     "translate",
     "language",
-    "multilingual"
+    "multilingual",
+    "translation-management",
+    "localization-management",
+    "translation-tool",
+    "i18next",
+    "developer-tools",
+    "devtools",
+    "dev-tool",
+    "ios",
+    "android",
+    "flutter",
+    "react",
+    "angular",
+    "vue",
+    "react-native",
+    "json",
+    "xml",
+    "arb",
+    "strings",
+    "automation",
+    "ci-cd",
+    "cicd",
+    "continuous-integration",
+    "workflow",
+    "export",
+    "import",
+    "translation-export",
+    "translation-import",
+    "team",
+    "collaboration",
+    "multilanguage",
+    "multi-language",
+    "lokalise-alternative",
+    "crowdin-alternative",
+    "phrase-alternative",
+    "affordable",
+    "free",
+    "gettext",
+    "po",
+    "locale",
+    "translation-keys",
+    "localization-tool",
+    "string-management",
+    "mobile-localization",
+    "web-localization",
+    "app-localization",
+    "saas",
+    "api"
   ],
   "author": "Siddharth Saxena <hello@langctl.com>",
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/siddharthsaxena0/langctl.git"
+    "url": "git+https://github.com/siddharthsaxena0/langctl.git"
   },
   "bugs": {
     "url": "https://github.com/siddharthsaxena0/langctl/issues"
@@ -40,7 +87,6 @@
     "node": ">=16.0.0"
   },
   "dependencies": {
-    "@supabase/supabase-js": "^2.89.0",
     "chalk": "^5.6.2",
     "commander": "^14.0.2",
     "conf": "^15.0.2",

package/NPM_PUBLISH_GUIDE.md

@@ -1,293 +0,0 @@
-# 🚀 Publishing Langctl CLI to npm
-
-**Date:** January 5, 2026  
-**Package:** langctl  
-**Version:** 0.1.0
-
----
-
-## ✅ Pre-Publish Checklist
-
-Before publishing, verify these items:
-
-- [x] Package name available: `langctl` ✅
-- [x] README.md complete with examples ✅
-- [x] package.json properly configured ✅
-- [x] .npmignore configured ✅
-- [x] TypeScript source code ready ✅
-- [x] License file present (MIT) ✅
-
----
-
-## 📋 Step-by-Step Publishing Guide
-
-### Step 1: Verify npm Login
-
-Check if you're logged into npm:
-
-```bash
-npm whoami
-```
-
-**If not logged in:**
-
-```bash
-npm login
-```
-
-Enter your credentials:
-- Username
-- Password
-- Email
-- One-time password (if 2FA enabled)
-
----
-
-### Step 2: Final Build & Test
-
-```bash
-cd /Users/siddharthsaxena/Documents/projects/langctl/langctl-cli
-
-# Clean previous build
-rm -rf dist/
-
-# Fresh build
-npm run build
-
-# Verify build succeeded
-ls -la dist/
-```
-
-**Expected:** You should see `.js` and `.d.ts` files in dist/
-
----
-
-### Step 3: Test Package Locally
-
-Before publishing, test the package works:
-
-```bash
-# Link package globally for testing
-npm link
-
-# Test the CLI
-langctl --version
-langctl --help
-
-# If it works, unlink
-npm unlink -g langctl
-```
-
----
-
-### Step 4: Dry Run (Recommended)
-
-See what will be published WITHOUT actually publishing:
-
-```bash
-npm pack --dry-run
-```
-
-This shows:
-- ✅ Files that will be included
-- ✅ Package size
-- ✅ No errors
-
----
-
-### Step 5: Create Package Tarball (Optional)
-
-Create actual tarball to inspect:
-
-```bash
-npm pack
-```
-
-This creates: `langctl-0.1.0.tgz`
-
-**To inspect:**
-```bash
-tar -xzf langctl-0.1.0.tgz
-ls -la package/
-```
-
-**Clean up after:**
-```bash
-rm langctl-0.1.0.tgz
-rm -rf package/
-```
-
----
-
-### Step 6: Publish to npm! 🚀
-
-**First time publishing (public package):**
-
-```bash
-npm publish --access public
-```
-
-**Expected output:**
-```
-npm notice 
-npm notice 📦  langctl@0.1.0
-npm notice === Tarball Contents === 
-npm notice 1.1kB LICENSE
-npm notice 2.3kB README.md
-npm notice 845B  package.json
-npm notice 15.2kB dist/...
-npm notice === Tarball Details === 
-npm notice name:          langctl
-npm notice version:       0.1.0
-npm notice package size:  XX.X kB
-npm notice unpacked size: XXX.X kB
-npm notice total files:   XX
-npm notice 
-+ langctl@0.1.0
-```
-
----
-
-### Step 7: Verify Publication
-
-**Check on npm:**
-1. Visit: https://www.npmjs.com/package/langctl
-2. Verify README displays correctly
-3. Check version number
-
-**Test installation:**
-```bash
-# In a different directory
-npx langctl@latest --version
-```
-
----
-
-## 🎉 Success! Package Published
-
-Your CLI is now available globally at:
-- **npm:** https://www.npmjs.com/package/langctl
-- **Install:** `npm install -g langctl`
-- **Use:** `npx langctl`
-
----
-
-## 📊 Post-Publish Tasks
-
-### Update Landing Page
-
-Add npm install instructions to langctl.com:
-
-```bash
-npm install -g langctl
-```
-
-### Update README (if needed)
-
-If you notice issues, you can publish patches:
-
-```bash
-# Fix README or other files
-# Bump version
-npm version patch  # 0.1.0 → 0.1.1
-
-# Rebuild and republish
-npm run build
-npm publish
-```
-
-### Monitor npm Stats
-
-Check download stats:
-- https://www.npmjs.com/package/langctl
-- https://npmtrends.com/langctl
-
----
-
-## 🔧 Troubleshooting
-
-### Error: "You do not have permission to publish"
-
-**Solution:**
-```bash
-npm login
-npm whoami  # Verify correct account
-```
-
-### Error: "Package name already exists"
-
-**Solution:** The name is taken. Since you reserved it, make sure you're logged in correctly.
-
-### Error: "Must be logged in to publish"
-
-**Solution:**
-```bash
-npm login
-```
-
-### Build errors
-
-**Solution:**
-```bash
-rm -rf node_modules/ dist/
-npm install
-npm run build
-```
-
----
-
-## 📈 Version Updates (Future)
-
-**Patch (bug fixes):** 0.1.0 → 0.1.1
-```bash
-npm version patch
-npm run build
-npm publish
-```
-
-**Minor (new features):** 0.1.0 → 0.2.0
-```bash
-npm version minor
-npm run build
-npm publish
-```
-
-**Major (breaking changes):** 0.1.0 → 1.0.0
-```bash
-npm version major
-npm run build
-npm publish
-```
-
----
-
-## ✅ Final Checklist
-
-Before running `npm publish`:
-
-- [ ] Logged into npm (`npm whoami`)
-- [ ] Build succeeded (`npm run build`)
-- [ ] Local test passed (`npm link` + test commands)
-- [ ] Dry run clean (`npm pack --dry-run`)
-- [ ] Ready to publish! (`npm publish --access public`)
-
----
-
-## 🎯 Quick Command Summary
-
-```bash
-# From langctl-cli directory:
-npm whoami                        # Verify login
-npm run build                     # Build TypeScript
-npm pack --dry-run                # Preview package
-npm publish --access public       # Publish!
-npx langctl@latest --version      # Verify
-```
-
----
-
-**Good luck! You're about to publish your first npm package! 🚀**
-
-**Questions? Issues?**
-- npm support: https://www.npmjs.com/support
-- Package page: https://www.npmjs.com/package/langctl

package/QUICK_PUBLISH.md

@@ -1,64 +0,0 @@
-# 🚀 PUBLISH LANGCTL - QUICK COMMANDS
-
-**Run these commands in order on YOUR MAC:**
-
-```bash
-# 1. Navigate to CLI directory
-cd /Users/siddharthsaxena/Documents/projects/langctl/langctl-cli
-
-# 2. Check npm login
-npm whoami
-
-# 3. If not logged in:
-npm login
-
-# 4. Build the package
-npm run build
-
-# 5. Test locally (optional but recommended)
-npm link
-langctl --version
-langctl --help
-npm unlink -g langctl
-
-# 6. Dry run to preview
-npm pack --dry-run
-
-# 7. PUBLISH! 🚀
-npm publish --access public
-
-# 8. Verify it worked
-npx langctl@latest --version
-```
-
----
-
-## ✅ Expected Result
-
-After `npm publish`, you should see:
-
-```
-+ langctl@0.1.0
-```
-
-Then check: https://www.npmjs.com/package/langctl
-
----
-
-## 🎉 That's It!
-
-Your CLI is now installable worldwide:
-
-```bash
-npm install -g langctl
-```
-
-or
-
-```bash
-npx langctl --help
-```
-
----
-
-**Full guide:** See `NPM_PUBLISH_GUIDE.md` for detailed instructions and troubleshooting.

package/SECURITY_FIX.md

@@ -1,167 +0,0 @@
-# 🔒 Security Fix - Supabase Credentials
-
-**Date:** January 5, 2026  
-**Issue:** Supabase credentials were being stored in user config files  
-**Status:** ✅ FIXED
-
----
-
-## 🚨 What Was Wrong
-
-Previously, the CLI was:
-- ❌ Storing Supabase URL in `~/.langctl/config.json`
-- ❌ Storing Supabase anon key in `~/.langctl/config.json`
-- ❌ Asking users about "Supabase configuration" during init
-- ❌ Exposing backend implementation details to users
-
-**Why this was bad:**
-- Users could see our backend credentials
-- Users could manipulate Supabase connection
-- Exposed unnecessary implementation details
-- Confused users with technical jargon
-
----
-
-## ✅ What's Fixed
-
-Now the CLI:
-- ✅ Hardcodes Supabase credentials in source code
-- ✅ Only stores user credentials (API key, org ID, preferences)
-- ✅ Users never see or interact with Supabase
-- ✅ Clean, simple user experience
-
----
-
-## 📄 Files Changed
-
-### 1. `src/config.ts`
-**Removed from interface:**
-```typescript
-// REMOVED - no longer stored
-supabaseUrl?: string;
-supabaseAnonKey?: string;
-```
-
-**Now only stores:**
-```typescript
-apiKey?: string;              // User's API key
-organizationId?: string;      // User's org ID
-organizationName?: string;    // User's org name
-defaultProject?: string;      // User preference
-defaultLanguage?: string;     // User preference
-```
-
-### 2. `src/supabase.ts`
-**Before:**
-```typescript
-// BAD - pulled from user config
-const supabaseUrl = config.get('supabaseUrl');
-const supabaseAnonKey = config.get('supabaseAnonKey');
-```
-
-**After:**
-```typescript
-// GOOD - hardcoded in source
-const SUPABASE_URL = 'https://bcgnmvkgkbhbxzzflwdb.supabase.co';
-const SUPABASE_ANON_KEY = 'eyJhbGci...';
-```
-
-### 3. `src/commands/init.ts`
-**Before:**
-```typescript
-// BAD - saved to user config
-config.set('supabaseUrl', SUPABASE_URL);
-config.set('supabaseAnonKey', SUPABASE_ANON_KEY);
-```
-
-**After:**
-```typescript
-// GOOD - just initializes, doesn't save
-initializeSupabase();
-```
-
-### 4. `src/commands/config.ts`
-**Before:**
-```typescript
-// BAD - displayed Supabase credentials
-supabaseAnonKey: allConfig.supabaseAnonKey ? maskSensitive(...) : undefined
-```
-
-**After:**
-```typescript
-// GOOD - only displays user data
-apiKey: allConfig.apiKey ? maskApiKey(allConfig.apiKey) : undefined,
-organizationId: allConfig.organizationId,
-organizationName: allConfig.organizationName
-```
-
----
-
-## 🔐 Security Notes
-
-**Is it safe to hardcode Supabase credentials in the CLI?**
-
-✅ **YES!** This is perfectly safe because:
-
-1. **Anon key is designed for client-side use**
-   - It's meant to be public-facing
-   - Row Level Security (RLS) protects all data
-   - Users can only access what they're authorized for
-
-2. **RLS policies enforce security**
-   - Users can only see their own organization data
-   - API key verification happens server-side (Edge Function)
-   - All operations are protected by RLS
-
-3. **This is standard practice**
-   - Same as mobile apps that embed API credentials
-   - Same as web apps that expose client keys
-   - Backend security, not client security
-
-**What if someone decompiles the CLI?**
-- They'll see the Supabase URL and anon key
-- But they CANNOT access data without a valid API key
-- API keys are user-specific and verified server-side
-- RLS prevents unauthorized access
-
----
-
-## 📊 What Users See Now
-
-### Config File (`~/.langctl/config.json`)
-```json
-{
-  "apiKey": "lc_abc123...",
-  "organizationId": "uuid-here",
-  "organizationName": "My Company",
-  "defaultLanguage": "en"
-}
-```
-
-**Clean and simple!** No backend implementation details.
-
-### Running `langctl config`
-```
-📋 Langctl Configuration
-
-apiKey: lc_abc123...wxyz
-organizationId: 550e8400-e29b-41d4-a716-446655440000
-organizationName: My Company
-defaultLanguage: en
-
-Config file: /Users/username/.langctl/config.json
-```
-
-**Only user-relevant information!**
-
----
-
-## ✅ Ready to Publish
-
-This security fix is complete. The CLI now:
-- ✅ Keeps backend credentials private
-- ✅ Only exposes user data to users
-- ✅ Maintains full security with RLS
-- ✅ Provides clean user experience
-
-**Safe to publish to npm!** 🚀

package/dist/supabase.d.ts

@@ -1,14 +0,0 @@
-import { SupabaseClient } from '@supabase/supabase-js';
-/**
- * Initialize Supabase client with hardcoded credentials
- */
-export declare function initializeSupabase(): SupabaseClient;
-/**
- * Get existing Supabase client or initialize it
- */
-export declare function getSupabase(): SupabaseClient;
-/**
- * Reset Supabase client (useful for tests)
- */
-export declare function resetSupabase(): void;
-//# sourceMappingURL=supabase.d.ts.map

package/dist/supabase.js

@@ -1,30 +0,0 @@
-import { createClient } from '@supabase/supabase-js';
-// Hardcoded Supabase credentials (safe for client-side use with RLS)
-const SUPABASE_URL = 'https://bcgnmvkgkbhbxzzflwdb.supabase.co';
-const SUPABASE_ANON_KEY = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImJjZ25tdmtna2JoYnh6emZsd2RiIiwicm9sZSI6ImFub24iLCJpYXQiOjE3MzQ3OTE4ODEsImV4cCI6MjA1MDM2Nzg4MX0.LqZYO8GGQfI-C9WCF_a2NTKqIrO1TDsPXU9LHRE8b0E';
-let supabaseClient = null;
-/**
- * Initialize Supabase client with hardcoded credentials
- */
-export function initializeSupabase() {
-    if (!supabaseClient) {
-        supabaseClient = createClient(SUPABASE_URL, SUPABASE_ANON_KEY);
-    }
-    return supabaseClient;
-}
-/**
- * Get existing Supabase client or initialize it
- */
-export function getSupabase() {
-    if (!supabaseClient) {
-        return initializeSupabase();
-    }
-    return supabaseClient;
-}
-/**
- * Reset Supabase client (useful for tests)
- */
-export function resetSupabase() {
-    supabaseClient = null;
-}
-//# sourceMappingURL=supabase.js.map