stackinit 0.1.0

package/.editorconfig

@@ -0,0 +1,18 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_style = space
+indent_size = 2
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.md]
+trim_trailing_whitespace = false
+
+[*.{yml,yaml}]
+indent_size = 2
+
+[Makefile]
+indent_style = tab

package/.env.example

@@ -0,0 +1,11 @@
+# Environment variables
+# Copy this file to .env and fill in the values
+
+NODE_ENV=development
+PORT=3000
+
+# Database (example)
+# DATABASE_URL=postgresql://user:password@localhost:5432/dbname
+
+# API Keys (example)
+# API_KEY=your-api-key-here

package/.eslintrc.json

@@ -0,0 +1,30 @@
+{
+  "root": true,
+  "env": {
+    "node": true,
+    "es2022": true
+  },
+  "extends": [
+    "eslint:recommended",
+    "plugin:@typescript-eslint/recommended"
+  ],
+  "parserOptions": {
+    "ecmaVersion": 2022,
+    "sourceType": "module",
+    "project": "./tsconfig.json"
+  },
+  "rules": {
+    "no-console": "warn",
+    "no-debugger": "warn",
+    "no-unused-vars": "warn",
+    "prefer-const": "error",
+    "no-var": "error",
+    "@typescript-eslint/no-unused-vars": "warn",
+    "@typescript-eslint/explicit-function-return-type": "off",
+    "@typescript-eslint/no-explicit-any": "warn"
+  },
+  "parser": "@typescript-eslint/parser",
+  "plugins": [
+    "@typescript-eslint"
+  ]
+}

package/.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+name: CI
+
+on:
+  push:
+    branches: [main, master, develop]
+  pull_request:
+    branches: [main, master, develop]
+
+jobs:
+  ci:
+    runs-on: ubuntu-latest
+    
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+      
+      - name: Install dependencies
+        run: npm ci
+      
+      - name: Lint
+        run: npm run lint
+
+      
+      - name: Type check
+        run: npm run type-check
+
+      
+      - name: Run tests
+        run: npm test
+        continue-on-error: true

package/.prettierignore

@@ -0,0 +1,11 @@
+node_modules
+dist
+build
+.next
+.nuxt
+.cache
+coverage
+*.log
+.DS_Store
+.env
+.env.local

package/.prettierrc.json

@@ -0,0 +1,10 @@
+{
+  "semi": true,
+  "trailingComma": "es5",
+  "singleQuote": true,
+  "printWidth": 80,
+  "tabWidth": 2,
+  "useTabs": false,
+  "arrowParens": "always",
+  "endOfLine": "lf"
+}

package/CONTRIBUTING.md

