@nestjs-ssr/react 0.1.7 → 0.1.9

package/README.md

@@ -1,176 +1,39 @@
 # @nestjs-ssr/react
 
-**React SSR for NestJS that respects Clean Architecture.**
-
-A lightweight, production-ready library that brings React to NestJS while preserving the architectural principles that make NestJS great: **Dependency Injection**, **SOLID principles**, and **clear separation of concerns**.
-
-## Why This Library?
-
-### Built for Clean Architecture
-
-If you value [Uncle Bob's Clean Architecture](https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html) and software craftsmanship, you'll appreciate how this library maintains architectural boundaries:
-
-**Clear Separation of Concerns:**
-```typescript
-// View component with typed props (Presentation Layer)
-export interface UserProfileProps {
-  user: User;
-}
-
-export default function UserProfile(props: PageProps<UserProfileProps>) {
-  return <div>{props.user.name}</div>;  // Pure presentation
-}
-
-// Server logic stays in controllers (Application Layer)
-import UserProfile from './views/user-profile';
-
-@Controller()
-export class UserController {
-  constructor(private userService: UserService) {}  // Proper DI
-
-  @Get('/users/:id')
-  @Render(UserProfile)  // Type-safe! Cmd+Click to navigate
-  async getUserProfile(@Param('id') id: string) {
-    const user = await this.userService.findById(id);  // Business logic
-    return { user };  // ✅ TypeScript validates this matches UserProfileProps
-  }
-}
-```
-
-**No Server/Client Confusion:**
-- Server code is server code (Controllers, Services, Guards)
-- Client code is client code (React components, hooks)
-- No `'use server'` / `'use client'` directives scattered throughout
-- No mixing of database queries with JSX
-- No hidden boundaries where code "magically" switches execution context
-
-**True Dependency Injection:**
-```typescript
-// Use NestJS DI throughout your application
-@Injectable()
-export class ProductService {
-  constructor(
-    private db: DatabaseService,
-    private cache: CacheService,
-  ) {}
-}
-
-// Testable, mockable, follows IoC principle
-```
-
-### Why Not Next.js?
-
-Next.js is excellent for many use cases, but if you care about architectural integrity:
-
-**Next.js encourages coupling:**
-```tsx
-// ❌ Server and client code mixed in the same file
-export default function Page() {
-  const data = await fetch('...').then(r => r.json());  // Server
-  const [count, setCount] = useState(0);                 // Client
-  return <button onClick={() => setCount(count + 1)}>{data.title}</button>;
-}
-```
-- Server and client logic intertwined
-- No dependency injection - just imports and function calls
-- Difficult to test business logic in isolation
-- Routes are files, not proper routing with guards/interceptors
-- Framework-specific patterns instead of universal principles
-
-**NestJS SSR maintains boundaries:**
-```tsx
-// ✅ View: Client-only, pure presentation
-export interface ProductsProps {
-  products: Product[];
-}
-
-export default function Products(props: PageProps<ProductsProps>) {
-  const [selected, setSelected] = useState(null);
-  return <ProductList products={props.products} onSelect={setSelected} />;
-}
-
-// ✅ Controller: Server-only, testable, uses DI
-import Products from './views/products';
-
-@Controller()
-export class ProductController {
-  constructor(private productService: ProductService) {}
-
-  @Get('/products')
-  @UseGuards(AuthGuard)  // Proper middleware
-  @Render(Products)  // Type-safe component reference
-  async list() {
-    return { products: await this.productService.findAll() };
-  }
-}
-```
-
-### Performance as a Bonus
-
-Following clean architecture doesn't mean sacrificing performance. In our benchmarks:
-
-- **NestJS SSR:** 3,050 req/sec (32ms latency)
-- **Next.js:** 2,965 req/sec (33ms latency)
-- **Remix:** 915 req/sec (109ms latency)
-
-**Equal performance** with **better architecture.**
+Server-side rendering for React in NestJS with full TypeScript support and type-safe props.
 
 ## Features
 
-✅ **Type-Safe Props** - Automatic validation of controller return types against component props
-✅ **IDE Navigation** - Cmd+Click on components to jump to view files
-✅ **Architectural Integrity** - Respects SOLID and Clean Architecture principles
-✅ **Dependency Injection** - Full NestJS DI throughout your application
-✅ **Clear Boundaries** - Server code is server, client code is client
-✅ **Zero Configuration** - Works out of the box with sensible defaults
-✅ **TypeScript First** - Fully typed with excellent IDE support
-✅ **Streaming SSR** - Modern renderToPipeableStream support
-✅ **HMR in Development** - Powered by Vite for instant feedback
-✅ **Production Optimized** - Code splitting, compression, and caching
-✅ **Testable** - Easy to unit test controllers and services separately
+- **Type-Safe Props** - TypeScript validates controller returns match component props
+- **Zero Config** - Works out of the box with sensible defaults
+- **Streaming SSR** - Modern renderToPipeableStream support
+- **HMR in Development** - Powered by Vite for instant feedback
+- **Production Ready** - Code splitting, caching, and optimizations built-in
 
-## Quick Start
-
-### Installation
+## Installation
 
 ```bash
-npm install @nestjs-ssr/react react react-dom vite
+npm install @nestjs-ssr/react
+npx nestjs-ssr  # Set up your project automatically
 ```
 
-### 1. Configure Vite
-
-```typescript
-// vite.config.ts
-import { defineConfig } from 'vite';
-import react from '@vitejs/plugin-react';
-import { resolve } from 'path';
+The CLI installs dependencies, creates entry files, and configures TypeScript/Vite for you.
 
-export default defineConfig({
-  plugins: [react()],
-  resolve: {
-    alias: {
-      '@': resolve(__dirname, 'src'),
-    },
-  },
-});
-```
+## Usage
 
-### 2. Setup NestJS Module
+**1. Register the module**
 
 ```typescript
 // app.module.ts
-import { Module } from '@nestjs/common';
 import { RenderModule } from '@nestjs-ssr/react';
 
 @Module({
-  imports: [
-    RenderModule.register(), // Zero config!
-  ],
+  imports: [RenderModule],
 })
 export class AppModule {}
 ```
 
-### 3. Create a View Component
+**2. Create a view component**
 
 ```typescript
 // src/views/home.tsx
@@ -185,7 +48,7 @@ export default function Home(props: PageProps<HomeProps>) {
 }
 ```
 
-### 4. Create a Controller
+**3. Use in a controller**
 
 ```typescript
 // app.controller.ts
@@ -196,379 +59,61 @@ import Home from './views/home';
 @Controller()
 export class AppController {
   @Get()
-  @Render(Home)  // Type-safe! Cmd+Click to navigate to view
+  @Render(Home)
   getHome() {
-    return { message: 'Hello from NestJS SSR!' };
+    return { message: 'Hello World' };  // TypeScript validates this!
   }
 }
 ```
 
-That's it! No manual view registry or entry files needed - everything is handled automatically.
-
-### 5. Run
-
-```bash
-npm run dev
-```
-
-Visit [http://localhost:3000](http://localhost:3000) 🎉
-
-## Core Concepts
-
-### The `@Render` Decorator
-
-The decorator takes a React component and automatically validates that your controller returns the correct props:
-
-```typescript
-import UserProfile from './views/user-profile';
-
-@Get('/users/:id')
-@Render(UserProfile)  // Type-safe! Cmd+Click to navigate
-async getUser(@Param('id') id: string) {
-  const user = await this.userService.findOne(id);
-  return { user }; // ✅ TypeScript validates this matches component props
-}
-```
-
-### Type-Safe Props
-
-Components receive props with full TypeScript support and validation:
-
-```typescript
-import type { PageProps } from '@nestjs-ssr/react';
-
-export interface UserProfileProps {
-  user: User;
-}
-
-export default function UserProfile(props: PageProps<UserProfileProps>) {
-  return (
-    <div>
-      <h1>{props.user.name}</h1>
-      <p>Requested from: {props.context.path}</p>
-    </div>
-  );
-}
-```
-
-**Benefits:**
-- ✅ Build-time validation - wrong props = compilation error
-- ✅ Cmd+Click navigation from controller to view file
-- ✅ No manual type annotations needed
-- ✅ Refactoring-friendly - rename props with confidence
+That's it! Run `npm run dev` and visit http://localhost:3000
 
-### Request Context
-
-Every component receives the request context:
-
-```typescript
-interface RenderContext {
-  url: string;
-  path: string;
-  query: Record<string, any>;
-  params: Record<string, string>;
-  userAgent?: string;
-  acceptLanguage?: string;
-  referer?: string;
-}
-```
-
-You can extend it with custom data using TypeScript declaration merging!
+## API
 
 ### React Hooks
 
-Access context in any component:
-
 ```typescript
 import { usePageContext, useParams, useQuery } from '@nestjs-ssr/react';
 
 function MyComponent() {
-  const context = usePageContext();
-  const params = useParams();
-  const query = useQuery();
-
+  const context = usePageContext();  // { url, path, query, params, ... }
+  const params = useParams();        // Route params
+  const query = useQuery();          // Query string
   return <div>User ID: {params.id}</div>;
 }
 ```
 
-## Configuration
-
-### SSR Modes
-
-Choose between string mode (simple) or stream mode (faster):
+### Head Tags & SEO
 
 ```typescript
-RenderModule.register({
-  mode: 'stream', // or 'string' (default)
-})
-```
+import { Head } from '@nestjs-ssr/react';
 
-### Custom Error Pages
-
-```typescript
-import { ErrorPageCustom } from './error-page';
-
-RenderModule.register({
-  errorPageDevelopment: ErrorPageCustom,
-  errorPageProduction: ErrorPageCustom,
-})
-```
-
-### Environment Variables
-
-```bash
-SSR_MODE=stream          # 'string' or 'stream'
-NODE_ENV=production      # Enables production optimizations
-```
-
-### Vite Development Setup
-
-You have two options for integrating Vite during development:
-
-#### Option 1: Simple Setup (Recommended for Getting Started)
-
-Use Vite in middleware mode directly within NestJS. This approach is simpler but requires manual page refresh to see changes.
-
-```typescript
-// main.ts
-import { createServer as createViteServer } from 'vite';
-import { RenderService } from '@nestjs-ssr/react';
-
-async function bootstrap() {
-  const app = await NestFactory.create(AppModule);
-  const renderService = app.get(RenderService);
-
-  if (process.env.NODE_ENV !== 'production') {
-    const vite = await createViteServer({
-      server: { middlewareMode: true },
-      appType: 'custom',
-    });
-
-    app.use(vite.middlewares);
-    renderService.setViteServer(vite);
-  }
-
-  await app.listen(3000);
-}
-```
-
-**Pros:**
-- Simple setup (~10 lines of code)
-- Single server on port 3000
-- Auto-restart on file changes
-
-**Cons:**
-- Requires manual page refresh to see changes
-- No hot module replacement (HMR)
-
-See [`minimal-simple`](../../examples/minimal-simple) example.
-
-#### Option 2: Full HMR Setup (Best Developer Experience)
-
-Run a separate Vite dev server with proxy middleware for instant hot reloading.
-
-```typescript
-// main.ts
-import { createServer as createViteServer } from 'vite';
-import { RenderService } from '@nestjs-ssr/react';
-
-async function bootstrap() {
-  const app = await NestFactory.create(AppModule);
-  const renderService = app.get(RenderService);
-
-  if (process.env.NODE_ENV !== 'production') {
-    // Proxy to external Vite server for HMR
-    const { createProxyMiddleware } = await import('http-proxy-middleware');
-    const viteProxy = createProxyMiddleware({
-      target: 'http://localhost:5173',
-      changeOrigin: true,
-      ws: true,
-      pathFilter: (pathname: string) => {
-        return (
-          pathname.startsWith('/src/') ||
-          pathname.startsWith('/@') ||
-          pathname.startsWith('/node_modules/')
-        );
-      },
-    });
-    app.use(viteProxy);
-
-    // Vite instance for SSR
-    const vite = await createViteServer({
-      server: { middlewareMode: true },
-      appType: 'custom',
-    });
-    renderService.setViteServer(vite);
-  }
-
-  await app.listen(3000);
-}
-```
-
-**Additional dependencies:**
-```bash
-npm install -D http-proxy-middleware concurrently
-```
-
-**package.json scripts:**
-```json
-{
-  "scripts": {
-    "start:dev": "concurrently \"vite --port 5173\" \"nest start --watch\""
-  }
-}
-```
-
-**vite.config.js:**
-```javascript
-export default defineConfig({
-  server: {
-    port: 5173,
-    strictPort: true,
-    hmr: { port: 5173 },  // Critical for HMR
-  },
-});
-```
-
-**Pros:**
-- Instant hot module replacement (HMR)
-- Best developer experience for rapid iteration
-- No page refresh needed
-
-**Cons:**
-- More complex setup (~40 lines)
-- Requires two servers (NestJS + Vite)
-- Additional dependencies
-
-See [`minimal`](../../examples/minimal) example.
-
-## Advanced Features
-
-### Error Monitoring (Coming in v0.2.0)
-
-Error monitoring integration is planned for the next release. It will support integrations with Sentry, Datadog, and custom error reporters.
-
-For now, you can use NestJS's built-in exception filters and logging for error handling.
-
-### Extending Context
-
-Add custom data to the render context:
-
-```typescript
-// types/render-context.d.ts
-declare module '@nestjs-ssr/react' {
-  interface RenderContext {
-    user?: User;
-    tenant?: string;
-  }
+export default function MyPage(props: PageProps<MyProps>) {
+  return (
+    <>
+      <Head>
+        <title>My Page</title>
+        <meta name="description" content="Page description" />
+      </Head>
+      <div>{props.content}</div>
+    </>
+  );
 }
 ```
 
-Then inject it in a custom interceptor.
-
-## Examples
-
-Choose the example that matches your needs:
-
-- **[Minimal Simple](../../examples/minimal-simple/)** - Simplest setup with Vite middleware (no HMR)
-  - Perfect for getting started quickly
-  - Single server, minimal configuration
-
-- **[Minimal](../../examples/minimal/)** - Full HMR setup with dual-server architecture
-  - Best developer experience with instant hot reloading
-  - Recommended for active development
-
-- **[Full-Featured](../../examples/full-featured/)** - Production-ready example
-  - Security headers, caching, error handling
-  - Streaming SSR with React Suspense
-
 ## Documentation
 
-- [Getting Started](../../docs/getting-started.md)
-- [Why NestJS SSR?](../../docs/why-nestjs-ssr.md)
-- [Architecture](../../docs/ARCHITECTURE.md)
-- [Testing Guide](../../docs/TESTING_STRATEGY.md)
-- [Production Deployment](../../docs/PRODUCTION_RISKS.md)
-
-## Philosophy
-
-This package is built on two foundational principles:
-
-### Clean Architecture & SOLID Principles
-
-Following [Uncle Bob's Clean Architecture](https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html) and software craftsmanship principles:
-
-**Single Responsibility Principle (SRP):**
-- Controllers handle HTTP routing and orchestration
-- Services contain business logic
-- Views handle presentation
-- Each has one reason to change
-
-**Dependency Inversion Principle (DIP):**
-- Controllers depend on service abstractions (interfaces)
-- Services are injected via NestJS DI
-- Views receive data as props (dependency injection via props)
-- No concrete dependencies on frameworks in your business logic
-
-**Interface Segregation & Open/Closed:**
-- Use NestJS Guards for authentication/authorization
-- Use Interceptors for cross-cutting concerns
-- Views are pure functions - open for extension, closed for modification
-
-**Clear Architectural Boundaries:**
-```
-┌─────────────────────────────────────────┐
-│  Presentation Layer (React Components)  │
-│  - Pure presentation logic              │
-│  - Client-side interactivity            │
-│  - No business logic                    │
-└─────────────────────────────────────────┘
-              ↓ Props (Data Flow)
-┌─────────────────────────────────────────┐
-│  Application Layer (Controllers)        │
-│  - Request handling                     │
-│  - Orchestration                        │
-│  - DTO validation                       │
-└─────────────────────────────────────────┘
-              ↓ DI (Dependency Injection)
-┌─────────────────────────────────────────┐
-│  Domain Layer (Services)                │
-│  - Business logic                       │
-│  - Domain models                        │
-│  - Use cases                            │
-└─────────────────────────────────────────┘
-```
-
-### UnJS Philosophy
-
-Following the [UnJS philosophy](https://unjs.io/) for modern JavaScript libraries:
-
-1. **Unintrusive** - Integrates seamlessly with existing NestJS apps
-2. **Zero-Config** - Works out of the box with sensible defaults
-3. **Fully Extensible** - Customize everything when needed
-4. **Framework Agnostic** - No opinions on routing, state, or business logic
-5. **TypeScript First** - Excellent type safety and IDE support
-
-**The Result:** Clean, maintainable, testable code that scales with your team and product.
+- [Full Documentation](https://georgialexandrov.github.io/nestjs-ssr/)
+- [Examples](https://github.com/georgialexandrov/nestjs-ssr/tree/main/examples)
+- [GitHub](https://github.com/georgialexandrov/nestjs-ssr)
 
 ## Requirements
 
-- Node.js 18+
+- Node.js 20+
 - NestJS 11+
 - React 19+
-- Vite 6+
 - TypeScript 5+
 
 ## License
 
-MIT © Georgi Alexandrov
-
-## Contributing
-
-Contributions welcome! Please see [CONTRIBUTING.md](../../CONTRIBUTING.md).
-
-## Support
-
-- [GitHub Issues](https://github.com/georgialexandrov/nestjs-ssr/issues)
-- [Documentation](../../docs/)
-- [Examples](../../examples/)
+MIT © [Georgi Alexandrov](https://github.com/georgialexandrov)

package/dist/cli/init.d.mts

@@ -0,0 +1 @@
+#!/usr/bin/env node

package/dist/cli/init.d.ts

@@ -0,0 +1 @@
+#!/usr/bin/env node