svger-cli 2.0.0 → 2.0.2

package/dist/utils/native.js

@@ -0,0 +1,305 @@
+import fs from 'fs';
+import { promisify } from 'util';
+/**
+ * Native Node.js utilities to replace external dependencies
+ */
+/**
+ * Convert string to PascalCase (replaces change-case package)
+ */
+export function toPascalCase(str) {
+    return str
+        .replace(/[^a-zA-Z0-9]/g, ' ')
+        .split(' ')
+        .filter(Boolean)
+        .map(word => word.charAt(0).toUpperCase() + word.slice(1).toLowerCase())
+        .join('');
+}
+/**
+ * Native file system utilities (replaces fs-extra package)
+ */
+export class FileSystem {
+    static _readFile = promisify(fs.readFile);
+    static _writeFile = promisify(fs.writeFile);
+    static _readdir = promisify(fs.readdir);
+    static _stat = promisify(fs.stat);
+    static _mkdir = promisify(fs.mkdir);
+    static _rmdir = promisify(fs.rmdir);
+    static _unlink = promisify(fs.unlink);
+    static async exists(path) {
+        try {
+            await this._stat(path);
+            return true;
+        }
+        catch {
+            return false;
+        }
+    }
+    static async readFile(path, encoding = 'utf8') {
+        return this._readFile(path, encoding);
+    }
+    static async writeFile(path, content, encoding = 'utf8') {
+        return this._writeFile(path, content, encoding);
+    }
+    static async readDir(path) {
+        return this._readdir(path);
+    }
+    static async ensureDir(dirPath) {
+        try {
+            await this._mkdir(dirPath, { recursive: true });
+        }
+        catch (error) {
+            if (error.code !== 'EEXIST') {
+                throw error;
+            }
+        }
+    }
+    static async removeDir(dirPath) {
+        try {
+            const files = await this._readdir(dirPath);
+            for (const file of files) {
+                const filePath = `${dirPath}/${file}`;
+                const stats = await this._stat(filePath);
+                if (stats.isDirectory()) {
+                    await this.removeDir(filePath);
+                }
+                else {
+                    await this._unlink(filePath);
+                }
+            }
+            await this._rmdir(dirPath);
+        }
+        catch (error) {
+            if (error.code !== 'ENOENT') {
+                throw error;
+            }
+        }
+    }
+    static async emptyDir(dirPath) {
+        if (!(await this.exists(dirPath))) {
+            return;
+        }
+        const files = await this._readdir(dirPath);
+        for (const file of files) {
+            const filePath = `${dirPath}/${file}`;
+            const stats = await this._stat(filePath);
+            if (stats.isDirectory()) {
+                await this.removeDir(filePath);
+            }
+            else {
+                await this._unlink(filePath);
+            }
+        }
+    }
+    static async unlink(filePath) {
+        return this._unlink(filePath);
+    }
+    static readJSONSync(path) {
+        try {
+            const content = fs.readFileSync(path, 'utf8');
+            return JSON.parse(content);
+        }
+        catch {
+            return {};
+        }
+    }
+    static writeJSONSync(path, data, options) {
+        const content = JSON.stringify(data, null, options?.spaces || 0);
+        fs.writeFileSync(path, content, 'utf8');
+    }
+    static existsSync(path) {
+        try {
+            fs.statSync(path);
+            return true;
+        }
+        catch {
+            return false;
+        }
+    }
+    static ensureDirSync(dirPath) {
+        try {
+            fs.mkdirSync(dirPath, { recursive: true });
+        }
+        catch (error) {
+            if (error.code !== 'EEXIST') {
+                throw error;
+            }
+        }
+    }
+}
+/**
+ * Simple CLI argument parser (replaces commander package)
+ */
+export class CLI {
+    commands = new Map();
+    programName = '';
+    programDescription = '';
+    programVersion = '';
+    name(name) {
+        this.programName = name;
+        return this;
+    }
+    description(desc) {
+        this.programDescription = desc;
+        return this;
+    }
+    version(version) {
+        this.programVersion = version;
+        return this;
+    }
+    command(signature) {
+        return new CommandBuilder(signature, this);
+    }
+    addCommand(signature, description, action, options) {
+        const [command] = signature.split(' ');
+        this.commands.set(command, {
+            description,
+            action: action,
+            options
+        });
+    }
+    async parse() {
+        const args = process.argv.slice(2);
+        if (args.length === 0 || args[0] === '--help' || args[0] === '-h') {
+            this.showHelp();
+            return;
+        }
+        if (args[0] === '--version' || args[0] === '-v') {
+            console.log(this.programVersion);
+            return;
+        }
+        const [commandName, ...remainingArgs] = args;
+        const command = this.commands.get(commandName);
+        if (!command) {
+            console.error(`Unknown command: ${commandName}`);
+            this.showHelp();
+            process.exit(1);
+        }
+        const { parsedArgs, options } = this.parseArgs(remainingArgs, command.options);
+        try {
+            await command.action(parsedArgs, options);
+        }
+        catch (error) {
+            console.error('Command failed:', error);
+            process.exit(1);
+        }
+    }
+    parseArgs(args, commandOptions) {
+        const parsedArgs = [];
+        const options = {};
+        let i = 0;
+        while (i < args.length) {
+            const arg = args[i];
+            if (arg.startsWith('--')) {
+                const optionName = arg.slice(2);
+                const optionConfig = commandOptions.get(optionName);
+                if (optionConfig) {
+                    if (optionConfig.hasValue) {
+                        options[optionName] = args[i + 1];
+                        i += 2;
+                    }
+                    else {
+                        options[optionName] = true;
+                        i++;
+                    }
+                }
+                else {
+                    // Handle key=value format
+                    if (arg.includes('=')) {
+                        const [key, value] = arg.slice(2).split('=');
+                        options[key] = value;
+                        i++;
+                    }
+                    else {
+                        i++;
+                    }
+                }
+            }
+            else {
+                parsedArgs.push(arg);
+                i++;
+            }
+        }
+        return { parsedArgs, options };
+    }
+    showHelp() {
+        console.log(`${this.programName} - ${this.programDescription}`);
+        console.log(`Version: ${this.programVersion}\n`);
+        console.log('Commands:');
+        for (const [name, cmd] of this.commands) {
+            console.log(`  ${name.padEnd(15)} ${cmd.description}`);
+        }
+        console.log('\nOptions:');
+        console.log('  --help, -h      Show help');
+        console.log('  --version, -v   Show version');
+    }
+}
+class CommandBuilder {
+    signature;
+    desc = '';
+    cli;
+    options = new Map();
+    constructor(signature, cli) {
+        this.signature = signature;
+        this.cli = cli;
+    }
+    description(desc) {
+        this.desc = desc;
+        return this;
+    }
+    option(flag, description) {
+        const hasValue = flag.includes('<') || flag.includes('[');
+        const optionName = flag.split(' ')[0].replace(/^--/, '');
+        this.options.set(optionName, { description, hasValue });
+        return this;
+    }
+    action(fn) {
+        this.cli.addCommand(this.signature, this.desc, fn, this.options);
+    }
+}
+/**
+ * File watcher using native fs.watch (replaces chokidar)
+ */
+export class FileWatcher {
+    watchers = [];
+    callbacks = new Map();
+    watch(path, options) {
+        try {
+            const watcher = fs.watch(path, {
+                recursive: options?.recursive || false,
+                persistent: true
+            }, (eventType, filename) => {
+                if (filename) {
+                    this.emit(eventType, `${path}/${filename}`);
+                }
+            });
+            this.watchers.push(watcher);
+        }
+        catch (error) {
+            console.error(`Failed to watch ${path}:`, error);
+        }
+        return this;
+    }
+    on(event, callback) {
+        if (!this.callbacks.has(event)) {
+            this.callbacks.set(event, []);
+        }
+        this.callbacks.get(event).push(callback);
+        return this;
+    }
+    emit(event, ...args) {
+        const callbacks = this.callbacks.get(event) || [];
+        callbacks.forEach(callback => {
+            try {
+                callback(...args);
+            }
+            catch (error) {
+                console.error('Watcher callback error:', error);
+            }
+        });
+    }
+    close() {
+        this.watchers.forEach(watcher => watcher.close());
+        this.watchers = [];
+        this.callbacks.clear();
+    }
+}