@@ -0,0 +1,272 @@
+# Contributing to stackinit
+
+Thank you for your interest in contributing to stackinit! This document provides guidelines and instructions for contributing to the project.
+
+## Code of Conduct
+
+By participating in this project, you agree to maintain a respectful and inclusive environment for all contributors.
+
+## How to Contribute
+
+### Reporting Bugs
+
+Before reporting a bug, please:
+
+1. Check if the issue has already been reported in the [Issues](https://github.com/yourusername/stackinit/issues) section
+2. Verify that the bug still exists in the latest version
+3. Collect relevant information:
+   - Node.js version
+   - Operating system
+   - Steps to reproduce
+   - Expected behavior
+   - Actual behavior
+   - Error messages (if any)
+
+When creating a bug report, please use the bug report template and include as much detail as possible.
+
+### Suggesting Features
+
+We welcome feature suggestions! Please:
+
+1. Check if the feature has already been suggested
+2. Open an issue with the "enhancement" label
+3. Clearly describe:
+   - The problem the feature would solve
+   - How the feature would work
+   - Why it would be useful
+
+### Pull Requests
+
+We love pull requests! Here's how to submit one:
+
+1. **Fork the repository**
+   ```bash
+   git clone https://github.com/yourusername/stackinit.git
+   cd stackinit
+   ```
+
+2. **Create a branch**
+   ```bash
+   git checkout -b feature/your-feature-name
+   # or
+   git checkout -b fix/your-bug-fix
+   ```
+
+3. **Set up the development environment**
+   ```bash
+   npm install
+   ```
+
+4. **Make your changes**
+   - Write clean, maintainable code
+   - Follow the existing code style
+   - Add tests if applicable
+   - Update documentation as needed
+
+5. **Test your changes**
+   ```bash
+   # Development mode (no build needed)
+   npm run dev
+   
+   # Or build and test
+   npm run build
+   npm start
+   
+   # Test with options
+   npm run dev -- --dry-run
+   npm run dev -- --strict --docker
+   ```
+   
+   **Test in a real project:**
+   ```bash
+   # Create test project
+   mkdir test-project && cd test-project
+   npm init -y
+   
+   # Use npm link (from stackinit directory)
+   npm link
+   
+   # Now test from test-project
+   stackinit --dry-run
+   ```
+
+6. **Commit your changes**
+   ```bash
+   git add .
+   git commit -m "feat: add your feature description"
+   ```
+   
+   We follow [Conventional Commits](https://www.conventionalcommits.org/):
+   - `feat:` for new features
+   - `fix:` for bug fixes
+   - `docs:` for documentation changes
+   - `style:` for code style changes (formatting, etc.)
+   - `refactor:` for code refactoring
+   - `test:` for adding or updating tests
+   - `chore:` for maintenance tasks
+
+7. **Push and create a Pull Request**
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+8. **Open a Pull Request**
+   - Provide a clear description of your changes
+   - Reference any related issues
+   - Wait for review and address feedback
+
+## Development Setup
+
+### Prerequisites
+
+- Node.js >= 18.0.0
+- npm, yarn, or pnpm
+
+### Installation
+
+```bash
+# Clone the repository
+git clone https://github.com/yourusername/stackinit.git
+cd stackinit
+
+# Install dependencies
+npm install
+
+# Build the project
+npm run build
+```
+
+### Development Workflow
+
+```bash
+# Run in development mode (with tsx)
+npm run dev
+
+# Build TypeScript
+npm run build
+
+# Run the built CLI
+npm start
+```
+
+### Testing Your Changes
+
+To test your changes locally:
+
+1. Build the project:
+   ```bash
+   npm run build
+   ```
+
+2. Create a test project directory:
+   ```bash
+   mkdir test-project
+   cd test-project
+   npm init -y
+   ```
+
+3. Run stackinit from the built dist:
+   ```bash
+   node ../stackinit/dist/index.js
+   ```
+
+   Or use `npm link` for easier testing:
+   ```bash
+   # From stackinit directory
+   npm link
+   
+   # From test project directory
+   npx stackinit
+   ```
+
+## Code Style Guidelines
+
+### TypeScript
+
+- Use TypeScript strict mode
+- Prefer explicit types over `any`
+- Use meaningful variable and function names
+- Keep functions focused and small
+- Add JSDoc comments for public APIs
+
+### Code Organization
+
+- Keep modules focused on a single responsibility
+- Use descriptive file and directory names
+- Group related functionality together
+- Export only what's necessary
+
+### Formatting
+
+The project uses Prettier for code formatting. Before committing:
+
+```bash
+npm run format
+```
+
+### Linting
+
+We use ESLint for code quality. Check for linting errors:
+
+```bash
+npm run lint
+```
+
+Fix auto-fixable issues:
+
+```bash
+npm run lint:fix
+```
+
+## Project Structure
+
+```
+stackinit/
+├── src/
+│   ├── index.ts          # CLI entry point
+│   ├── detect.ts         # Project detection logic
+│   ├── generate.ts       # File generation
+│   ├── templates.ts      # Template content
+│   ├── husky.ts          # Husky setup
+│   ├── ci.ts             # CI generation
+│   ├── docker.ts         # Docker generation
+│   └── types.ts          # Type definitions
+├── dist/                 # Compiled output (gitignored)
+└── ...
+```
+
+## Areas for Contribution
+
+We welcome contributions in these areas:
+
+- **Bug fixes**: Fix issues reported in the issue tracker
+- **New features**: Add support for new project types or tools
+- **Documentation**: Improve README, add examples, write guides
+- **Testing**: Add tests to improve code coverage
+- **Performance**: Optimize detection or generation logic
+- **DX improvements**: Better error messages, more helpful output
+
+## Review Process
+
+1. All pull requests require at least one review
+2. Maintainers will review your PR and may request changes
+3. Once approved, a maintainer will merge your PR
+4. Be patient and responsive to feedback
+
+## Questions?
+
+If you have questions about contributing:
+
+- Open an issue with the "question" label
+- Check existing issues and discussions
+- Review the README for project overview
+
+## Recognition
+
+Contributors will be recognized in:
+- The project's README (if applicable)
+- Release notes for significant contributions
+- GitHub contributors page
+
+Thank you for contributing to stackinit! 🎉
+

package/Dockerfile

@@ -0,0 +1,36 @@
+# Build stage
+FROM node:20-alpine AS builder
+
+WORKDIR /app
+
+# Copy package files
+COPY package.json COPY package-lock.json .
+
+RUN npm ci
+
+# Copy source files
+COPY . .
+
+# Build the application (adjust as needed)
+RUN npm run build
+
+# Production stage
+FROM node:20-alpine AS production
+
+WORKDIR /app
+
+# Copy package files
+COPY package.json COPY package-lock.json .
+
+# Install production dependencies only
+RUN npm ci --only=production
+
+# Copy built application from builder
+COPY --from=builder /app/dist ./dist
+COPY --from=builder /app/public ./public 2>/dev/null || true
+
+# Expose port (adjust as needed)
+EXPOSE 3000
+
+# Start the application
+CMD ["node", "dist/index.js"]

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2024 stackinit
+
+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/README.md

@@ -0,0 +1,202 @@
+# stackinit
+
+> Initialize a consistent development environment for Node-based projects with a single command.
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
+## Philosophy
+
+`stackinit` is an opinionated CLI tool that sets up a production-ready development environment for Node.js projects. It follows these principles:
+
+- **Zero configuration by default**: Sensible defaults that work for most projects
+- **Non-destructive**: Never overwrites existing files
+- **TypeScript-first**: Optimized for TypeScript projects but works with JavaScript
+- **No interactive prompts**: Everything is configurable via flags
+- **Production-ready**: Includes CI/CD, linting, formatting, and git hooks out of the box
+
+## Installation
+
+```bash
+npx stackinit
+```
+
+Or install globally:
+
+```bash
+npm install -g stackinit
+```
+
+## Usage
+
+### Basic Usage
+
+Run `stackinit` in your project directory:
+
+```bash
+npx stackinit
+```
+
+This will:
+- Auto-detect your project type (Node, React, Next.js, Vite)
+- Detect your package manager (npm, yarn, pnpm)
+- Generate configuration files (ESLint, Prettier, .gitignore, etc.)
+- Set up Husky git hooks with lint-staged
+- Create GitHub Actions CI workflow
+
+### Options
+
+```bash
+npx stackinit [options]
+
+Options:
+  --strict        Enable stricter lint rules and CI failure on warnings
+  --docker        Generate Dockerfile and docker-compose.yml
+  --ci-only       Generate only GitHub Actions workflow
+  --dry-run       Show what files would be created without writing
+  -h, --help      Display help for command
+  -V, --version   Display version number
+```
+
+### Examples
+
+**Strict mode with Docker:**
+```bash
+npx stackinit --strict --docker
+```
+
+**CI-only (for existing projects):**
+```bash
+npx stackinit --ci-only
+```
+
+**Dry run to preview changes:**
+```bash
+npx stackinit --dry-run
+```
+
+## What Gets Generated
+
+### Configuration Files
+
+- **`.eslintrc.json`** - ESLint configuration (TypeScript-aware, React-aware)
+- **`.prettierrc.json`** - Prettier configuration
+- **`.prettierignore`** - Prettier ignore patterns
+- **`.gitignore`** - Comprehensive .gitignore for Node.js projects
+- **`.editorconfig`** - EditorConfig for consistent coding styles
+- **`.env.example`** - Environment variables template
+
+### Git Hooks (Husky)
+
+- **pre-commit** - Runs lint-staged to lint and format staged files
+- **commit-msg** - Runs commitlint (only in strict mode)
+
+### CI/CD
+
+- **`.github/workflows/ci.yml`** - GitHub Actions workflow that:
+  - Installs dependencies
+  - Runs linting
+  - Runs type checking (if TypeScript)
+  - Runs tests (if present)
+
+### Docker (optional)
+
+- **`Dockerfile`** - Multi-stage Docker build
+- **`docker-compose.yml`** - Docker Compose configuration
+
+### Package.json Scripts
+
+The following scripts are added to your `package.json` (only if they don't already exist):
+
+- `lint` - Run ESLint
+- `lint:fix` - Run ESLint with auto-fix
+- `format` - Format code with Prettier
+- `format:check` - Check code formatting
+- `type-check` - TypeScript type checking (if TypeScript is detected)
+- `prepare` - Husky install hook
+
+## Project Detection
+
+`stackinit` automatically detects:
+
+- **Project Type**: Node backend, React, Next.js, Vite
+- **Package Manager**: npm, yarn, pnpm (via lock files or package.json)
+- **TypeScript**: Checks for `tsconfig.json` or TypeScript in dependencies
+- **Monorepo**: Detects pnpm workspaces, Lerna, Nx, Turborepo, Rush
+
+## Features
+
+### Auto-Detection
+
+The tool intelligently detects your project setup and generates appropriate configurations:
+
+- **React projects**: Adds React ESLint plugins
+- **Next.js projects**: Adds Next.js ESLint config
+- **TypeScript projects**: Configures TypeScript ESLint parser
+- **Monorepos**: Adapts configurations for monorepo structures
+
+### Non-Destructive
+
+`stackinit` never overwrites existing files. If a file already exists, it will be skipped with a warning.
+
+### Strict Mode
+
+When using `--strict`:
+
+- Stricter ESLint rules
+- CI fails on warnings (not just errors)
+- Commitlint enabled for conventional commits
+- More aggressive TypeScript checks
+
+## Requirements
+
+- Node.js >= 18.0.0
+- Git repository (for Husky setup)
+
+## After Running
+
+`stackinit` automatically:
+
+- ✅ Installs all required dependencies (ESLint, Prettier, Husky, lint-staged, etc.)
+- ✅ Detects and installs TypeScript ESLint plugins if TypeScript is detected
+- ✅ Detects and installs React plugins if React is detected
+- ✅ Installs commitlint if `--strict` mode is enabled
+- ✅ Initializes Husky git hooks (if in a git repository)
+
+**That's it!** You're ready to start developing. The tool handles everything automatically based on your project setup.
+
+## Development
+
+### Testing Locally
+
+To test `stackinit` locally during development:
+
+```bash
+# Install dependencies
+npm install
+
+# Development mode (runs TypeScript directly)
+npm run dev
+
+# Or build and test
+npm run build
+npm start
+
+# Test with options (note: use -- to pass flags to the script)
+npm run dev -- --dry-run
+npm run dev -- --strict
+npm run dev -- --docker
+npm run dev -- --strict --docker
+```
+
+**Important:** When using npm scripts, use `--` to pass flags to the underlying command. For example: `npm run dev -- --docker`
+
+For detailed development and testing instructions, see [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Contributing
+
+Contributions are welcome! Please read our [Contributing Guidelines](CONTRIBUTING.md) for details on our code of conduct and the process for submitting pull requests.
+
+## License
+
+MIT
+

package/dist/banner.d.ts

@@ -0,0 +1,2 @@
+export declare function printBanner(): void;
+//# sourceMappingURL=banner.d.ts.map

package/dist/banner.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"banner.d.ts","sourceRoot":"","sources":["../src/banner.ts"],"names":[],"mappings":"AAAA,wBAAgB,WAAW,IAAI,IAAI,CAclC"}

package/dist/banner.js

@@ -0,0 +1,16 @@
+export function printBanner() {
+    const banner = `
+╔═══════════════════════════════════════════════════════════════════════╗
+║                                                                       ║
+║                                                                       ║
+║                          S T A C K I N I T                            ║
+║                                                                       ║
+║                                                                       ║
+║              Initialize your development environment                  ║
+║                                                                       ║
+║                                                                       ║
+╚═══════════════════════════════════════════════════════════════════════╝
+`;
+    console.log(banner);
+}
+//# sourceMappingURL=banner.js.map

package/dist/banner.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"banner.js","sourceRoot":"","sources":["../src/banner.ts"],"names":[],"mappings":"AAAA,MAAM,UAAU,WAAW;IACzB,MAAM,MAAM,GAAG;;;;;;;;;;;CAWhB,CAAC;IACA,OAAO,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;AACtB,CAAC"}

package/dist/ci.d.ts

@@ -0,0 +1,3 @@
+import type { ProjectInfo, Options } from './types.js';
+export declare function generateCI(projectInfo: ProjectInfo, options: Options): Promise<void>;
+//# sourceMappingURL=ci.d.ts.map

package/dist/ci.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ci.d.ts","sourceRoot":"","sources":["../src/ci.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,WAAW,EAAE,OAAO,EAAE,MAAM,YAAY,CAAC;AAEvD,wBAAsB,UAAU,CAAC,WAAW,EAAE,WAAW,EAAE,OAAO,EAAE,OAAO,GAAG,OAAO,CAAC,IAAI,CAAC,CAuB1F"}