feat: improve Lingo.dev Compiler initialization API

[davidturnbull]

Summary

Refactor Lingo.dev Compiler API with dedicated framework-specific export paths for Vite and Next.js, improving developer experience with clearer imports and plugin usage patterns.

What changed

New framework-specific export paths

The compiler now provides dedicated, publicly-documented export paths instead of requiring framework-specific method access on a default export:

Before (old pattern):

import lingoCompiler from "lingo.dev/compiler";

// Using framework-specific methods
export default lingoCompiler.vite(config)(viteConfig);
export default lingoCompiler.next(config)(nextConfig);

After (new pattern):

// Direct, framework-specific imports
import { lingo } from "lingo.dev/compiler/vite";
import { withLingo } from "lingo.dev/compiler/next";

// Use as regular Vite plugins
plugins: [lingo(config), react(), ...]

// Use as Next.js configuration wrapper
export default withLingo(config)(nextConfig);

Structural changes

• Created packages/compiler/src/vite.ts: Exports lingo() function that returns a Vite-compatible plugin. Automatically detects React Router and emits appropriate build events.
• Created packages/compiler/src/next.ts: Exports withLingo() function with Next.js-specific configuration handling (Webpack, Turbopack, etc).
• Refactored packages/compiler/src/unplugin.ts: Extracted core unplugin logic that was previously in index.ts.
• Updated packages/compiler/src/index.ts: Now maintains backward compatibility by delegating to the new framework-specific modules.
• Updated package exports: Added ./compiler/vite and ./compiler/next export paths in both packages/cli/package.json and packages/compiler/package.json.
• Updated build config: Modified packages/cli/tsup.config.ts to build the new export paths.

Demo updates

All demo projects have been updated to use the new API:

• demo/vite-project/vite.config.ts: Now uses lingo() as a regular plugin instead of the curried wrapper pattern
• demo/react-router-app/vite.config.ts: Simplified to inline plugin format
• demo/adonisjs/vite.config.ts: Uses new import path with cleaner plugin array
• demo/next-app/next.config.ts: Uses withLingo() instead of lingoCompiler.next()

Why

• Clearer mental model: Users import what they need for their framework rather than accessing nested methods
• Better TypeScript support: Direct imports enable better IDE autocomplete and type checking
• Familiar patterns: Follows standard conventions for framework plugins (similar to Tailwind, React Router, etc)
• Backward compatible: Old API still works through re-exports in the default export
• Easier to document: Framework-specific docs can point to specific import paths

Testing

To verify the new API works correctly:

1. Verify package exports are built correctly:

   cd packages/compiler && pnpm build
   ls -la build/vite.* build/next.*

2. Test Vite integration with demo project:

   cd demo/vite-project && pnpm install && pnpm dev
   # Verify compilation works in browser

3. Test Next.js integration with demo project:

   cd demo/next-app && pnpm install && pnpm build
   # Verify build completes successfully

4. Test React Router demo:

   cd demo/react-router-app && pnpm install && pnpm dev
   # Verify React Router framework is detected and build events are correct

5. Verify backward compatibility:

   • Projects still using the old lingoCompiler.vite() and lingoCompiler.next() API should continue working
   • Check that the old pattern still functions correctly as a fallback

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.