package/package.json

@@ -1,14 +1,21 @@
 {
   "name": "svger-cli",
-  "version": "2.0.0",
+  "version": "2.0.2",
   "description": "CLI and runtime for converting SVGs to React components with watch support",
-  "main": "dist/cli.js",
+  "main": "dist/index.js",
   "type": "module",
   "bin": {
     "svger-cli": "./bin/svg-tool.js"
   },
+  "files": [
+    "dist",
+    "bin",
+    "README.md",
+    "LICENSE"
+  ],
   "scripts": {
     "build": "tsc -p tsconfig.json",
+    "prepublishOnly": "npm run build",
     "dev": "ts-node src/cli.ts"
   },
   "keywords": [
@@ -18,7 +25,6 @@
     "components"
   ],
   "author": "faeze mohades",
-  "repository": "https://github.com/faezemohades/svger-cli",
   "license": "MIT",
   "dependencies": {},
   "devDependencies": {

package/.svgconfig.json

@@ -1,3 +0,0 @@
-{
-  "defaultHeight": 32
-}

package/CODE_OF_CONDUCT.md

@@ -1,79 +0,0 @@
-# Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
-
-We value open and honest communication, inspired by the Linux kernel community's emphasis on technical excellence and direct feedback, while maintaining respect and professionalism.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-* Focusing on what is best not only for us as individuals, but for the overall community
-* Using inclusive language and avoiding assumptions about others' backgrounds or abilities
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement. All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity

package/CONTRIBUTING.md

@@ -1,146 +0,0 @@
-# Contributing to svger-cli
-
-Thank you for your interest in contributing to svger-cli! We welcome contributions from the community to help improve and grow this zero-dependency enterprise SVG processing framework. This document outlines the guidelines and processes for contributing.
-
-## Table of Contents
-
-- [Code of Conduct](#code-of-conduct)
-- [How to Contribute](#how-to-contribute)
-- [Development Setup](#development-setup)
-- [Reporting Issues](#reporting-issues)
-- [Submitting Pull Requests](#submitting-pull-requests)
-- [Code Style and Standards](#code-style-and-standards)
-- [Testing](#testing)
-- [Commit Guidelines](#commit-guidelines)
-- [License](#license)
-
-## Code of Conduct
-
-This project adheres to a [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to the maintainers.
-
-## How to Contribute
-
-There are many ways to contribute to svger-cli:
-
-- **Report bugs** and request features via GitHub Issues
-- **Improve documentation** by fixing typos or adding examples
-- **Write code** by submitting pull requests
-- **Review pull requests** from other contributors
-- **Help others** in discussions and issue threads
-- **Add framework support** for new UI libraries
-- **Optimize performance** and reduce bundle size
-
-## Development Setup
-
-1. **Fork and Clone**: Fork the repository on GitHub and clone your fork locally.
-
-   ```bash
-   git clone https://github.com/your-username/svger-cli.git
-   cd svger-cli
-   ```
-
-2. **Install Dev Dependencies**: Install TypeScript and development tools.
-
-   ```bash
-   npm install
-   ```
-
-3. **Build the Project**: Compile TypeScript to JavaScript.
-
-   ```bash
-   npm run build
-   ```
-
-4. **Test the CLI**: Run the built CLI to ensure it works.
-
-   ```bash
-   node dist/cli.js --help
-   ```
-
-## Reporting Issues
-
-When reporting issues, please include:
-
-- A clear and descriptive title
-- Steps to reproduce the issue
-- Expected behavior
-- Actual behavior
-- Environment details (OS, Node.js version, etc.)
-- Any relevant SVG files or error messages
-- Framework you're targeting (React, Vue, etc.)
-
-Use GitHub Issues for bug reports and feature requests.
-
-## Submitting Pull Requests
-
-1. **Create a Branch**: Create a feature branch from `main`.
-
-   ```bash
-   git checkout -b feature/your-feature-name
-   ```
-
-2. **Make Changes**: Implement your changes, following the code style guidelines.
-
-3. **Test Manually**: Since automated tests are not yet implemented, thoroughly test your changes manually.
-
-4. **Update Documentation**: Update README.md or other docs if necessary.
-
-5. **Commit Changes**: Use clear commit messages (see [Commit Guidelines](#commit-guidelines)).
-
-6. **Push and Create PR**: Push your branch and create a pull request on GitHub.
-
-   - Provide a clear description of the changes
-   - Reference any related issues
-   - Include before/after screenshots for UI changes
-   - Test with multiple frameworks if applicable
-
-## Code Style and Standards
-
-- **Language**: TypeScript is the primary language
-- **Zero Dependencies**: Maintain zero runtime dependencies - use only native Node.js APIs
-- **Modular Architecture**: Follow the service-oriented architecture in `src/`
-- **Naming**: Use descriptive names for variables, functions, and classes
-- **Comments**: Add JSDoc comments for public APIs
-- **Error Handling**: Use the centralized error handler for consistent error management
-- **Performance**: Optimize for speed and memory usage
-
-Build and test your changes:
-
-```bash
-npm run build
-node dist/cli.js [your-test-command]
-```
-
-## Testing
-
-Currently, the project relies on manual testing. Future contributions that add automated testing infrastructure are highly encouraged.
-
-When testing:
-
-- Test with various SVG files (simple and complex)
-- Test all supported frameworks
-- Test edge cases like malformed SVGs
-- Verify performance doesn't regress
-
-## Commit Guidelines
-
-- Use the imperative mood in commit messages (e.g., "Add feature" not "Added feature")
-- Keep the first line under 50 characters
-- Provide a detailed description in the body if needed
-- Reference issue numbers when applicable (e.g., "Fix #123")
-
-Example:
-
-```
-Add Vue.js framework support
-
-- Implement Vue composition API template
-- Add Vue-specific prop handling
-- Update framework detection logic
-
-Closes #456
-```
-
-## License
-
-By contributing to this project, you agree that your contributions will be licensed under the [MIT License](LICENSE).

package/TESTING.md

@@ -1,143 +0,0 @@
-# SVGER-CLI Testing Guide
-
-## Automated Framework Tests
-
-The project includes comprehensive testing for all 8 supported frameworks.
-
-### Run All Framework Tests
-
-```bash
-node test-frameworks.js
-```
-
-This test suite validates:
-- ✅ Component generation for React, Vue, Svelte, Angular, Solid, Preact, Lit, Vanilla
-- ✅ TypeScript type correctness
-- ✅ Framework-specific patterns and best practices
-- ✅ Correct file extensions per framework
-- ✅ Code syntax validity
-
-### Test Output
-
-All generated test components are saved to `test-output/` directory for manual inspection.
-
-## Manual CLI Testing
-
-### Test React (Default)
-
-```bash
-svger-cli build my-svgs test-react
-```
-
-Expected: `.tsx` files with React.forwardRef components
-
-### Test Vue Composition API
-
-```bash
-svger-cli build my-svgs test-vue --framework vue --composition
-```
-
-Expected: `.vue` files with `<script setup lang="ts">`
-
-### Test Vue Options API
-
-```bash
-svger-cli build my-svgs test-vue-options --framework vue
-```
-
-Expected: `.vue` files with `defineComponent`
-
-### Test Svelte
-
-```bash
-svger-cli build my-svgs test-svelte --framework svelte
-```
-
-Expected: `.svelte` files with TypeScript props
-
-### Test Angular Standalone
-
-```bash
-svger-cli build my-svgs test-angular --framework angular --standalone
-```
-
-Expected: `.component.ts` files with `standalone: true`
-
-### Test Angular Module
-
-```bash
-svger-cli build my-svgs test-angular-module --framework angular
-```
-
-Expected: `.component.ts` files without standalone flag
-
-### Test Solid
-
-```bash
-svger-cli build my-svgs test-solid --framework solid
-```
-
-Expected: `.tsx` files with Solid Component types
-
-### Test Preact
-
-```bash
-svger-cli build my-svgs test-preact --framework preact
-```
-
-Expected: `.tsx` files with Preact FunctionComponent
-
-### Test Lit
-
-```bash
-svger-cli build my-svgs test-lit --framework lit
-```
-
-Expected: `.ts` files with @customElement decorator
-
-### Test Vanilla JS
-
-```bash
-svger-cli build my-svgs test-vanilla --framework vanilla
-```
-
-Expected: `.ts` files with factory functions
-
-## Build Verification
-
-After making changes:
-
-```bash
-# Clean build
-npm run build
-
-# Run automated tests
-node test-frameworks.js
-
-# Manual CLI test
-svger-cli build my-svgs test-output --framework vue
-```
-
-## Test Results
-
-Latest test run (2025-11-07):
-
-```
-Total Tests: 10
-✅ Passed: 10
-❌ Failed: 0
-
-Frameworks Tested:
-- React ✅
-- Vue (Composition) ✅
-- Vue (Options) ✅
-- Svelte ✅
-- Angular (Standalone) ✅
-- Angular (Module) ✅
-- Solid ✅
-- Preact ✅
-- Lit ✅
-- Vanilla ✅
-```
-
-All frameworks generate valid, idiomatic components that follow framework best practices.